7 ms·

Ask HN: How much of OpenAI code is written by AI?

Amidst the nascent concerns of AI replacing software engineers, it seems a proxy for that might be the amount of code written at OpenAI by the various models they have. If AI is a threat to software engineering, I wouldn't expect many software engineers to actively accelerate that trend. I personally don't view it as a threat, but some people (non engineers?) obviously do. I'd be curious if any OpenAI engineers can share a rough estimate of their day to day composition of human generated code vs AI generated.

crop_rotation 1y ago
> If AI is a threat to software engineering, I wouldn't expect many software engineers to actively accelerate that trend. This is a naive take. Throughout history things have been automated with the help of professions who were being automated away.
- growbell_social 1y ago
  I don't disagree it's a naive take, and I would love to read about some examples where this happened. I haven't seen too many industries be automated away first hand, and I'm sure there are historic examples. I wouldn't expect the lamp lighters to have been championing the rise of electric lamps. Maybe they did though because it meant they could work less hours.
  - madeofpalk 1y ago
    Software developers have been automating away software developers since the beginning of the field. Higher level languages, better+safer languages, improved IDEs. All the ways in which we made developing software easier and more efficient. QA teams investing in automated testing.
    - kadushka 1y ago
      At some point, if this process continues, it is expected to actually automate software developers, would you agree?
  - est31 1y ago
    It's everywhere. One example is probably blacksmiths. Before, each larger village used to have one. Nowadays, this is not the case any more as people order replacement parts for whatever metal piece that broke in your car, house, etc. The metal molding happens in factories instead. But in order you still need to have people who know how to mold metals. The early folks for this profession were blacksmiths. Nowadays you would not call them any more. But it's definitely been "engineers with AI". Same goes for industrialized food. The huge industrial bakeries still employ people who know how to bake bread, but they can do 1000x more than they could do if they had to knead the dough on their own, separate it, form little pieces of bread, order it nicely on a tray, etc. Now it's a machine doing most pieces of work, but they still have folks who design new bread products, adjust machines, know what to change in the formula if one particular product from one particular supplier is not available in the quantities needed, etc. A lot of the skills needed aligns enough with the traditional job of a baker that these factories employ actual bakers. As for software, whenever I use AI tools, I don't really feel that they help me save time much. But it's entirely possible that this is going to change in the future. They are only going to get better. And of course a lot of people say it's useful for them, so it already affects folks. Just because something is not useful to me doesn't mean it's not going to be useful to anybody.
- iknowSFR 1y ago
  Yeah, this needs to be considered down to the individual level. If your employer not only incentives you to go against your best interests but also threatens the stability of your role, then your choices are either do the job or accept that you might not be reliably employed. This is the culmination of decades of moving power from the employee to the employer.
notfried 1y ago
Not OpenAI, but Anthropic CPO Mike Krieger said in response to a question of how much of Claude Code is written by Claude Code: "At this point, I would be shocked if it wasn't 95% plus. I'd have to ask Boris and the other tech leads on there." [0] https://www.lennysnewsletter.com/p/anthropics-cpo-heres-what-comes-next https://www.lennysnewsletter.com/p/anthropics-cpo-heres-what...
- PostOnce 1y ago
  TFA says "How Anthropic uses AI to write 90-95% of code for some products and the surprising new bottlenecks this creates". for some products. If it were 95% of anything useful, Anthropic would not still have >1000 employees, and the rest of the economy would be collapsing, and governments would be taking some kind of action. Yet none of that appears to be happening. Why?
  - ebiester 1y ago
    I don't doubt it, especially when you have an organization that is focused on building the most effective tooling possible. I'd imagine that they use AI even when it isn't the most optimal, because they are trying to build experiences that will allow everyone else to do the same. So let's take it on face value and say 95% is written by AI. When you free one bottleneck you expose the next. You still need developers to review it to make sure it's doing the right thing. You still need developers to be able to translate the business context into instructions that make the right product. You have to engage with the product. You need to architect the system - the context windows mean that the tasks can't just be handed off to AI. So, The role of the programmer changes - you still need technical competence, but to serve the judgement calls of "what is right for the product?" Perhaps there's a world where developers and product management merges, but I think we will still need the people.
  - aforwardslash 1y ago
    Been using claude code almost daily for over a month. It is the smartest junior developer I've ever seen; it can spew high-quality advanced code and with the same confidence, spew utter garbage or over-engineered crap; it can confidently tell you a task is done and passing tests, with glaring bugs in it; it can happily introduce security bugs if it's a shurtcut to finish something. And sometimes, will just tell you "not gonna do it, it takes too much time, so here's a todo comment". In short, it requires constant supervision and careful code review - you still need experienced developers for this.
