The Essence of Software: Why Concepts Matter for Great Design
A summary of Daniel Jackson's work on conceptual modeling and why clarity of underlying concepts is vital for robust software design.
I like reading a lot and sometimes I read technical books which I found very very interesting.
Since one of the best tools for me is the elaboration / summarization of concepts found in the materials I study, I decided to write some articles.
My purpose was not to write a full comprehensive summary of the book, but to squeeze out the most interesting part (for me): If I want to come back to a particular thing I can still re-read it :)
By trying to find out the main address (alas: there may be more than one!) of those books I wanted to to pursue two goals:
The books you’ll find here are chose by personal taste only and are related to technology at large: you won’t find an article regarding a programming language book or kubernates or AWS for example. Those kind of books ages too fast.
I would say I am looking for books that would be worth to have on paper rather than in digital edition ;)
Some articles are not new: they were previously published in Medium / Dev.to / and my last company’s tecnical blog.
Versions you’ll find here are the most updated.
A summary of Daniel Jackson's work on conceptual modeling and why clarity of underlying concepts is vital for robust software design.
A summary of Kim Scott's framework for giving and receiving feedback, balancing caring personally with challenging directly.
A summary of Felienne Hermans' insights into how the brain learns, reads, and processes code, offering strategies for improving programming skills.
A summary of John Ousterhout’s core philosophy, focusing on reducing complexity as the central challenge in software design.
A summary of Cyrille Martraire's foundational work on aligning code, tests, and documentation to create living, always-up-to-date knowledge.