Developing Programmers .com

I’ve been pretty impressively sick for about a week now. Again. I’ve recovered enough now to sit up at the computer for a bit, so hopefully I can give you another article soon. While I’m talking about health, health is important for a professional programmer. Let’s face it, if your day job involves sitting in [...]

Jamie Wodetzki is a technology lawyer. I had the opportunity to ask him some questions over breakfast. I asked him about two different topics: Mixing open source and proprietary software licenses, and “those scary clauses” from employment contracts. This article is about mixing and matching open source and proprietary licenses.

Ridiculous Fish have a most wonderful article about how floats are stored and what numbers they can and can’t represent.

“The Waterfall Alliance” have produced a wonderful web site, advertising the Waterfall 2006 conference, with wonderful tutorials like “Pair Managing: Two Managers per Programmer” by Jim Highsmith. Take a look at their site, it’s full of ideas that probably achieve something… Not programming, but something.

In his article, “Making Wrong Code Look Wrong”, Joel discusses the idea that besides having some style, whatever it might be, a key to good programming is to engineer the conventions for a project so that wrong things look wrong. This can be done by organizing code so that the main consequences of a line of code, and the semantics of the line of code, are visible locally, without having to search around the program to see what’s really going on.