ivraatiems 1y ago
I absolutely believe that a large proportion of new code written is at least in-part AI generated, but that doesn't mean a large proportion of new code is 100% soup-to-nuts/pull-request-to-merge the result of decisions made by an agent and not a human. I doubt that very much. I think the difference between situations where AI-driven development works and doesn't is going to be largely down to the quality of the engineers who are supervising and prompting to generate that code, and the degree to which they manually evaluate it before moving it forward. I think you'll find that good engineers who understand what they're telling an agent to do are still extremely valuable, and are unlikely to go anywhere in the short to mid term. AI tools are not yet at the point where they are reliable on their own, even for systems they helped build, and it's unclear whether they will be any time soon purely through model scaling (though it's possible). I think you can see the realities of AI tooling in the fact that the major AI companies are hiring lots and lots of engineers, not just for AI-related positions, but for all sorts of general engineering positions. For example, here's a post for a backend engineer at OpenAI: https://openai.com/careers/backend-software-engineer-leverage-engineering/ https://openai.com/careers/backend-software-engineer-leverag... - and one from Anthropic: https://job-boards.greenhouse.io/anthropic/jobs/4561280008 https://job-boards.greenhouse.io/anthropic/jobs/4561280008. Note that neither of these require direct experience with using AI coding agents, just an interest in the topic! Contrast that with many companies who now demand engineers explain how they are using AI-driven workflows. When they are being serious about getting people to do the work that will make them money, rather than engaging in marketing hype, AI companies are honest: AI agents are tools, just like IDEs, version control systems, etc. It's up to the wise engineer to use them in a valuable way. Is it possible they're just hiring these folks to try and make their models better to later replace those people? It's possible. But I'm not sure when in time, if ever, they'll reach the point where that was viable.
- osigurdson 1y ago
  >> new code is 100% soup-to-nuts/pull-request-to-merge the result of decisions made by an agent I am beginning to have more success with this in simpler parts of the code. Particularly if you already have a good example of how to do something and you need something very similar. I usually have to do a few tweaks but generally quite useful.
appreciatorBus 1y ago
> If AI is a threat to software engineering, I wouldn't expect many software engineers to actively accelerate that trend. I personally don't view it as a threat, but some people (non engineers?) obviously do. Software engineers have been automating away jobs for other people for nearly a century. It would be quite rich if the profession suddenly felt qualms about the process! (TBC I think automation is great and should always be pursued. Ofc there are real human concerns when change happens quickly but I am skeptical that smashing the looms is the best response)
- another_twist 1y ago
  Software engineering has also been automating its own jobs for ages. The first thing we engineers do when asked to do a repetitive thing is find ways to automate it. I think the industry had qualms about losing their jobs. But honestly what are the examples of people losing their jobs to software ? Everybody says that this has happened many times yet examples are hard to come by.
  - genidoi 1y ago
    > But honestly what are the examples of people losing their jobs to software? And furthermore, what is the full causality chain that links the precise PR in provided example software to the employment termination decision? Lacking that, can you really assert the software 'automated' a dev out of the job?
    - another_twist 1y ago
      Honeslty I would even accept statistical test (but conclusive, no p-hacked bullshit). Yet I just dont see examples of devs being automated out of a job.
  - i_have_an_idea 1y ago
    > But honestly what are the examples of people losing their jobs to software ? Bank tellers Travel agents Cashiers Bookkeeping clerks Typists
