Favstar gets even better if you sign in.
Worried that TDD will slow down your programmers? Don't. They probably need slowing down.
New study shows that you should just figure out what works well for you and get on with things.
TDD is like chess: you can learn the rule in a few minutes, but if you’re lucky, you’ll learn new things from it every day.
Non-local variables are simply implicit parameters to every block of code in your entire system. So limit them.
A friendly, irregular reminder to try to interpret people generously. It’s made such a difference in my life.
Maybe the single most costly property of legacy code: I can't tell significant details from accidental ones.
In software job ads, fear terms like "fast-paced" and "minimal supervision". They probably mean "we're fucked" and "you have to save us".
Another reminder: please don't say "technical debt" when you mean "sloppiness".
Technical debt: the conscious decision to value nearer-term cash-flow over longer-term return on investment. Really. That’s it.
Q: “How do we convert story points to hours?” A: “Misguidedly.”
I take tiny steps, not in order to make fewer mistakes, but rather in order to notice my mistakes sooner and more easily see their cause.
The one constant throughout my entire software career: “I don’t care if the estimate’s accurate; I just need you to give me a number.”
How you write the code today very probably matters much less than your ongoing willingness to change it.
A skilled tester notices what I don't notice; I think that surfacing unarticulated assumptions forms the foundation of testing skill.
TDD will not lead to better design unless the programmer uses it as a way to internalise the relevant design principles.
European stuck in a Canadian's body. Barista. 5-pin Bowler. Adviser to software companies. Lifestyle designer. Friend. http://online-training.jbrains.ca
Like @jbrains’ tweets? Send them a Favstar Pro Membership to show you care.Gift them Pro!