Thanks, I will check it out.

Job security for those of us who think like this.

Two layers vibe coding can't touch: architecture decisions (where the constraints live) and cleanup when the junior-dev-quality code accumulates enough debt. Someone has to hold the mental model.

Although I write very little code myself anymore, I don't trust AI code at all. My default assumption: every line is the most mid possible implementation, every important architecture constraint violated wantonly. Your typical junior programmer.

So I run specialized compliance agents regularly. I watch the AI code and interrupt frequently to put it back on track. I occasionally write snippets as few-shot examples. Verification without reading every line, but not "vibe checking" either.

I like this. The few-shot example snippet method is something I’d like to incorporate in my workflow, to better align generated code with my preferences.

I have written a research paper on another interesting prompting technique that I call axiomatic prompting. On objectively measurable tasks, when an AI scores below 70%, including clear axioms in the prompt systematically increases success.

In coding this would convert to: when trying to impose a pattern or architecture that is different enough from the "mid" programming approach that the AI is compelled to use, including axioms about the approach (in a IF this THEN than style, as opposed to few shot examples) will improve success.

The key is the 70% threshold: if the model already has enough training data, axioms hurt. If the model is underperforming because the training set did -not- have enough examples (for example hyperscript), axioms helps.

Been saying this for years about frontend environments too. My genx.software does the same thing with declarative HTML attributes instead of imperative JavaScript config. Zero setup, zero sync bugs between what you declare and what you get.

It is like the airplane with the bullet holes meme; looking in the wrong places, asking the wrong questions.

The REALLY interesting question is: why does this guy have ANY intelligence and consciousness at all? https://www.sciencealert.com/a-man-who-lives-without-90-of-h...

I can't help you now, but for next time:

Preventive measure: get Scrum Master certified yourself. The training can even be fun with a good instructor.

Then when professional managers come sniffing around muttering about Scrum, you say: "I am a certified Scrum Master. Our process is already 100% Scrum.

Interesting strategy. I've thought about getting certified just to have the credibility. The irony would be certified Scrum Master saying "we don't need full ceremony right now" harder to dismiss as "doesn't understand Agile."

Smart defensive move.

The key to success in the world of coding assistants is to be a good manager. The AI is a very fast, but also very stupid, programmer. It will make a ton of architectural mistakes, and AI, more often than not pick the most mid solution possible. If you are a good code architect, and if you can tell the difference between a mid pattern and a good one, and force the AI to do things right, you will rise to the top.

Yes but I am jr. dev so there are certain implementations which I have not seen or not been familiarized with which is why there are times where it's difficult for me to notice certain code which might break in future for certain cases but due to my inexperience it is a bit difficult to catch it.

I admire your honesty. I suspect that attitude will take you far.

Exercism.io is excellent for exactly the experience you're seeking. The mentored tracks force you to see multiple solutions to the same problem, which builds pattern recognition faster than production work alone. You start noticing when code "feels" fragile before you can articulate why.

Mill's declarative build configs are just right.

You describe what you want, not the 47 imperative steps to get there. Zero chance to call methods in the wrong order or manage intermediate build state that should never be your problem anyway.

IMHO All libraries should use declarative interfaces.

This is exactly right. Client-side processing for sensitive data like contacts eliminates the trust problem entirely. Most migration tools want you to upload your entire contact database to some random server when the extraction can happen locally in milliseconds.

Pure client-side tools like this should be an option for any personal data processing.

This is what I have done for my users: an option to import their emails to an in-browser db for guaranteed privacy.

Building a production app on Turso now. No bugs or compatibility issues so far. The sqlite API isn't fully implemented yet, so I wrote a declarative facade that backfills the missing implementations and parallels writes to both Turso and native sqlite: gives me integrity checking and fallback while the implementation matures