In real code, so after the first week of development, typing really isn't what I spend most of my time on. Fancy autocomplete can sometimes be right and then it saves a few seconds, but not nearly 50-100% added productivity. Maybe more like 1-2%.
If I get a single unnecessary failed compile from the autocomplete code, it loses me more time than it saved.
But it does feel nice not having to type out stuff.
That's why all research on this topic says that AI assistance feels like a 20-30% productivity boost (when the developers are asked to estimate how much time they saved) while the actual time spent on the task actually goes up by 20-30% (so productivity gets lost).
You know, that's really close to the original way gendering was done in German.
There used to be separate word endings for male and female, and if you don't care you'd just skip the ending. IIRC it was "Bäcko" for male, "Bäcka" for female and "Bäck" for "I don't care as long as I get good bread".
The vovel shift then changed -o and -a both to -e, and then there was no gender marking at all. The modern -in ending for female forms only originated in the 16th century to make women more visible in the language.
That's why German doesn't have symmetric male/female variants but only a generic and a female form. As in, if you say "Bäckerin" it's clear you are specifically only referring to women, while "Bäcker" doesn't clearly mean you are only referring to a man.
To be honest? I don't care how an honest innovator is supposed to survive. It's not my responsibility to risk my sanity and my financial stability for someone else's dream.
I spent long enough in a crappy startup. Not doing that again.
Also, it's not exactly fair to lump youtube in with the average startup that any random person will work in. Youtube was created by three super rich ex-Paypalers and within a year it was big enough to be sold for €1.3 billion. It was basically founded as a mega corporation, including everything that a huge corporation requires (structures, HR, good salaries and so on).
Can't find anything on canonical's history.
While Youtube was technically classified as a startup, it's a far cry from the average 5 person startup that you'll usually find when talking about startups.
Why bigot? If you agree that startups suck, why would that make me a bigot?
Startups are ok if it's your first job and you have no other choice or if you own them (or at least a significant share of it). In any other case it's a ton of work in a volatile environment without any safeguards against abuse for very little pay.
Mhm, and those academics were no IT people and had nothing to do with computers?
Let's fact-check that.
Computer Sciences as an academic course was first created by IBM at the Columbia University in 1946. Because IBM had made their first commercial computer two years prior and wanted to have people who could operate it and who could continue to develop it.
Same with programmers. Of course I don't have the documentation of everything I use memorized. But my skill is to understand what I am reading, figure out what is trash and what is useful and then apply it to the situation in front of me.
Same as a doctor would do when googleing the specifics of medicine and conditions.
But did the elevator operator get replaced by a humanoid robot pulling the lever of a formerly human-operated elevator?
That's what they person before you was referencing. In most situations a simple computer-controlled mechanism is enough. If that's not enough, a non-humanoid robot trumps a humanoid robot. And in situations where a humanoid shape is really necessary, human labour is really cheap.
Humans don't have their shape because it's the perfectly ideal form, but because evolution always only iterates on what it has.
Btw: automatisation happens because either using a full human for a simple task is overkill (e.g. your elevator operator example) or because humans really aren't the optimal shape (e.g. using a robot arm to lift a car during production). If a humanoid shape is required, humans will do the job.
In real code, so after the first week of development, typing really isn't what I spend most of my time on. Fancy autocomplete can sometimes be right and then it saves a few seconds, but not nearly 50-100% added productivity. Maybe more like 1-2%.
If I get a single unnecessary failed compile from the autocomplete code, it loses me more time than it saved.
But it does feel nice not having to type out stuff.
That's why all research on this topic says that AI assistance feels like a 20-30% productivity boost (when the developers are asked to estimate how much time they saved) while the actual time spent on the task actually goes up by 20-30% (so productivity gets lost).