Three bullet points, each starting with a phrase in bold: instantly gives the game away. Maybe AI will augment coding, but it's not doing blog writing any favors.
And the Final Thoughts heading. LLMs love that as well.
The AI Revolution in Coding: Why I'm Ignoring the Prophets of Doom
11–17 of 17 posts
Re: The AI Revolution in Coding: Why I'm Ignoring the Prophets of Doom
#12A 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.
Re: The AI Revolution in Coding: Why I'm Ignoring the Prophets of Doom
#13A 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 peopl…
Labeling it "denial" does not refute any of the article. Would you care to actually address the content?
Re: The AI Revolution in Coding: Why I'm Ignoring the Prophets of Doom
#14Three bullet points, each starting with a phrase in bold: instantly gives the game away. Maybe AI will augment coding, but it's not doing blog writing any favors.
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 muc…
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.
Re: The AI Revolution in Coding: Why I'm Ignoring the Prophets of Doom
#15Earlier quoted context omitted.
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 muc…
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
Re: The AI Revolution in Coding: Why I'm Ignoring the Prophets of Doom
#16its 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?
Re: The AI Revolution in Coding: Why I'm Ignoring the Prophets of Doom
#17its 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?
It's probably his 3am vibe coding sessions