pav (@blorgfester) 's Twitter Profile
pav

@blorgfester

Who/Whom/Whose

ID: 2962162925

calendar_today05-01-2015 14:54:17

397 Tweet

127 Followers

340 Following

Brandon Jacoby (@jacobybrandon) 's Twitter Profile Photo

Nike and Apple principles from the early days. Absolute gold. “If we do the right things, we’ll make money damn near automatic”

Nike and Apple principles from the early days. Absolute gold.

“If we do the right things, we’ll make money damn near automatic”
Quite Interesting (@qikipedia) 's Twitter Profile Photo

NASA research shows that a successful mission to Mars would require a ‘class clown’ to resolve tensions, boost morale and unite teams. E.g., Scott’s Antarctic exploration team didn’t have a joker and broke into cliques, but Amundsen’s crew did, which helped with group cohesion.

Vala Afshar (@valaafshar) 's Twitter Profile Photo

Poor manager Good manager —————— —————— Controlling Collaborative On the sideline Player coach Self-centered Humble, giving Big opinions Lifelong student Company first Customer first No feedback A Mentor Demanding Developing

Cory House (@housecor) 's Twitter Profile Photo

9 things that I've found improve development team velocity: - Mock APIs - Static types - Fast CI builds - Fast feedback loops - Small, focused tickets - Frequent, small releases - Comprehensive, fast tests - Automated code quality checks - Automatic code formatting on save

Dave Craft (@craftyfella) 's Twitter Profile Photo

👋 my contract is ending soon and I'm considering options for remote contract/fixed price/perm work. #fsharp #csharp #dotnet #goland #typescript. Happy to lead a project from beginning to delivery. Most recently working with azure serverless. github.com/CraftyFella/ RTs 🙏

Miguel de Icaza ᯅ🍉 (@migueldeicaza) 's Twitter Profile Photo

Prioritize paper-cuts in your products over features. Missing features might bring more users, but they will just join the ranks of frustrated users that you are not helping. My long-tail thesis is that the pain of papercuts is larger than the pain of a missing feature

Prioritize paper-cuts in your products over features.

Missing features might bring more users, but they will just join the ranks of frustrated users that you are not helping.

My long-tail thesis is that the pain of papercuts is larger than the pain of a missing feature