Amusingly, when I know my peer is just going to point his AI at my feedback, I write for their AI, not for them. I'm much more curt. Maybe not so amusing but I don't feel bad about dumping a laundry list of fixes for them.
> Amusingly, when I know my peer is just going to point his AI at my feedback, I write for their AI, not for them.
At this point, why not just talk directly to the AI?
Asking as someone who is likely leaving dev, and maybe tech completely, very soon, possibly to go wait tables, as he hates everything about the way things have gone in the last half decade or more with remote work, stupid levels of unnecessary complication everywhere (people architecting to be the next Amazon as soon as, or even before, they have three users, and just about every thing client-side), and now generative AI, and would rather be replaced by a Claude license and a monkey to use it than deal with generative AI & related agents himself…
I think three are far more of us than speak out. Most don't have the luxury of potentially committing career suicide by speaking their minds so openly within jobs where such thoughts would make them seem entirely uncommitted to the vision and therefore someone to be moved on.
At this point, why not just talk directly to the AI?
Asking as someone who is likely leaving dev, and maybe tech completely, very soon, possibly to go wait tables, as he hates everything about the way things have gone in the last half decade or more with remote work, stupid levels of unnecessary complication everywhere (people architecting to be the next Amazon as soon as, or even before, they have three users, and just about every thing client-side), and now generative AI, and would rather be replaced by a Claude license and a monkey to use it than deal with generative AI & related agents himself…