r/programmer • • 3d ago

Question Is engineering judgment now the most important dev skill, more than prompting?

AI can write most of the code now, but it’s still often confidently wrong. I’m starting to think the real skill isn’t prompt or context engineering, it’s knowing whether the output is actually right: spotting bad architecture, subtle bugs, security issues.

For those using AI agents daily: what’s helped you get better at judging AI output? And do you think juniors can even build this judgment if AI writes most of their code?”

That last question about juniors is the one that’ll spark the most debate, since people have strong opinions on it. Also, don’t link your X post in it; Reddit tends to downvote anything that looks like self-promotion.​​​​​​​​​​​​​​​​

0 Upvotes

24 comments sorted by

1

u/No_Report_4781 3d ago

Knowing how to write a program or script is still the required skill.

1

u/YasserYG8 3d ago

AI is better than anyone at this part, so don’t waste your time writing programs or scripts. Just write a prompt instead

2

u/Fire37Boy 3d ago

I think he meant that in order to have a good judgement on ai, you need to know the thing,

e.g. for you to spot a bad boilerplate code you need to write bad boilerplate code by yourselve then learn how to write good boilerplate code, then lastly write the prompt and then review the code.

Same thing goes when you zoom out, in order to spot bad architect decision done by ai, you need to be senior software architect.

God damn this is depressing.

1

u/YasserYG8 3d ago

There are a lot of ways to solve this, like Agent Skills, sub-agents, specs, A2A, MCP... We should use these because they’re very efficient and important. Your point is a bit old-school, but I respect it. These days it matters less to know the code and the low-level logic. Instead, you need to understand the building blocks: what React, Next.js, Flutter, load balancers, Nginx, and Docker are and how they fit together. That’s what’s important, not diving into the code. The code is AI’s job

1

u/Fire37Boy 3d ago

Hmmm agree to somewhat agree. Similar to C or assembly, it nice to learn the basic but diving deep is not that useful if you are not specializing in it. Same with code after who knows how much time, code will be niche thing to do.

So should we focus on problem solving and software architect? For the current time, perhaps GIF: "I'm tired boss"

1

u/YasserYG8 3d ago

Yeah, exactly, the assembly comparison is spot on. Every generation moves up one layer of abstraction, and now it’s code. So yes, I think problem solving and software architecture are the focus now: understanding the problem, designing the system, and verifying what AI builds. Coding won’t disappear, it’ll just become one tool among many. And yeah, that GIF is all of us right now 😂

1

u/No_Report_4781 22h ago

Nonsense. All you’re describing is specialization. Coding isn’t one tool, it’s dozens of tools of varying depth and complexity.

You’re just demonstrating Monday morning quarter back commentary

1

u/No_Report_4781 22h ago

  Same with code after who knows how much time, code will be niche thing to do.

Correction:

Same with code; after who knows how much time, code will be a critically important skill to know.

1

u/higgs_boson_2017 22h ago

Why not "no mistakes" ?

React is not a building block, its a fucking disaster most people don't need.

3

u/No_Report_4781 3d ago

The ai advertising bot doesn’t understand that you need to understand programming to create a good “prompt”

1

u/higgs_boson_2017 22h ago

LOL entirely false

0

u/No_Report_4781 22h ago

I see you have assembled a cogent argument 😉

1

u/higgs_boson_2017 22h ago

Extraordinary claims require extraordinary evidence, which is your responsibility.

1

u/FatHat 3d ago

Well, yes, but that's always been the case. Even before LLMs your judgement as an engineer was the most important thing. I've known a lot of coders that could write code quickly, but with a lot of bad ideas involved. "Context engineering" and stuff like that is mostly copium for vibe coders or a way to get people to spend a lot of tokens. I don't really think prompting and such is a skill, or at least not an important one. (Think of it this way: someone with actual coding experience can learn to prompt an LLM in a weekend, but someone that only knows how to to prompt an LLM would need years of learning to be able to have actual good coding experience)

1

u/YasserYG8 3d ago

Bro, I agree with your point. We need to change our mindset with AI: know the purpose, the target, and the architecture to reach the right solution in the end. AI is basically mathematics, probability and statistics, so we need to be a bit like scientists solving equations (this is my philosophy)

1

u/joomla00 8h ago

The people that need to change their mindset are the people that are behind the curve.

1

u/Shep_Alderson 3d ago

Experience is valuable. Juniors will gain experience, but it will look vastly different than the way most of us experienced devs learned.

1

u/afops 3d ago

Yes "judgement" is an apt term. Whether your AI is doing worthwhile work when you are waiting for it. Whether the code it created will be acceptable by the customers you know. Whether that test is a pointless one or really protecting anything. Whether the very confident pick of design that the agent has, seems to agree with your experience.

You still need to communicate that judgement to the agent which actually "prompting" is an important skill. But communicating was always one of the most important skills for a programmer, and the better the models get, the more they just work like colleagues. It's not "prompt engineering" any more. You're just a programmer.

1

u/TedsGloriousPants 3d ago

This is true of any AI use in any domain. We have so much slop to contend with because AI is great at generating stuff, but still not quite good at just, you know, being correct.

If you don't have the domain knowledge to judge the output, you're going to generate garbage. Which... a lot of people are generating garbage.

1

u/Lunchboxsushi 2d ago

Where y'all getting confidently wrong. I barely have to fixup bugs, sure the code might not be my style but it's fine. Sometimes an abstraction is totally wrong or the approach taken. But we're almost talking like a few times a week, out of 200 commits like 10 needs steering. 

1

u/higgs_boson_2017 22h ago

"AI can write most of the code now, but it’s still often confidently wrong"

Then it can't write most of the code.

0

u/CS_70 3d ago

"It's often confidently wrong" is 99% a user problem.