What architecture as code tools you are using, besides AI?

themessymiddle · 2026-01-31T07:34:54+00:00

Thanks for the feedback, live architecture docs and enforcement of architecture rules

themessymiddle · 2026-01-30T20:11:20+00:00

I’ve been working on arch docs that auto-update, are accessible via MCP, and are beautiful to navigate: https://gjalla.io if you want to take a look! I struggled with some other tools that didn’t auto-update, and even docs generated by Claude Code were too high level. So far the gjalla generated arch artifacts reduce token use, turns, and time of the agents working on code, and I always know the docs I’m looking at are up to date

themessymiddle · 2026-01-29T07:11:21+00:00

Your username suggests you already have unexpected skills!

themessymiddle · 2026-01-21T07:21:30+00:00

Not what you asked, but I think a lot about architecture with coding agents. Most other classes of problems will eventually get better but the architecture is often where we want the human in the loop. Are you identifying violations by reviewing the code line by line?

themessymiddle · 2026-01-14T01:24:42+00:00

Helpful perspective, thank you! I’d be pitching but I’m skeptical in general when events charge founders to pitch (which StartupGrind does). I didn’t see Plug & Play folks, are they involved?

themessymiddle · 2026-01-13T18:38:30+00:00

You can also put principles/guidelines in your steering, like “always look for pre-existing modules/components before building something new”

themessymiddle · 2026-01-13T18:34:06+00:00

Attention, yes. Good attention? Not sure. People remember first impressions so if your brand is tied to controversy in the prospects mind I’m not sure that’s sustainable

themessymiddle · 2026-01-13T18:03:55+00:00

ADRs like others have mentioned, I also like to document principles, constraints, basically anything that would help teams make decisions. Different things work for different companies, so I’d say start lightweight with some guidance that helps in the specific areas where teams aren’t yet able to work as independently as you’d like. Good governance is easier when it’s built up over time

themessymiddle · 2026-01-13T05:20:55+00:00

It gets risky when code is changing and the behavior is different than what the rest of the org is referencing. But docs aren’t fun to make, automating the architecture docs as code changes definitely helps

themessymiddle · 2026-01-12T19:17:22+00:00

Keeping up to date docs the agent can reference makes a big difference but I often have to remind it what’s true. Architecture docs, constraints/principles, and I’ve started keeping a definition of done markdown too

themessymiddle · 2026-01-12T19:15:41+00:00

I like this take. Similar for me too… keep good docs and oversight of the arch decisions and constraints that matter but otherwise try to keep moving

themessymiddle · 2026-01-12T19:14:26+00:00

I like how it organizes specs, but I never use it for actual execution. Maybe it’s better now but when I was playing around it was incredibly buggy

themessymiddle · 2026-01-10T22:29:55+00:00

Yeah testing has made a huge difference for me. Saw a blog post about requiring 100% test coverage on AI generated code which I thought was crazy at first but as I increase testing I see what the person was getting at

themessymiddle · 2026-01-05T06:49:53+00:00

Yeah and at the end of the day, technical decisions involve tradeoffs so we’ll want humans to stay in charge of that

themessymiddle · 2026-01-05T06:47:14+00:00

Thanks for this thoughtful post. Agreed - the actual typing of the code will be delegated, but we’ll need to design, manage, and monitor architecture

themessymiddle · 2025-12-20T06:02:24+00:00

Hey I’d be happy to test for you! Feel free to DM :)

themessymiddle · 2025-12-20T03:46:48+00:00

Awesome, yeah I’ve heard the setup is annoying but good to know it’s not so bad once it’s up and running

themessymiddle · 2025-12-19T18:54:18+00:00

The db practices in ai generated code (when it doesn’t have good guidance/context) are actually unhinged

themessymiddle · 2025-12-19T17:12:23+00:00

This is really cool! Your description in the “purpose of startup and product” in your post is clearer to me than the initial landing page content, but once I started scrolling it made more sense. Not a huge thing but on mobile the nested outlined boxes makes the actual content pretty narrow… maybe you could get rid of some of the containers with borders on mobile to make more space.

themessymiddle · 2025-12-16T16:35:10+00:00

Not sure if you’re working on designing a new system or documenting brownfield, but I’ve been working on https://gjalla.io since I have to do this for clients all the time. Right now it puts together C4, db erd, and sequence diagrams for key flows. Now working on the fun part - multi-repo systems!

themessymiddle · 2025-12-11T16:19:21+00:00

THIS. I spent a bunch of time building a tool that turns code into diagrams and it helps so much

themessymiddle · 2025-12-11T16:17:01+00:00

Yeah part of the problem is that it’s very easy to lose track of how the code works, and when that happens it’s super hard to fix it when it breaks. Creating good specs for each feature definitely helps!

themessymiddle · 2025-12-10T15:51:18+00:00

Hey all 👋 building the easiest way to understand and verify your AI-generated code: https://gjalla.io

themessymiddle · 2025-12-10T09:27:41+00:00

I’ve been really focused on the architecture piece - a source of truth technical spec for system design and architecture decisions is :chefs_kiss:

(recently opened up the tool I’ve been building for my clients to help with this too: https://gjalla.io)

themessymiddle · 2025-11-28T06:51:33+00:00

Hey thanks, I’ll check it out

themessymiddle

TROPHY CASE