Interesting Reads
Curated articles across programming, music, politics, and more. The ideas that shape how I think about technology and the world.
Gregor Riegler · Levels of Modularity
This document presents a 'Levels of Modularity' model that categorizes software architectures from -1 (Distributed Monolith) to 4 (Microservices), where higher levels indicate better modularity through increased cohesion and reduced coupling. The model serves both as an assessment tool for evaluating current architecture and as a step-by-step cookbook for incrementally refactoring from monoliths to microservices. The key insight is that you should progress through each level gradually rather than jumping directly to microservices, and that higher modularity comes with significant costs that may not always be justified.
Read ArticleVibe coding for teams, thoughts to date
Main takeaways - LLM's will attempt to solve the problem at hand, but not necessarily in the way you would like them to. E.g. creating a new function, which already exists in some other form in your codebase. How to solve this? - Highly productive engineering teams (historically) reach that productivity by building a deep expertise in their tool chain. -> So investigate every tool you want to add to your stack. - Current LLMs lower the cost of writing the code, what about the cost of reading, maintaining, debugging, etc?
Read Article