out_coders retweeted
It’s come to my attention that many people think continuous delivery/deployment is about taking whatever crap you have in version control & shipping it into prod as fast as possible so you can test in prod
NO
CD is about making it SAFE to ship your code into prod quickly by:
out_coders retweeted
"Monolith" is the word you use when you want to blame the brokenness of your system on its size, instead of on 15 years of bad development practices.
out_coders retweeted
Art Overflow (monkeyuser.com/2020/art-over…)
out_coders retweeted
“On time” and “in budget” are utterly meaningless terms if you don’t know exactly what you’re creating in advance. “On time” building what, exactly? That sort of thinking simply can’t work in the face of learning and uncertainty. It can’t work if agility is your goal.
out_coders retweeted
Why do people name Sprints? I've never understood it. Once it's over, it's over. The whole naming thing seems like a fallback to waterfall scheduling and milestones.
out_coders retweeted
If you do TDD, you can pretty much say goodbye to your debugger. The presence of a bug is really the absence of a test. Add the test. About the only think I use debuggers for any more is analyzing legacy code that’s not adequately tested.
out_coders retweeted
What's coming in TypeScript 4? | HTTP Toolkit httptoolkit.tech/blog/whats-…
out_coders retweeted
Agile is about welcoming change. Management that thinks it’s about working faster will actively destroy any incipient agility.
“Twice the work in half the time” is a hand grenade thrown into the heart of your agility. It will destroy any chance you have at becoming Agile.
out_coders retweeted
Schmuck (monkeyuser.com/2020/schmuck/)
out_coders retweeted
In general, the need for estimation is inversely proportional to the transparency of your process. When you deliver every few days, people stop asking for estimates.
out_coders retweeted
Internal “Stakeholders” are usually the worst possible source of stories (or requirements) that drive development. Stakeholders can provide useful business-focused constraints, but only users/customers can tell you what they actually need in a product. 1/
out_coders retweeted
There isn’t a customer on the planet who cares how big your backlog is or how much work has gone into the refinement of it.
out_coders retweeted
There isn’t a customer on the planet who cares how many story points you completed in the last Sprint.
Replying to @duarte_vasco
The accountability of "success" needs to be business outcomes, not project metrics. We don't ship product metrics to customers.
out_coders retweeted
Pair Programming (monkeyuser.com/2020/pair-pro…)












