← Back to context

Comment by xpct

1 day ago

I find it a bit comical. AI tools are so easy to pick up, and it's unlikely you've pushed some highly critical features which couldn't have waited for a few months.

You make a good point. That’s why there is AI fatigue. People are moving at speeds that aren’t normal and it’s mentally taxing.

If it’s not already a thing, it will be soon, the mental health aspects of all professions moving at unsustainable speeds and what that will do to people.

  • No stakeholder will care, they're high on the illusion they can drain a batch of people and then replace them with fresh meat.

    Nobody will take care of us. Ever.

  • > You make a good point. That’s why there is AI fatigue. People are moving at speeds that aren’t normal and it’s mentally taxing.

    I don't think any vague claim of "speed" has anything to do with fatigue.

    I do think the parallel world monitoring and validating N work fronts, followed by rounds of fixes where you lay there waiting for the agents to converge, is the defining factor.

    Instead of you hunkering down and hammering out a single task where your full attention can be focused 100% on a problem, your mindset is a kin to juggling N balls and hoping to not let any of which to fall.

    So it's not really about speed but throughput, and keeping up with the throughout rate is mentally taxing.

    • Reading, understanding and verifying code has always required more cognitive effort than typing it out. Running agents in parallel just forces you to spend 100% of your day doing the most taxing part of the job

  • I guess a shop can burn away his whole crew, no newcomers- and the old guard is burned out and quits- and the profession suddenly is just AI and managers yelling at AI realizing the job leads to burn out fast.