The factory and bridge-building software analogies create bad practices, thinking about software as a being like a garden is a more realistic and useful approach.

how people often perceive lots of work as being the same as lots of bad work

A discussion of the relative worth of the very best coders and how their skills will never get reflected in their salary.

How moving to a tools of the trade IT approach can help engineers and other knowledge workers have a better environment.

Has nothing to do with killing children, but does discuss agile processes. Highly random.

Some simple rules to consider when making the decision to rewrite a major piece of software

How to deal with ego as a software manager

Rambling thoughts about management consulting

How we may have passed the cost-effectiveness point on outsourced development work

How organizations can create rules and conventions that work for them

How good software companies blend opportunism and idealism

A discussion on how to organize people and teams.

Why humility is an important virtue for a startup company

Project delivery bonuses are common, but more often than not they end up doing more harm, than good.

Conventional wisdom says you should never do something that others have already done. I think this is taking things a bit too far.

Why bigger isn’t always (or even generally) better when it comes to picking which tools to use.

How trying to be to careful not to let anything go wrong can sometimes be worse than accepting that things will go wrong.

How to use the things you fear in your code (or organization) to help you become better.

How bad experts can create dependent organizations.

Sometimes it’s best not to let your mind get in the way too much when trying to look for ways to improve.