This is the last in my four-part literate programming series: What is it? Problems and challenges Modern variants Closing thoughts (the rest of this article) As I’ve developed my understanding … Continue reading Literate programming part 4: Closing thoughts
Literate programming (LP) hasn’t taken off, despite its promises to developers. After my previous posts understanding literate progamming itself and looking at some possible challenges and problems, in this post … Continue reading Literate programming part 3: Modern variants
In part 1 of this series I looked at the promise of literate programming (LP), created by Donald Knuth. It seems to be a fairly simple idea to promote good … Continue reading Literate programming, part 2: Problems and challenges
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?
The other day I was having a conversation with someone about requirements and software design. We had a description for a small system, and I was saying “this is the … Continue reading Requirements are entangled with design
One thing I often say to people I work with is, “If you need an FAQ you’ve done it wrong.” This idea stems from a blog post I read ages … Continue reading If you need an FAQ you’ve done it wrong
I’ve often come across a situation where a team needs to undertake a major refactoring or some other technical change, which may take in the order of days or weeks, … Continue reading The word puzzle analogy for technical changes