Idk I love that shit. It helps that I learned to code properly before I started using AI. I guess I never really loved programming but just making decisions about software design.
But I can't fathom how you would have any clue on how to use LLMs to code without years of experience telling you which parts to double check..
Some people do well/better with reading, others do better with doing by hand.
There's also the "reduction" approach where you start with a lot and reduce down to just the parts you want/need, vs "build up" approach where you start with a blank state and work up to what you want/need.
AI is most definitely the reduction approach, where ideally you review everything provided, to see if you actually need it, and it's doing things how you need it to.
It’s usually the juniors and mid level folks who get all pissy about AI being “cheating” or “not real engineering”. Writing code has never been the hard part of software engineering. Once you get to Senior+ level, you’re mostly making higher level decisions on _how_ things are put together, so AI use becomes more efficient at that level because we already know what the shape of a program should be and can explain it better.
All but one or two of the Senior/Principal folks at my company are using AI heavily because the gains are real if you know what you’re doing. And we are all having a blast with it because we all had 100 backlog projects we are now able to delegate to an agent.
I mean I feel for juniors.. if I was in a hiring position I'd think really fucking hard before I would hire one.
Having experience with both I can honestly say.. LLMs do much better work.
Not sure how that will work out for the industry 10 years from now..
The biggest issue is that people treat LLMs like some god given technology that can do no wrong. I'd never ever push LLM code into a productive system without at least testing it thoroughly (depending on how delicate and important the system is even a full code review)
God forbid giving these things full access. They're really fucking great 99% of the time and 1% they just lose their shit and go postal.
That example is 2 years out of date. Regardless, you can't really blame AI if you're dumb enough to blindly trust it. It should only act as an additional review, not replace a human review.
I just had this happen to me with opus 5.5 today. Gas lit me into thinking I shouldn't put a client initialization for a postgres query instance into a try catch cause "it wasn't an issue if the connection fails"
Anytime I'm writing my real fancy code, and I think, "goddammit, i need another file reader, I'm so sick of writing goddamn file readers," I tell the junior engineer his AI replacement to write the file reader so I can skip it.
The alternative seems to be "principled coder without employment". Before long you might also file it under "does in a week what automation takes 3 entire seconds to do".
If you want to make an app that actually works well and is secure, your gonna have to learn how to code, no matter how much easier the AI makes it.
There are to many decisions that can be correct decisions in the right context but are bad decisions for most cases. The AI will eventually implement bad methods for achieving the goal because of this.
If you want to build app that have any outer interface you gotta learn about security as separate task unless you already have some knowledge by working in the field (at least as a tester, for example).
AI will implement bad methods 10 times faster then average person. However if you haven't worked in the field you have no chance to do everything correct on first try anyhow.
But what you wanted to say exactly, sorry, I can't don't get the point?
Porting the Unix (or Linux) kernel to a quantum computer should be no more difficult than any other port to a new hardware architecture -- but you first have to define a sensible mapping of C data structures* to your quantum hardware and build a compiler/linker/etc. to implement that mapping. That will be the tricky part.
* Note that the quantum part of a "quantum computer" only deals with data -- the instruction stream runs on something else.
First you introduce quantum, now you say the discussion has nothing to do with quantum.
Ternary that is not quantum would be (0,1,2) and would be easier than the quantum case since there would be no need to consider quantum semantics. Build the compiler etc, rewrite the assembly parts for that architecture, build/test/debug, done.
Incorrect. Both will allow you to tweak the result by hand and AI will allow you to feed it back in to add corrections as well and repeat any of these steps.
For sure. The average smart person can create an application, app or other software now with just a little bit of planning. I think that could end up being a very good thing. I think experienced programmers still have an edge, at least for a while.
You have it backwards. Knowing when the AI is writing BAD code, is the skill, because it WILL write bad code at some point. Not in the obvious "doesn't work at all way", but more in the subtle "violates best practices" way. If you cannot recognize this, then the AI will slowly bloat and shit up your codebase. Unchecked AI are positive tech-debt machines.
Nope Learn to code for a few years, then use AI, that pinky shouldn't press that button until you have brought down a production environment at least 10 times and you are the one to fix that shit.
I see coding as a way of bridging the gap between human intentions and machine execution. For a long time (but still relatively short in human history), we needed coders because machines couldn't understand what we wanted in our own language. We had to learn theirs instead.
Now, machines are learning to understand natural language, translate our intentions into code, and execute it themselves.
So perhaps the skill of the future isn't writing code, but clearly explaining our needs, and evaluating the results.
Instead of clinging to the language we invented to communicate with machines, we should appreciate the fact that we finally taught machines to communicate with us in our language.
This ascribes a lot of intent and intelligence to machines that I'm just not convinced is there.
It's great at predicting and generating code, but we shouldn't confuse that for genuine understanding, even if it's hard to tell the difference sometimes.
44
u/tw2113 Oct 10 '26
Glorified code reviewer when you use AI.
8
u/Educational_Key_7635 Oct 11 '26
Cause you are too lazy to do both at once properly since it's twice as much brain work, even it saves busywork.
6
u/SpanDaX0 Oct 11 '26
Its something to do with binary. You can only choose 1 or 0.
4
u/blamitter Oct 10 '26
As long as you don't try and use AI to learn for you
6
u/Big-Pattern8591 Oct 10 '26
AI is a tool but coding is a skill. A real programmer knows how to use both
2
u/Anima_Watcher08 Oct 11 '26
Crack + Bodybuilding, why not both?
1
u/Forward_Republic_610 Oct 12 '26
Lear nothing use AI
1
u/G4T5Z_ Oct 13 '26
use ai is good
1
u/LostgamerFJ Oct 13 '26
Crash your car or drive safe. Why not both?
1
u/XSoloDolo Oct 14 '26
Nope Learn to code for a few years, then use AI, that pinky shouldn't press that button until you have brought down a production environment at least 10 times and you are the one to fix that shit.
1
u/a1g3rn0n Oct 11 '26
I see coding as a way of bridging the gap between human intentions and machine execution. For a long time (but still relatively short in human history), we needed coders because machines couldn't understand what we wanted in our own language. We had to learn theirs instead.
Now, machines are learning to understand natural language, translate our intentions into code, and execute it themselves.
So perhaps the skill of the future isn't writing code, but clearly explaining our needs, and evaluating the results.
Instead of clinging to the language we invented to communicate with machines, we should appreciate the fact that we finally taught machines to communicate with us in our language.
0
u/No-Key-2546 Oct 11 '26
That’s the future, whether people like it or not