Blog

🕑Jan 19, 2008 🖋John Locke 💬0

I give up. Trackbacks and Pingbacks now closed.

It's too bad the spammers are out to piss all over the public commons. Since I've started writing more regularly here, I've been getting inundated with pingbacks and trackbacks, and have to keep marking them as spam, a couple dozen a day.

🕑Jan 19, 2008 🖋John Locke 💬0

Reliable code: building in robustness

Ok. Last post on the quality code series. One of the downsides of getting older is realizing you do have shortcomings. You know how when you're young, going into a job interview, the toughest question is the one about your weaknesses?

🕑Jan 15, 2008 🖋John Locke 💬1

Clear code: Building understandable applications

Programming is an exercise in understanding a problem. To program effectively, you need to fully understand, in intricate detail, the problem your program is solving. Sometimes as a programmer you don't fully understand the problem until you've wrestled with it a few times in code.

🕑Jan 14, 2008 🖋John Locke 💬0

Powerful code: Get more out of every line

Programming borrows a lot from the construction industry. Many programming terms derive from construction: hacking, builds, development, architecture, scaffolding, frameworks, and dozens of others. But in some ways, programming has an element of power beyond construction.

🕑Jan 11, 2008 🖋John Locke 💬0

Quality Code: How do you judge?

We're hiring programmers, over at Freelock. I've been going through lots code samples to try to identify how experienced and competent a particular developer is. I also do this on a regular basis to evaluate how solid a particular open source project is.