One thing we talk a lot about is how important it is, for costs, to stick to problems which have already been solved. Get fancy and do something new, and your costs have rocketed away. A developer has just done a nice little piece on spellchecking. In 1984 it was ferociously hard. In fact, if you wanted a decent spellchecker… continue reading ⇢
Archive for June, 2008
It’s hard to measure the cost of code. Simple stuff can be ferociously time-consuming to develop, and bad coders often produce reams of poorly structured code. But let’s assume you’re dealing with a typical, decent developer who doesn’t take the long route, or dangerous shortcuts.