From the @energizedwork tweet stream with hash tag #rediscoveringkent:
Make software development economically valuable. Spend money slowly. Earn money quickly. Increase product lifespan. Increase options for business decisions.
Software development that doesn’t recognize economics risks the hollow victory of a technical success.
Software development will improve when we pay more attention to macro-optimization, social structure, responsibility and transparency.
Good, safe social interaction is as necessary to successful software development as good technical skills.
Humility is the rule of the day for an intervention.
You can’t manage other peoples’ expectations. You can communicate clearly what you know so their expectations have a chance of matching reality.
If you’re having trouble succeeding, fail. When you don’t know what to do, risking failure can be the shortest, surest road to success.
Don’t protect yourself from success by holding back. Do your best and then deal with the consequences. That’s extreme!
Good teams don’t just do the work, they think about how they’re working and why they’re working.
Collective ownership is this seemingly crazy idea that anyone can change any piece of code at any time
When a developer dismisses a bug its failure of values not technique. A bug might be a failure of technique but the developer doesn’t value learning.
What’s the simplest thing that could possibly work? Bias thinking toward eliminating unnecessary complexity. Try to solve more problems than you create.
It’s better to do a simple thing today and pay a little more tomorrow to change it if it needs it. Sometimes tomorrow never comes.
Two or more ideas about a design present an opportunity, not a problem.
A day without refactoring is like a day without sunshine.
Defects should be notable because they’re rare.
Watching someone else programming is about as interesting as watching grass die in a desert.