The AI Revolution in Coding: Why I'm Ignoring the Prophets of Doom(codingismycraft.blog)
codingismycraft.blog
The AI Revolution in Coding: Why I'm Ignoring the Prophets of Doom
https://codingismycraft.blog/index.php/2026/01/23/the-ai-revolution-in-coding-why-im-ignoring-the-prophets-of-doom/
16 comments
ya idk, structure screams AI and its a generic take, but i see no reason to assume anything beyond AI assistance especially in regards to the styling.
Personally I'd avoid a 2nd to last topic anywhere near resembling "reality check" into a clearly marked "final thoughts"... Even if i followed that sorta structure i would avoid # Reality Check style formatting simply because of the implication it gives off.
pretty much im hesitant to dismiss something as AI just because of bullet points.
Personally I'd avoid a 2nd to last topic anywhere near resembling "reality check" into a clearly marked "final thoughts"... Even if i followed that sorta structure i would avoid # Reality Check style formatting simply because of the implication it gives off.
pretty much im hesitant to dismiss something as AI just because of bullet points.
It's not any one thing, it's all of it combined. Very middling language, bold keywords, simple tricolon throughout, unnecessary em-dashes... If it's not AI, it's still mediocre writing with no substance behind it.
"Not only x, it's y" is an obvious tell as well.
> Software development isn’t just about outputting lines of code; it’s about solving human problems
> Software development isn’t just about outputting lines of code; it’s about solving human problems
You've found me, it's the guy that has been using this style that AI probably learned things from.
And the Final Thoughts heading. LLMs love that as well.
Yeah... I had to quit reading after seeing the No True Scotsman argument about who can and can't form an opinion on the state of the robots. I don't have any professional experience but feel like I can see enough, through experimentation using the daffy robots, to see what's happening but my only formal software education was when I was in high school in the 80s so I don't count.
And why do all these conversations center around web apps and whatnot? I don't work on anything like that but probably know a lot more about virtual machines and compiler theory than your average web programmer.
And why do all these conversations center around web apps and whatnot? I don't work on anything like that but probably know a lot more about virtual machines and compiler theory than your average web programmer.
> Medical AI: In 2016, Geoffrey Hinton—the “father of modern AI”—predicted that radiologists would be replaced within five years. We are now a decade past that prediction, and radiologists are as essential as ever.
This one is instructive. State of the art radiology image classification models match or exceed the performance of expert human radiologists.
But radiologists haven't been replaced... why?
The simplest answer is that classifying images is not all a radiologist does, and therefore cannot be replaced completely by a computer.
Radiologists serve as the human-in-the-loop to blame if something goes wrong. Also, there are myriad regulations in healthcare that slow or prevent the adoption of tools like this: FDA regs on medical devices, insurance stuff, professional associations, etc.
Like much of the tech world, the problem often isn't the tech, it's the context.
This one is instructive. State of the art radiology image classification models match or exceed the performance of expert human radiologists.
But radiologists haven't been replaced... why?
The simplest answer is that classifying images is not all a radiologist does, and therefore cannot be replaced completely by a computer.
Radiologists serve as the human-in-the-loop to blame if something goes wrong. Also, there are myriad regulations in healthcare that slow or prevent the adoption of tools like this: FDA regs on medical devices, insurance stuff, professional associations, etc.
Like much of the tech world, the problem often isn't the tech, it's the context.
A classic case of denial
Denial is a defense mechanism in which an individual refuses to recognize or acknowledge objective facts or experiences. It’s an unconscious process that serves to protect the person from discomfort or anxiety.
Denial unconsciously protects the ego from discomfort and distress by rejecting aspects of reality itself.
signs of denial
You find ways to justify your behavior. You blame other people or outside forces for causing the problem. You persist in a behavior despite negative consequences. You avoid thinking about the problem.
Denial is a defense mechanism in which an individual refuses to recognize or acknowledge objective facts or experiences. It’s an unconscious process that serves to protect the person from discomfort or anxiety.
Denial unconsciously protects the ego from discomfort and distress by rejecting aspects of reality itself.
signs of denial
You find ways to justify your behavior. You blame other people or outside forces for causing the problem. You persist in a behavior despite negative consequences. You avoid thinking about the problem.
Labeling it "denial" does not refute any of the article. Would you care to actually address the content?
its not even a prediction anymore, meaningful amounts of software engineering are already automated. really dont understand the point of these posts. its just people that are bad at using the tooling
> its not even a prediction anymore, meaningful amounts of software engineering are already automated.
I hear claims like this a lot, but I never see anything to back it up. Do you have any evidence that this is actually the case?
I hear claims like this a lot, but I never see anything to back it up. Do you have any evidence that this is actually the case?
It's probably his 3am vibe coding sessions
[deleted]
Sorry but this is clearly written by an LLM.
So impressed by your eye, I didn't see this
Maybe AI will augment coding, but it's not doing blog writing any favors.