add-sub-mul-div 1y ago
> If AI is a threat to software engineering, I wouldn't expect many software engineers to actively accelerate that trend. There are two strong forces at play. Employees generally want to put in the least amount of effort possible and go home at 5. Employers want to save money and pay for fewer employees. AI creates a strong symbiosis here and both sides are focused on a short term win.
- senectus1 1y ago
  >Employees generally want to put in the least amount of effort possible and go home at 5. Really? In my experience coding engineers are coders because they enjoy the challenge. they like building things, breaking things and rebuilding things. Its the white-collar 9-5 office workers that churn out power-point and word documents that want to do as little as possible.
  - siddboots 1y ago
    Sometime very soon we’ll cross a threshold where most people can do most of their coding through a tool like Claude and be more productive. It will feel like coding still, breaking and building things, but they will get more done in the same time. Everyone will switch.
    - oulu2006 1y ago
      I'm already building whole projects now with AI -- not a single line of code by myself. I love it, I've coded for 25 years and I don't need to write another line ever again, I just want to build cool things as fast as possible.
  - pizzalife 1y ago
    If you work at a startup, sometimes you have to do extremely mundane and boring things unrelated to your expertise (“wear many hats”). AI is especially useful in those cases so you can quickly go back to working on things you enjoy.
- oulu2006 1y ago
charlesju 1y ago
I think this is the wrong question. The right question is how much human code can a human push now vs prior to AI. Everything we've done in coding has been assisted. Prior to this current generation of web applications, we had the advent of concepts like Object Orientated Programming and prior to that even C was a massive move up from Assembly and punch cards. AI has written a lot of code. AI has written very little high velocity production code by itself (ie. for people with no coding background). In Ruby on Rails, the concept of fast coding has been around for over 20 years, look up this concept of Scaffolding: https://www.rubyguides.com/2020/03/rails-scaffolding/ https://www.rubyguides.com/2020/03/rails-scaffolding/ So to answer your question, 1. AI has pushed a lot of code 2. AI has pushed almost no code without the oversight of human software engineers 3. Software engineers are pushing a magnitude more code and producing more functional utility and solving more bugs than ever before I don't know what the future holds, but I do think that this is not a new trend to use software to help humans build faster, and I don't think software has the ability to fully replace humans (yet).
- fugalfervor 1y ago
  > Software engineers are pushing a magnitude more code and producing more functional utility and solving more bugs than ever before Citation needed
  - ythiscoyness 1y ago
    More programmers than ever before makes this implicitly true. It’s not as clever as the author hoped.
    - charlesju 1y ago
      From my personal account, I started with PHP and Perl (high school and college) and then graduated to Ruby on Rails (early dev career) and now its Python and JS. I would say Ruby on Rails was a 10x on raw PHP in terms of feature specs per hour and AI is a 10x on Ruby on Rails (and its derivatives). We're probably 100x the developer productivity on a per developer basis from the early days of Web 2.0 with PHP, just a personal anecdote though.
