One of the most likely professions eaten by software, is software.
You are on point. I've been quietly mentioning this to software engineer friends, and poo pooed. I am more of the computer science-y than software engineer-y persuasion - and have seen this as a clear risk.
edit 1: originally I thought it will mainly be for new code bases (green field) - but with the ability for code to "git pull" and then "chatgpt refactor" may be a game changer.
edit 2: I think this is great - it can allow engineers to work on a higher level. I remember in CompSci training always thinking "why in the heck am I typing into a computer how to do its job?" and "why should engineers be dealing with stupid $hit like NaN and pointer overflows (C++) and heap issues an CRUD apps. It all seems like low brain stuff"
AI will eat software engineering the same way it'll eat art - from the bottom, and quickly at first then very very slowly. Engineers will be responsible for directing, verifying and correcting AIs at increasingly high levels over time. Hand written code will be limited to optimizations and working around weaknesses in the model much the same as inline assembly is still used with compiled code.
Fully agree with your assessment. Bottom up is vulnerable.
I can then see engineers running entire department of AI by themselves..... someone who is an architect level and understands the business and can both envision the services, but also fix black box systems creating content that no one understands under the covers.
This could be a very good time to create a startup that can make that command line and:
1. Document its functioning overall ("chatgpt doc")
2. Find bugs / logical flaws ("chatgpt debug")
3. Refactor the code for readability ("chatgpt refactor")
4. Improve its compute/memory performance ("chatgpt speed")
5. Improve the quality of comments ("chatgpt comment")
Seems that the main limitation at this point would be the OpenAI Terms of Use. How much freedom is given to build commercial services on top of their API?
You are on point. I've been quietly mentioning this to software engineer friends, and poo pooed. I am more of the computer science-y than software engineer-y persuasion - and have seen this as a clear risk.
edit 1: originally I thought it will mainly be for new code bases (green field) - but with the ability for code to "git pull" and then "chatgpt refactor" may be a game changer.
edit 2: I think this is great - it can allow engineers to work on a higher level. I remember in CompSci training always thinking "why in the heck am I typing into a computer how to do its job?" and "why should engineers be dealing with stupid $hit like NaN and pointer overflows (C++) and heap issues an CRUD apps. It all seems like low brain stuff"