It's all about the test suite. The test suite becomes an executable specification, and the better the spec, the better the results you can get from AI.

Regarding speed - now it takes much less learning to use a fast web framework(like Meteor), this means web based software will be more performant.

Regarding security - i wonder: can we develop a framework that is responsible to 100% of the security, with zero responsibility for security on the app developer?

Aha, the problem is you're asking for code that works.

I cannot imagine how nitpicky people are. AI went from 'good autocomplete' to 'I just tell it to do an entire thing and it does it and it works the first try'.

Maybe pick languages that are more boring. That's what works for me. It worked for hiring crappy outsourced programmers and it works for AI. It seems to do well with PHP - no long running processes / side effects. it works great with golang, simple language spec, and a very common style of writing.1

[flagged]

[dead]

I feel like I’m reading a post from 2025 instead of one written three minutes ago.

People get entrenched in closedminded thinking. My guess is that this has been your canned spasm for the past year. Repeating these things won’t make them true or protect your job.

You protect your job by learning how to use new tools as the technology advances.

This sort of lazy thinking isn’t acceptable anymore. Whether this is a reflexive Luddite response or a reflection of your work ethic, neither is a good look.

> Yet when I ask for code

Engineers don't ask a tool to write code.

Skill issue.

The fact is that with the right spec, agentic guardrails, and evals, frontier models can now one-shot secure, performant code.

This is the job of software engineering now. Learn to properly use the tools for the job.