Dave van Herten retweeted
Basic, but important:
Product teams should rarely prioritize Efficiency higher than Effectiveness. And yet so many do
How to tell them apart:
Teams that value Efficiency obsess over Speed & Process
Teams that value Effectiveness obsess over Customer Problems & Differentiation
Dave van Herten retweeted
We released patch 1.2 of #TheOuterWorlds today, and it includes a fix for the dreaded "the game thinks my companions are dead" bug, which I believe I spent more time investigating than I have for any other individual bug in my career (1/18)
Dave van Herten retweeted
🚨 📣 Announcing:
🏆🔥🏆🔥🏆🔥🏆🔥🏆🔥🏆
🔥🏆 TestingJavaScript.com 🏆🔥
🏆🔥🏆🔥🏆🔥🏆🔥🏆🔥🏆
💸 There's a HUGE discount right now too 💸
From total beginner to EXPERT tester with 8.5 hours of *super* high value-to-minute content (I don't waste your time), and ...
1/9
Dave van Herten retweeted
not using a framework is sometimes creating an ad-hoc, undocumented, non-standard, can't look up answers on stackoverflow, bespoke personal framework
Dave van Herten retweeted
Most common mistake software developers make: putting stuff in the wrong place. Coupling responsibilities and concepts that should be kept separate.
For me, this is 95% of software development. Just figuring out *where* things belong.
Dave van Herten retweeted
One of the most valuable concepts I learned in school: Opportunity cost - The loss of potential gain from other options when an option is chosen.
This is why getting comfortable with saying "no" is important.
Every "yes" is an implicit "no" to something else.
Dave van Herten retweeted
Today is YC's Demo Day, where founders try their hardest to give away control of their company.
Let's celebrate bootstrapped and self-funded founders with our own "Demo Day". Reply with:
1. A description of your company in 10 words or less
2. MRR (if any)
3. Link to your site
Dave van Herten retweeted
The longer I do design systems the more I feel like seeing a lot very flexible APIs in your tools is a red flag. It's another thing in Decision Debt land. Thread:
Dave van Herten retweeted
Whenever a rule is added in a team, first ask:
Will the existence of this rule discourage future people from using their human judgement to make smart decisions in nuanced situations?
Dave van Herten retweeted
Optimist - The glass is half full.
Pessimist - The glass is half empty.
Developer - The glass is twice as big as it needs to be.
Product Owner - We need to put 3 times more water in that glass; Make it happen
Dave van Herten retweeted
The most frustrating thing in debugging is not finding the problem. It's when you find the problem, see the problem, fully understand and agree with the problem...and now don't understand how it EVER worked.
Dave van Herten retweeted
What good is a retro if you cannot actually implement improvements? In that situation, a retro is a demoralizing exercise in futility, and the SM needs to improve the surrounding org, as per the Scrum Guide, to get the team motivated.
Dave van Herten retweeted
For those of you who hate microservices because of some maintenance or testing nightmare, there is such a thing as bad design/implementation. Simply using an architecture does not guarantee a good (maintainable, testable) system. That requires knowledge, experience, thinking, &c.
Dave van Herten retweeted
Most advice is too general, hence, it might apply to you, or not.
That’s not a good reason to discount it though.
You should evaluate advice to uncover its intended audience and any implicit prerequisites.
Dave van Herten retweeted
Pro Tip: Part of your automated test suite is one that hits your prod domains and fails if their certs expire in less than 30 days. – at Sugar Bush Knolls, OH
Dave van Herten retweeted
Of course, I wouldn't be surprised if somebody responded to the above with a "you can't run a business like that." That's true. You can't run a 19th century business like that. Just ask Taylor.
Dave van Herten retweeted
The basic premise of Agile development is that predictability is impossible. Since you can't predict anything reliably, it's better to be adaptable than predictable. Plan accordingly. The desire for predictability is waterfall planning. Ppl don't understand how radical Agile is.



















