u/mklfarha

I have been working this way for many years; I start modeling my schema and then take it from there, and it has worked for me.

I automated my process so that I can generate all the code for the CRUD operations, listing and so on, and then use that as a library and add my product logic on top.

I find that it speeds up development, adding a new entity or field is not as painful, and I fully control the core part of the application. I never use AI at this layer.

Does this speak true for anyone?

AI assistants are built for right now—to satisfy your immediate ask—without thinking ahead or designing the system with the future in mind. They'll happily write code against a column that doesn't exist or invent a slightly-wrong version of your schema.

But here's the thing I keep coming back to as an engineer: the most important part of building a system has never been the code. It's understanding what you're building, who it's for, and what the requirements are in the near and long term. Modeling the domain is the backbone of the architecture — and that hasn't changed with AI. If anything it matters more, because if the foundation is sane, your AI assistant can build on top of it instead of guessing at it.

So I built nuzur to make that foundation the source of truth. You model your data visually, and it generates the boring layers for you:

• SQL migrations
• a Protobuf / gRPC API
• Go server scaffolding

Change the model, regenerate—the generated code stays in sync, and you never hand-maintain it. Your own business logic lives in separate files it never overwrites. And because it's templated generation, not an LLM, the output is deterministic: same model, same code, every time. No hallucinations.

Backstory: I'm a solo dev. I originally built nuzur for myself years ago because MySQL Workbench made me want to throw my laptop out a window. As AI-assisted coding took off, the source-of-truth model I'd already built turned out to be a clean answer, at least that is what I think.

It's free for personal use (code generation included). I'd genuinely love feedback!

So, I have been exploring this approach and wanted to get some feedback

You start with the db schema, and make it the source of truth, then generate everything based on that.

so something like this:

model the schema -> generate proto -> generate go code + sqlc

the main issue I have found is that you need to be mindful when adding new fields if already in production to always add them at the end to not break things.

any other potential issues I might not be seeing?

curious, do you do anything like this to generate code? if so what is your source of truth?

I started working on my project in 2023, I have taken my time to do it right, mostly done with no AI, only started using it recently for minor stuff

I use it myself and I think it’s good, but I am having trouble getting to the right people

I am doing youtube videos, blog posts to help with SEO, I also tried an ad, but it’s not really getting traction, any recommendations?