There should only ever be ONE of this thing. Created once, shared across. Like a global config, db connection or a logger.

Projects and writing on agentic engineering, web development, software craftsmanship, and building systems that evolve | from Sumit Sute.

I built a Telegram bot for posting bytes and blips from my phone. Webhooks, singleton patterns, and a public channel that broadcasts my thoughts whether I like it or not.

Projects and writing on agentic engineering, web development, software craftsmanship, and building systems that evolve | from Sumit Sute.

test

The cost of bad structure is often seen in terms of scalability. It could actually be also a hesitagtion every time you need to edit something.

Code that translates user-facing input into application actions.

A contract surface, often an API, that reduces ambiguity between clients and the core system.

Good architecture compresses context. It lets an agent load the right truth without having to reconstruct it from scattered clues.

A design smell where one small requirement change from edits across too many places.