welder 1y ago
Estimates will always be off compared to a plugin like wakatime tracking the real amount of AI generated code vs human written code.
YZF 1y ago
I don't work for OpenAI and I doubt some random employee is going to come here and share what is likely a secret. I'm in the industry though so I have some idea of what's going on these days, both where I work and more broadly. AI is getting better at writing code. However writing code is just some fraction of the work of many software engineers. AI doesn't work independently, it needs to be guided, its work needs to be reviewed, tested etc. There are some domains where it does better and some domains where it doesn't. There's a range of "AI" work between auto-complete style work, assisting in understanding a code base, and writing code from some spec or doing other types work. All in all I would say it's a decent improvement to productivity for many situations. It's really hard to say how much and it's also not a zero sum game, as productivity improves there's more work. Something to keep in mind is that if you look at a modern software project likely most of the code executing is not code written by the developers of that project. There's a huge stack of open source bits executing for almost any new project. Specifically in OpenAI you also need to consider what type of software they are likely writing. Some of it may be more or less "vanilla" code and other is likely very specialized/performance critical. The vanilla code like API wrappers or simple front end pieces is likely more amenable to be written by AI whereas the more cutting edge algorithmic/scheduling/optimization work is almost certainly not done by AI. At least yet. As software organizations become larger there's a lot of overhead and waste. It is possible that AI can enable smaller teams and that has a multiplicative effect because it lets you reduce that waste/overhead. There are likely also software engineers who will become better/adapt to new workflows and some who will not. It's really hard to say where things are going but overall my sense is that this like many other innovations will lead to more software and more jobs and not the other way around. There are many moving pieces here, not just AI itself but geopolitics, macro-economics, etc. Where are those new jobs going to get created, what new types of software/technology are going to be created etc. etc. History seems to show us that we'll adapt/evolve and grow.
theusus 1y ago
IME I have had to review a lot of code written by AI. At certain almost all of it. And sometimes write the code myself because LLMs just don't get it. AI has written 95% of my code but not without any review.
crazylogger 1y ago
This is like asking me "how much of your software is built by the compiler?" -> the answer is 100%. Ask "how much did you build then?" -> also 100%. The compiler and I operate on different layers.
- lion__93332 1y ago
  Did you refer to any code from GitHub or other sources online?
ianpurton 1y ago
I don't work at Open AI but I use Codex as I imagine most people there do to. I actually use it from the web app not the cli. So far I've run over 100 codex sessions a great percentage of which I turned in to pull requests. I kick off codex for 1 or more tasks and then review the code later. So they run in the background while I do other things. Occasionally I need to re-prompt if I don't like the results. If I like the code I create a PR and test it locally. I would say 90% of my PR's are AI generated (with human in the loop). Since using codex, I very rarely create hand written PR's.
- dearilos 1y ago
  Do you use any tools to help with the code review part?

crop_rotation 1y ago

> If AI is a threat to software engineering, I wouldn't expect many software engineers to actively accelerate that trend. This is a naive take. Throughout history things have been automated with the help of professions who were being automated away.

growbell_social 1y ago
I don't disagree it's a naive take, and I would love to read about some examples where this happened. I haven't seen too many industries be automated away first hand, and I'm sure there are historic examples. I wouldn't expect the lamp lighters to have been championing the rise of electric lamps. Maybe they did though because it meant they could work less hours.
- madeofpalk 1y ago
  Software developers have been automating away software developers since the beginning of the field. Higher level languages, better+safer languages, improved IDEs. All the ways in which we made developing software easier and more efficient. QA teams investing in automated testing.
  - kadushka 1y ago
    At some point, if this process continues, it is expected to actually automate software developers, would you agree?
- est31 1y ago
  It's everywhere. One example is probably blacksmiths. Before, each larger village used to have one. Nowadays, this is not the case any more as people order replacement parts for whatever metal piece that broke in your car, house, etc. The metal molding happens in factories instead. But in order you still need to have people who know how to mold metals. The early folks for this profession were blacksmiths. Nowadays you would not call them any more. But it's definitely been "engineers with AI". Same goes for industrialized food. The huge industrial bakeries still employ people who know how to bake bread, but they can do 1000x more than they could do if they had to knead the dough on their own, separate it, form little pieces of bread, order it nicely on a tray, etc. Now it's a machine doing most pieces of work, but they still have folks who design new bread products, adjust machines, know what to change in the formula if one particular product from one particular supplier is not available in the quantities needed, etc. A lot of the skills needed aligns enough with the traditional job of a baker that these factories employ actual bakers. As for software, whenever I use AI tools, I don't really feel that they help me save time much. But it's entirely possible that this is going to change in the future. They are only going to get better. And of course a lot of people say it's useful for them, so it already affects folks. Just because something is not useful to me doesn't mean it's not going to be useful to anybody.
