13 Quotes by Kevlin Henney

Reading other people’s code is particularly hard. Not necessarily because other people’s code is bad, but because they probably think and solve problems in a different way to you.

We programmers are weird creatures. We love writing code. But when it comes to reading it we usually shy away. After all, writing code is so much more fun, and reading code is hard – sometimes almost impossible.

Fixing bugs is not making progress. You aren’t paid to debug. Debugging is waste.

You don’t have to make every module perfect before you check it in. You simply have to make it a little bit better than when you checked it out.

As Tony Hoare observed: There are two ways of constructing a software design: one way is to make it so simple that there are obviously no deficiencies and the other is to make it so complicated that there are no obvious deficiencies.

If your code needs comments, consider refactoring it so it doesn’t.

When did things go wrong? Probably already at the kick-off meeting. Some of the project members didn’t pay attention. Others didn’t understand the point. Worse, some disagreed and were already planning their coding standard rebellion. Finally, some got the point and agreed but, when the pressure in the project got too high, they had to let something go.

Beauty is born of and found in simplicity.

You need to spend evenings, weekends, and holidays educating yourself, therefore you cannot spend your evenings, weekends, and holidays working overtime on your current project.