At the end of the day, it is humans that control the bots.
I'm picturing you delivering this speech from a lectern in a 1950s sci-fi movie, and right at the end of this sentence the music gets really foreboding. And maybe even some heckler asks: "Yes, but for how long?"
But do you really want bob to be working 0 hours and have jack working 60-80 all the time?
Well . . . if bob is incompetent and turns out shoddy work, and jack is excellent at what he does, I'd rather hire jack. Certainly any
As a sysadmin, running the current version -1 is the safe bet for most businesses. The problem is that few businesses have an upgrade path, policy or methodology so you end up being current version -2 or -3
That tradition goes back to mainframes. One difference is that in the IBM mainframe days, a "version" came out every blue moon, thoroughly tested by an itty bitty monopoly, and justifying similar thorough testing by users; whereas today a "version" can arrive every few days (or faster for people who watch commits to the archive) and testing would almost be continuous.
... generate documentation based on the specifications and requirements.
What are these strange and mystic words you use?
It's like if your car wasn't acting right, and you took it to a mechanic, and he told you, "just read the fucking manual you idiot." Of course, that doesn't happen, because most-if-not-all mechanics aren't so arrogant they think everyone should know how to fix their own car.
Take it to the next step: Mechanics have realized that the benefit of others not knowing how to fix cars is that Mechanics have a skill for which they can ask to be paid. They can be as arrogant as they want about their superior car knowledge, as long as they don't tick off the paying customers. The programmer who has thrown his incomplete hack on a server and called it FOSS is not getting paid, and sees no reason to put in any "extra" effort.
The one day you'd sell your soul for something, souls are a glut.