iknowSFR 1y ago
Yeah, this needs to be considered down to the individual level. If your employer not only incentives you to go against your best interests but also threatens the stability of your role, then your choices are either do the job or accept that you might not be reliably employed. This is the culmination of decades of moving power from the employee to the employer.

notfried 1y ago

Not OpenAI, but Anthropic CPO Mike Krieger said in response to a question of how much of Claude Code is written by Claude Code: "At this point, I would be shocked if it wasn't 95% plus. I'd have to ask Boris and the other tech leads on there." [0] https://www.lennysnewsletter.com/p/anthropics-cpo-heres-what-comes-next https://www.lennysnewsletter.com/p/anthropics-cpo-heres-what...

PostOnce 1y ago
TFA says "How Anthropic uses AI to write 90-95% of code for some products and the surprising new bottlenecks this creates". for some products. If it were 95% of anything useful, Anthropic would not still have >1000 employees, and the rest of the economy would be collapsing, and governments would be taking some kind of action. Yet none of that appears to be happening. Why?
- ebiester 1y ago
  I don't doubt it, especially when you have an organization that is focused on building the most effective tooling possible. I'd imagine that they use AI even when it isn't the most optimal, because they are trying to build experiences that will allow everyone else to do the same. So let's take it on face value and say 95% is written by AI. When you free one bottleneck you expose the next. You still need developers to review it to make sure it's doing the right thing. You still need developers to be able to translate the business context into instructions that make the right product. You have to engage with the product. You need to architect the system - the context windows mean that the tasks can't just be handed off to AI. So, The role of the programmer changes - you still need technical competence, but to serve the judgement calls of "what is right for the product?" Perhaps there's a world where developers and product management merges, but I think we will still need the people.
- aforwardslash 1y ago
  Been using claude code almost daily for over a month. It is the smartest junior developer I've ever seen; it can spew high-quality advanced code and with the same confidence, spew utter garbage or over-engineered crap; it can confidently tell you a task is done and passing tests, with glaring bugs in it; it can happily introduce security bugs if it's a shurtcut to finish something. And sometimes, will just tell you "not gonna do it, it takes too much time, so here's a todo comment". In short, it requires constant supervision and careful code review - you still need experienced developers for this.

ivraatiems 1y ago

I absolutely believe that a large proportion of new code written is at least in-part AI generated, but that doesn't mean a large proportion of new code is 100% soup-to-nuts/pull-request-to-merge the result of decisions made by an agent and not a human. I doubt that very much. I think the difference between situations where AI-driven development works and doesn't is going to be largely down to the quality of the engineers who are supervising and prompting to generate that code, and the degree to which they manually evaluate it before moving it forward. I think you'll find that good engineers who understand what they're telling an agent to do are still extremely valuable, and are unlikely to go anywhere in the short to mid term. AI tools are not yet at the point where they are reliable on their own, even for systems they helped build, and it's unclear whether they will be any time soon purely through model scaling (though it's possible). I think you can see the realities of AI tooling in the fact that the major AI companies are hiring lots and lots of engineers, not just for AI-related positions, but for all sorts of general engineering positions. For example, here's a post for a backend engineer at OpenAI: https://openai.com/careers/backend-software-engineer-leverage-engineering/ https://openai.com/careers/backend-software-engineer-leverag... - and one from Anthropic: https://job-boards.greenhouse.io/anthropic/jobs/4561280008 https://job-boards.greenhouse.io/anthropic/jobs/4561280008. Note that neither of these require direct experience with using AI coding agents, just an interest in the topic! Contrast that with many companies who now demand engineers explain how they are using AI-driven workflows. When they are being serious about getting people to do the work that will make them money, rather than engaging in marketing hype, AI companies are honest: AI agents are tools, just like IDEs, version control systems, etc. It's up to the wise engineer to use them in a valuable way. Is it possible they're just hiring these folks to try and make their models better to later replace those people? It's possible. But I'm not sure when in time, if ever, they'll reach the point where that was viable.

