Hacks on top of interim solutions are code donuts, they make you fat without providing good nutritional value. Avoid them when you can.

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.

Tools are an important part of writing code, but the most important tool by far is your brain.

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

How writing code is the best way to find the right design

Discussion of my recent experimental work at making ruby faster for a public benchmark/contest

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

I’m going to go ahead and start an open source project. Here are my starter ideas; I’m looking for input.

How YAGNI needs to be ballanced with what you really DO know.

How frameworks need to take the cycle of knowing and doing into account to be successful and why Ruby on Rails succeeeds at doing this.

How organizations can create rules and conventions that work for them

How writing code involves making good decisions and not just using the same pattern over and over again regardless of the situation

If people thought more about the people who read their code and acted more like traditional writers there would be a lot better code in the world.

Every good thing needs kept within some bounds of sanity, and that includes testing.

Some thoughts on what’s wrong with web development as we know it.

no matter how fast processors get they are never fast enough!

Reuse is not the be all and end all that some people seem to think it is. Here I disect a few of the problems of reuse.

Some thoughts on how committeees can write better standards

bad code… VERY bad code