I read a lot. I’ve noticed that some of the most effective books I read share a clear focus. Every point is quickly and explicitly tied back to a concise core message.
What core message would I reiterate if I wrote a book on software?
I strongly believe that programming is problem modeling.
This phrase could work, but I’d also like to connect into knowledge programmers already have. Preferrably also have the core message be an action statement for the reader to apply.
Programmers often call the core of the problem we’re solving the domain. A repackaging of problem modeling could be Reflect the domain
Reflect the domain
I’m not 100% sold this is the best phrase, but there is no doubt it describes how I program.
- Code design process -> Reflect the domain [1, 2, 3]
- System structure -> Reflect the domain [1, 2, 3]
- Writting tests -> Reflect the domain (specifically requirements) [1, 2]
- Naming any programming construct -> Reflect the domain [1,2]
- Measure of progress -> Reflecting the domain [1, 2, 3, 4]
A potential flaw with this core lesson is communicating the importance of understandability. Mark Seemann does a good job of that with Code That Fits in Your Head.
Speaking of which, here are examples of books that do a great job of connecting back to their core message.