osigurdson 1y ago
>> new code is 100% soup-to-nuts/pull-request-to-merge the result of decisions made by an agent I am beginning to have more success with this in simpler parts of the code. Particularly if you already have a good example of how to do something and you need something very similar. I usually have to do a few tweaks but generally quite useful.

appreciatorBus 1y ago

> If AI is a threat to software engineering, I wouldn't expect many software engineers to actively accelerate that trend. I personally don't view it as a threat, but some people (non engineers?) obviously do. Software engineers have been automating away jobs for other people for nearly a century. It would be quite rich if the profession suddenly felt qualms about the process! (TBC I think automation is great and should always be pursued. Ofc there are real human concerns when change happens quickly but I am skeptical that smashing the looms is the best response)

another_twist 1y ago
Software engineering has also been automating its own jobs for ages. The first thing we engineers do when asked to do a repetitive thing is find ways to automate it. I think the industry had qualms about losing their jobs. But honestly what are the examples of people losing their jobs to software ? Everybody says that this has happened many times yet examples are hard to come by.
- genidoi 1y ago
  > But honestly what are the examples of people losing their jobs to software? And furthermore, what is the full causality chain that links the precise PR in provided example software to the employment termination decision? Lacking that, can you really assert the software 'automated' a dev out of the job?
  - another_twist 1y ago
    Honeslty I would even accept statistical test (but conclusive, no p-hacked bullshit). Yet I just dont see examples of devs being automated out of a job.
- i_have_an_idea 1y ago
  > But honestly what are the examples of people losing their jobs to software ? Bank tellers Travel agents Cashiers Bookkeeping clerks Typists

add-sub-mul-div 1y ago

> If AI is a threat to software engineering, I wouldn't expect many software engineers to actively accelerate that trend. There are two strong forces at play. Employees generally want to put in the least amount of effort possible and go home at 5. Employers want to save money and pay for fewer employees. AI creates a strong symbiosis here and both sides are focused on a short term win.

senectus1 1y ago
>Employees generally want to put in the least amount of effort possible and go home at 5. Really? In my experience coding engineers are coders because they enjoy the challenge. they like building things, breaking things and rebuilding things. Its the white-collar 9-5 office workers that churn out power-point and word documents that want to do as little as possible.
- siddboots 1y ago
  Sometime very soon we’ll cross a threshold where most people can do most of their coding through a tool like Claude and be more productive. It will feel like coding still, breaking and building things, but they will get more done in the same time. Everyone will switch.
  - oulu2006 1y ago
    I'm already building whole projects now with AI -- not a single line of code by myself. I love it, I've coded for 25 years and I don't need to write another line ever again, I just want to build cool things as fast as possible.
- pizzalife 1y ago
  If you work at a startup, sometimes you have to do extremely mundane and boring things unrelated to your expertise (“wear many hats”). AI is especially useful in those cases so you can quickly go back to working on things you enjoy.
oulu2006 1y ago

charlesju 1y ago

I think this is the wrong question. The right question is how much human code can a human push now vs prior to AI. Everything we've done in coding has been assisted. Prior to this current generation of web applications, we had the advent of concepts like Object Orientated Programming and prior to that even C was a massive move up from Assembly and punch cards. AI has written a lot of code. AI has written very little high velocity production code by itself (ie. for people with no coding background). In Ruby on Rails, the concept of fast coding has been around for over 20 years, look up this concept of Scaffolding: https://www.rubyguides.com/2020/03/rails-scaffolding/ https://www.rubyguides.com/2020/03/rails-scaffolding/ So to answer your question, 1. AI has pushed a lot of code 2. AI has pushed almost no code without the oversight of human software engineers 3. Software engineers are pushing a magnitude more code and producing more functional utility and solving more bugs than ever before I don't know what the future holds, but I do think that this is not a new trend to use software to help humans build faster, and I don't think software has the ability to fully replace humans (yet).

