Previously I’ve written about Niels Malotaux’s drive for zero defects. One of his principles (and the IBM Clean Room approach) is that any failure, such the as the discovery of … Continue reading Literate programming part 1: What is it?
For the last couple of weeks my wife has been trying out an electric pedal bike, as part of an environmental scheme to promote awareness and—it is hoped—adoption. Electric bikes … Continue reading Beware the peripheral variables when evaluating technologies
Some time ago I wrote about the error of slavishly following “best practice” without asking why. And I was reminded of this again the other day when a friend forwarded … Continue reading An example of the errors of “best practice”
The other day I was looking at some old Elm code, refamiliarising myself with one of the key language concepts (Signals) and found an article to help me. One part … Continue reading Plan for legacy systems
When a development team introduces new technology to solve a problem, they are adding a long term cost, too, even though it may not be obvious. This is one way … Continue reading The cost of new technology
Many years ago an experienced consultant was telling me about a company who was asking for his help. “They told me they wanted to develop a digital strategy. But they … Continue reading Follow the business strategy
I’ve been having fun this week watching some conference talks about my current favourite language, Elm, at Elm Europe 2017. And I enjoyed seeing an important idea discussed—important not just … Continue reading Always build for real people’s real problems