https://www.insidetechlaw.com/blog/2025/06/workday-ai-lawsui...
https://www.forbes.com/sites/janicegassam/2025/06/23/what-th...
I ended up building my own head hunting firm specifically to address the whole pipeline. That helped somewhat but head hunting is its own very odd space. Full of inefficiencies and bias.
With any AI company, there are always limits you hit. Energy, compute, optimizations, inference, team resources, money, and all the flows to make it a company. HR is usually the one that gets the fewest resources.
One day I decided to change my main disk and used the opportunity to rebuild everything from scratch and from backups. I was up in about an hour.
And then I spent a week fixing this and that, ah yes I changed that too and, crap, I cannot remember why this thingie is set up this way. And some more.
This is a one-man lab, with simple services, all on docker. I also work in IT.
Recovering from scratch a whole infrastructure managed by many people over the years is a titanic task.
I helped to recover my nearby hospital as a volunteer when it was ransomwared. The poor two IT guys over there has no idea how to recover and the official help was pityful.
I also helped with a ransomware attack on a large company. The effort people had to do to remember why something was that way, or just remember whatever was colossal. Sure a lot of things were "documented" and "tested" but reality hit hard.
I do think this article fully grasps that change. Using AI to do tasks is not vibe coding. At least to me.
When will the first vibe coding book come out I wonder?