3 ms·
> AI can't replace a decent newgrad. It literally can't find a React import and cannot be relied on for anything without a human double checking it, which takes
by mrshadowgoose 3y ago
> AI can't replace a decent newgrad. It literally can't find a React import and cannot be relied on for anything without a human double checking it, which takes as long as writing it yourself, when it comes to line-of-business applications.
This is little-picture, short-sighted thinking. A one-for-one replacement of a specific kind of employee is not a requirement to statistically displace employees across a workforce. AI tooling can augment the productivity of existing employees, which results in a lessened need for human labour. And you're making the baseless assumption that we have achieved the pinnacle of AI development. This problem will only get worse as AI tooling improves.
- enriquec 3y agoI would say this is archaic, luddite and unambitious thinking. Did the need for labor decrease after the lightbulb, electricity, or the telegraph? Or did Quality of life go up while projects expanded in scope and we accomplished greater things with more efficiency?
- mrshadowgoose 3y ago> Did the need for labor decrease after the lightbulb, electricity, or the telegraph? Or did Quality of life go up while projects expanded in scope and we accomplished greater things with more efficiency? It absolutely did...and you literally said it yourself. What is "more efficiency" except a reduced need for labour for a fixed unit of "productivity"?
- throw1234651234 3y agoLet me be more specific - as an architect working on a senior dev task today, it's faster for me to type out the code / figure things out then prompt ChatGPT to do the problem. I actually have it pulled up all day in vain attempts to use it. So far I had it remove access modifiers and {get; set;} from a property list so I could copy it into a UML diagram. In reality, it would have been faster if I just remembered the shortcut.