fugalfervor 1y ago
> Software engineers are pushing a magnitude more code and producing more functional utility and solving more bugs than ever before Citation needed
- ythiscoyness 1y ago
  More programmers than ever before makes this implicitly true. It’s not as clever as the author hoped.
  - charlesju 1y ago
    From my personal account, I started with PHP and Perl (high school and college) and then graduated to Ruby on Rails (early dev career) and now its Python and JS. I would say Ruby on Rails was a 10x on raw PHP in terms of feature specs per hour and AI is a 10x on Ruby on Rails (and its derivatives). We're probably 100x the developer productivity on a per developer basis from the early days of Web 2.0 with PHP, just a personal anecdote though.

welder 1y ago

Estimates will always be off compared to a plugin like wakatime tracking the real amount of AI generated code vs human written code.

YZF 1y ago

I don't work for OpenAI and I doubt some random employee is going to come here and share what is likely a secret. I'm in the industry though so I have some idea of what's going on these days, both where I work and more broadly. AI is getting better at writing code. However writing code is just some fraction of the work of many software engineers. AI doesn't work independently, it needs to be guided, its work needs to be reviewed, tested etc. There are some domains where it does better and some domains where it doesn't. There's a range of "AI" work between auto-complete style work, assisting in understanding a code base, and writing code from some spec or doing other types work. All in all I would say it's a decent improvement to productivity for many situations. It's really hard to say how much and it's also not a zero sum game, as productivity improves there's more work. Something to keep in mind is that if you look at a modern software project likely most of the code executing is not code written by the developers of that project. There's a huge stack of open source bits executing for almost any new project. Specifically in OpenAI you also need to consider what type of software they are likely writing. Some of it may be more or less "vanilla" code and other is likely very specialized/performance critical. The vanilla code like API wrappers or simple front end pieces is likely more amenable to be written by AI whereas the more cutting edge algorithmic/scheduling/optimization work is almost certainly not done by AI. At least yet. As software organizations become larger there's a lot of overhead and waste. It is possible that AI can enable smaller teams and that has a multiplicative effect because it lets you reduce that waste/overhead. There are likely also software engineers who will become better/adapt to new workflows and some who will not. It's really hard to say where things are going but overall my sense is that this like many other innovations will lead to more software and more jobs and not the other way around. There are many moving pieces here, not just AI itself but geopolitics, macro-economics, etc. Where are those new jobs going to get created, what new types of software/technology are going to be created etc. etc. History seems to show us that we'll adapt/evolve and grow.

theusus 1y ago

IME I have had to review a lot of code written by AI. At certain almost all of it. And sometimes write the code myself because LLMs just don't get it. AI has written 95% of my code but not without any review.

crazylogger 1y ago

This is like asking me "how much of your software is built by the compiler?" -> the answer is 100%. Ask "how much did you build then?" -> also 100%. The compiler and I operate on different layers.

lion__93332 1y ago
Did you refer to any code from GitHub or other sources online?

ianpurton 1y ago

I don't work at Open AI but I use Codex as I imagine most people there do to. I actually use it from the web app not the cli. So far I've run over 100 codex sessions a great percentage of which I turned in to pull requests. I kick off codex for 1 or more tasks and then review the code later. So they run in the background while I do other things. Occasionally I need to re-prompt if I don't like the results. If I like the code I create a PR and test it locally. I would say 90% of my PR's are AI generated (with human in the loop). Since using codex, I very rarely create hand written PR's.

dearilos 1y ago
Do you use any tools to help with the code review part?