2 ms·
> gathering requirements to communicating the changes. Right, but those are soft skills. They're important but they're not why SWE's make big bucks. SWE's make
by 2OEH8eoCRo0 3y ago
> gathering requirements to communicating the changes.
Right, but those are soft skills. They're important but they're not why SWE's make big bucks. SWE's make big bucks because as he says- it's a lot of hard work to gain the skills to turn an idea into instructions. That's programming.
At the bottom of everything it's just machine instructions. We have all these languages and conventions because humans need abstractions. When models get really good will we won't need programming at all. Tell the model what you want and it generates machine code directly.
- aldarisbm 3y agoAnd how do you debug it when it doesn’t work and the LLM can’t find the problem?
- 2OEH8eoCRo0 3y agoYou go grab the one SWE with an education on the whole team or contract it out.
- proc0 3y agoIt's not clear to what extent it's soft skills since gathering requirements often involves pushing back and negotiating what is possible on the technical level while at the same time taking into consideration organization goals and even market considerations. When it does get there, I would expect almost every other role to be completely automated. If you can just tell an AI the requirements and it just figures out the best way to implement it and release it, then I'd say we're very close to a singularity where machines will just take over civilization.