I’ve seen this claim recently and it’s rubbish.
Yes, if by “nothing” we mean writing next to no code, because they’re busy either:
- architecting software solutions, as they’re knowledgeable enough that they should be doing this instead of writing code
- understanding a lot of what is going on in components and/or the system so that when there’s an issue they say “oh, this is likely because of X” and the resolution takes days instead of weeks.
I.e. yes, there is a percentage of developers who we pile other tasks on and they don’t get to write code.
My experience is that the more knowledgeable developers get, the less code they write.
Then neurodivergent peeps are different - an Autistic dev might be super knowledgeable and happy writing unit tests because they don’t enjoy the uncertainty of large problems, or an ADHD developer might have a large system-wide view but write what seem like small contributions.
Two notes on this as someone who works in the sector.
It’s “completely normal”, but only if you’re not having a full time driver for each vehicle, which is what the article sounds like… Then the vehicles wouldn’t be autonomous, they’d just be teleoperated.
And the second part, why is this an industry standard and why are investors ok with it? Imagine you have a product (robotaxi) that is autonomous but can’t deal with absolutely everything on its own (not even Waymo is that advanced). The key component that you need to build into the system is the ability to come to a stop safely, and be recovered remotely. Then these “teleoperators” can recover the vehicles if/when they fail, and given a sufficiently low failure rate, you can have one operator for each X vehicles. Even if this is more than “0 drivers”, having 1 driver per 10 vehicles is a massive cost saving. Plus zooming out and thinking of other things than robotaxis, there are sectors like mining where they don’t care (that much) about the number of drivers - their primary goal is to have the drivers away from a dangerous mine. They can save money from simplifying operations that way.