Embarrassing confession: I still don't have a real test suite for this project. With agents writing more and more code, that's starting to feel lik...

Results from agentic workflows reward good management approaches. The obvious ones are: Clear instructions, Proper Context, Actionable Feedback. Bu...

Me: Excited about voice mode in Claude. Coding from everywhere. | My wife: May be work can stay inside work. | Capitalism: Flinches.

If the vocabulary is fuzzy, the instructions for the agents will be fuzzy. And the output ambigious. Clarity starts with words. Time to start build...

Built technical resource for structuring agentic workflows. 7 Chapters. 12k lines. 6 agents. 1. The future is extremely token hungry. 357k Tokens.

I once thought photography was an expensive hobby. Now building software doesn't feel too different. Except this one just guzzles gazillion tokens.

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.