3 ms·
> I’ve fed it an example of how the low-level “assembly/opcodes” look like and then how I would like the higher level scripting language to look. With minimal g
by aprilthird2021 2y ago
> I’ve fed it an example of how the low-level “assembly/opcodes” look like and then how I would like the higher level scripting language to look. With minimal guiding (I was telling it what I want, but not how I want it) it implemented a working decompiler and compiler that worked exactly to my specifications, written in Typescript.
I think this already falls out of OP's guidelines, which you pointed out are quite strict. They also happen to be the guidelines an AI would need to meet to "replace" competent engineers.
- signatoremo 2y agoIf there used to be 10 engineers in a team, and with LLM they only need eight because LLM help the team achieve the same workload, then two of them have been "replaced", even though the LLM can't do everything an engineer does. I haven't heard of any prediction that AI will completely replace all programmers.
- M4v3R 2y agoExactly. The argument never was that AI will replace every single programmer. But it looks like it will replace a good chunk of them. How many exactly remains to be seen.
- aprilthird2021 2y agoThis doesn't make sense though unless your company isn't growing. Most dev teams have large backlogs of work and any increase in productivity can lead to an increase in revenue generation. Programmers aren't paid to generate code. They're paid to figure out how to do X Y and Z business initiatives. Unless you don't have that many initiatives, how much sense does it make to let go of the people who can do that for you? It makes sense when companies are trying to cut costs, but that happens when the cost of borrowing is higher than the realizable profit margin