Coding is a fascinating subject, unbelievably frustrating in practice for me. Systems thinking is cool.
As a construction guy, I had to laugh with the 'hammer and a saw' metaphor for building a skyscraper! Might have to upgrade to a crane and impact wrenches! ;)
The bulkhead metaphor for separation of concerns is perfectbecause it captures both the protection and the failure mode. The Titanic detail about the bulkheads not going high enough is exactly what happens when devs think they have isolation but implementation details leak across boundaries. Ive seen this in prod where a schema change in one service cascaded because teh "independent" services were secretly coupled through shared database views.
Coding is a fascinating subject, unbelievably frustrating in practice for me. Systems thinking is cool.
As a construction guy, I had to laugh with the 'hammer and a saw' metaphor for building a skyscraper! Might have to upgrade to a crane and impact wrenches! ;)
Thanks for the brainfood!
The bulkhead metaphor for separation of concerns is perfectbecause it captures both the protection and the failure mode. The Titanic detail about the bulkheads not going high enough is exactly what happens when devs think they have isolation but implementation details leak across boundaries. Ive seen this in prod where a schema change in one service cascaded because teh "independent" services were secretly coupled through shared database views.
I look forward to these posts! I’m curious how you might encapsulate this approach in a Claude.md file…