Why subscribe?
Khola.Blog is about post-human engineering: software systems after code generation stops being the hard part.
The industry is learning to produce code at machine speed. That does not make software engineering easier. It moves the bottleneck. The scarce skill is no longer typing the implementation. It is knowing which abstractions hold, which invariants matter, which failure modes escape the demo, and where the system will pay the physical bill.
I read foundational software books as source material, not as nostalgia. CLRS, SICP, The Pragmatic Programmer, design patterns, distributed systems texts, architecture books, reliability handbooks: each one carries an old promise about how software should be built. I test those promises against modern production.
That means asking questions like:
What does this idea become when an agent writes the first draft?
Which invariant does the generated code have to preserve?
Where does the abstraction stop paying rent?
What happens when the happy path meets retries, queues, caches, control planes, and partial failure?
Which part of the theory is still binding, and which part is only a teaching model?
This is not a book-summary publication. The books are the lab bench.
The real subject is engineering judgment in a world where code is cheap, context is fragile, and production still has physics.
Subscribe if you want technical essays that treat classic computer science as living material: useful, dangerous, incomplete, and still worth arguing with.
Subscribe to get full access to the newsletter and publication archives.
Stay up-to-date
Never miss an update on systems architecture, distributed data, and engineering pragmatism. For a spam-free, ad-free reading experience, plus audio and community features, get the Substack app.
Join the crew
Be part of a community of people who share your interests. Participate in the comments section, or support this work with a subscription.
To learn more about the tech platform that powers this publication, visit Substack.com.
