Skip to content

Study Journal 31-07-2024

Published: at 12:00 AM

What I reviewed:

Where I’m at:

What I learnt:

Readme Driven Documentation

Working through the design documents makes you really think deep down what exactly it is that you’re trying to accomplish. It makes software design a lot easier, rather than making design choices as you are coding.

Coding for the sake of coding might start off well. But it comes back to the idea that organising feels good, but the productivity is fake.

But we also need to avoid over-organising.

The problem is that while thinking through abstractions methodically (e.g. literate programming a la Readme Driven Documentation) and staying in the abstraction domain it is easier to think through problems more thoroughly.

The problem is that we cannot foresee the miriad of issues that prevent our initial implementation / planning. We can expend intense efforts to produce exhaustive documentation first, but what if we cannot implement our documented design?

We now have a miriad of changes in documentation we have to work through, and that’s if we understand them all! Which we very likely do not.

Miscellaneous stuff

What I did:

Consider supporting this blog