We're sick and tired of the media and talking heads claiming that AI tools like ChatGPT are just going to replace programmers. What do they know? What data are they even basing this on?
That's the problem. There really is no data out there on how programmers are actually using ChatGPT or AI tools. Are they using them? Are they worried about them? Are their employers telling them to use them or not hiring developers anymore?
We wanted to find out the answers to these questions. So we put out a survey and gathered responses from June 3, 2023 to June 22, 2023 to find out if and how programmers are actually using AI tools.
We thought 1,000 responses would have been great, but the response was incredible. 3,240 people completed the survey, and it wasn't exactly short either!
Now 3,240 might not seem like a lot until you compare it to other AI surveys out there (or just other surveys in general).
McKinsey did one that had 1,492 respondents, one by the Verge had 2,000, and a recent developer specific survey by Github was based on only 500 developers (and every developer knows GitHub so their audience is pretty damn big).
We're not telling you this as a brag but so that you know these insights are based on a really solid sample size. And because many more people have heard of McKinsey, the Verge and GitHub.
Side note: The graphics and design on that Verge survey... so cool. Definitely check out those other surveys out as well.
But as far as we know, this is the biggest survey of developers on the topic of AI to date with responses from industry professionals across a variety of roles, companies, and levels of experience. Everyone from solopreneurs, contractors, new and long-term coders, and even team leads at 1,000+ employee companies.
So now that you know the sample size is solid, here is a sneak peak into what we thought were some of the most interesting findings:
Note: Keep reading for more details and additional stats as well as deep dives into how demographics and other factors affect trends in adoption, usage, and opinion.
But first we'll run you through our methodology. If you just want the stats and the takeaways, feel free to scroll by.
Our goal with this survey was to start broad and see which AI tools (if any) programmers are using, how they’re using them, their thoughts on the future, and their effect on programming.
Rather than look into every single potential AI tool, we wanted to look at pair programming tools (or tools that might not specifically be for this, but that can achieve it).
The reason for this filter was so we could look at the types of tools that could help with a large portion of a programmer's day vs. a niche tool used for one singular task.
Why?
Because we’ve had AI tools for a while now that can do one or two things fairly well, but there’s been a huge push lately in these new tools that could actually code for us - if we learn to use them properly.
And this is where the ‘what if’s exist.
Then we dove deeper to see if there were general trends that appeared across education level, company size, salary, role, and other metrics.
Things like:
Alright, enough talk, let's dive into the data.
Sounds good? Alright, let's get into it!
Note: Click on any graph below to open a high-res version.
Although there were over 20+ different roles that filled out the survey, the majority of responses came from:
After that we had:
There was a pretty balanced mix of responses from new developers as well as more experienced or senior programmers. This is great as it allows us to see how adoption and opinion differ across experience levels... more on this later.
The majority of responses came from the US, Europe, India, and Asia.
Our goal in finding out this information was to see if there were any particular trends across regions.
Are there specific locations that have been slower or faster to adopt these AI tools than others?
Spoiler alert: One region is adopting far faster than others and it's probably not where you might be thinking.
We also wanted to see if there were any variations in adoption rates and/or opinions based on age.
Special shoutout to the 2.2% of 60+ programmers out there. Nothing better than being a lifelong learner!
These people are evidence that you're never too old to learn to code.
We thought it could be interesting to see if there were any particular trends or differences based on the size of company that these programmers work at.
Would larger companies veer away from these tools, or would they be the ones to lead the charge?
Perhaps education ties into the adoption rate?
Would self-taught programmers be more agile and likely to adopt AI tools or more apprehensive to use these tools?
Finally, we also asked for a salary range. This way we could see if there were patterns among higher or lower earners for adoption, job security, etc.
So, with that out of the way, let’s start looking at more specific answers, and how they connect with demographics.
While most programmers at this point are at least trying out AI tools and experimenting with them, there are still 15.6% of programmers that have never tried any.
With this in mind, we wanted to find out what why they hadn't and if they planned to in the future.
However, 51.4% of those who hadn’t tried any tools yet, planned to use them over the next 6 months.
This is incredibly interesting, because although that 18.2% number seems high, when you look at that alongside planned future usage, it means that only ~3% of programmers that haven't already used an AI tool, have no plans or interest in trying them.
Or, even more impressive, by the end of 2023, ~97% of programmers will be either using AI tools, or at least tried them.
Clearly these tools are useful and people want to use them, but something is holding them back. So we figured the best way to find out, was to ask them what the issue was!
This makes sense. If you’re busy and stuck in the grind, it can be hard to slow down further just to find ways to speed up - even if it makes more sense long term.
It wasn’t just the effort to learn though. Another 13.4% were worried about the accuracy of the tools, which is a fair assessment.
It's been pretty well documented at this point that "hallucinations" can often happen, and unless you know the core topic and how to use the tools - you might be getting inaccurate information.
There were also 14.6% that stated it was the time to implement these tools as the reason for not using them yet.
We wonder what that really means...
Maybe because you could end up adding more time to your current tasks that you're already efficient at? Or perhaps this is people at bigger companies that have restrictions and hoops that need to be jumped through before employees are allowed to use these tools.
These are definitely some valid concerns, but as we've seen, the majority of programmers have been able to get past these issues and are finding ways to use these tools.
But what are they using them to do? And exactly how much are they using them? Which tools? And how effective are they?
Well, let's find out...
We provided a list of 12 AI tools that can be used for programming related tasks and asked people to let us know how often (if ever) they had used them.
This was the list of options:
The most popular tool by far was ChatGPT 3.5, with 58.4% of the respondents using it at least once a week (30.8% of those are using it daily).
Combined with the weekly usage of ChatGPT 4 (an additional 16.5%), that means that 74.9% of developers reported using some version of ChatGPT on a weekly basis 🤯
After ChatGPT 3.5, here were the next most used tools on a daily basis:
Right now, it probably comes down to breadth of usability, alongside frequency of tasks.
Or in simple terms, Visual Studio Intellicode and GitHub CoPilot are coding focused, so you would only use them for specific coding tasks. Whereas a tool like ChatGPT can be used for a much broader range of tasks - hence why it might be used more often. (More on this in a second).
Since ChatGPT 3.5 was used by far more of the survey audience than any other AI tool, we’ll be using it as our "proxy" going forward.
For example, in a coming section, if we say "Machine Learning Engineers are using AI tools more than any other role" (true story) then unless we specify otherwise, AI tools = ChatGPT 3.5 usage.
So let’s take a look at what we found out.
We wanted to know which roles were using these tools the most often.
To figure this out, we decided to cross-reference the 6 roles that gave the most responses, (Full-stack, Front-End, Back-End, Machine Learning Engineers, Designers, and Data Scientists), against their usage of the most popular tool (ChatGPT 3.5).
The results:
We'd think Machine Learning Engineers might use AI tools in general more in their job than other roles but it’s interesting to see how many of them are specifically using ChatGPT.
Across actual primary programming roles (front-end, back-end, full-stack), there wasn't a big difference in usage.
Programmers in Africa had the highest daily adoption rate of AI tools and programmers in Asia had the highest weekly adoption rate of AI tools.
The lowest adoption rate of all regions (daily and weekly)...? The United States!
We wanted to see if there was a difference in adoption rate of these tools based on a number of demographic factors.
The first one we looked at was the geographic location of the programmer against weekly usage, and then daily usage on its own, to see if there were any trends.
The weekly results are in the chart above with Asia edging out Africa.
Daily Results:
Although we did get responses from a ton of other countries and regions, we only included the ones that had more than 100 respondents.
Young Programmers (18-25 years old) are the biggest adopters of using AI tools for coding. 46.3% are using ChatGPT for work daily and an additional 29% on a weekly basis.
What about other age groups?
The results (using AI tools daily for work):
Side note
Programmers who are both working and under 18 technically had the highest adoption rate (53.1% daily use), but this audience size was less than 50 people so we excluded it from these results.
(Being under 18 and working in tech is incredibly rare, so this was too small a dataset to consider accurately, but it's awesome to see even 50 people who’ve achieved this).
We're not really shocked by this result as you would expect that younger people in general would be more open to trying new things (I'm still figuring out TikTok but I'm not telling you how old I am).
However, it was a bit surprising to see a direct correlation between age and usage of AI tools for coding work.
Maybe these younger programmers are more worried about proving themselves? Or maybe they see their peers using these tools and don't want to get left behind?
We wanted to see if there were any trends between years of experience in a role, and adoption of AI tools (again, using ChatGPT as our proxy).
We looked at the users for both daily + weekly combined (for a broad picture), and then those who it daily to see if there were any specific trends.
The results (daily usage for work purposes):
We were actually surprised to see such a significant percentage of experienced programmers using ChatGPT regularly.
While the lowest adoption is amongst programmers with 10+ years experience, almost 20% of them using it daily is extremely impressive given we would expect these people to be most resistant to change and new tools.
It'll be really interesting to see if the trend continues or if usage fades away for any of these groups when we do the 2024 edition.
We wanted to see if there was a difference in adoption rate and usage of this tool at work, based on the highest level of education someone has achieved.
Again, we looked at the combined daily + weekly users for a broad picture, and then the daily users only.
When we look at daily usage, there isn't a huge difference to report here.
Highest adopters: Programmers with a Bachelor’s Degree are the highest adopters of AI tools for work (31.2% using it daily).
Lowest adopters: Funny enough, people with a Doctorate Degree (highest education) are using AI tools for work at the same rate as people with no formal degree (least education).
The results (daily usage only)
We compared salary ranges of programmers against their daily and weekly usage of AI tools.
The weekly results are in the chart above.
The daily usage results:
Interestingly, there seems to be a pretty clear inverse correlation between salary and daily AI tool (ChatGPT) usage.
The highest daily adoption rate was among the lowest salary programmers and adoption rate dropped off as salary increased.
But when we zoomed out to weekly usage, there wasn't any correlation at all. Although the lowest salary programmers still have the highest weekly usage, the highest salary programmers have the second highest weekly usage (compared to lowest for daily usage).
Here's a deeper breakdown for the <$50K segment (daily + weekly in the chart below = total weekly):
Perhaps this is a case of when someone's salary increases, the role they are doing may contain less tasks that are more easily replaced by these AI tools (ex: repetitive tasks)?
That being said, while there is a dropoff rate at each higher salary range, it really isn't that big (ex: roughly 2 in 10 people making between $150-$200k vs. 3 in 10 people making less than $50k).
We wanted to see if there were any trends among adoption rate of AI tools and company size. Again, we looked at combined daily + weekly (see graph above) vs daily usage on its own.
Our initial theory was that solopreneurs might be the biggest adopters, simply so they could improve their output.
1 person + an AI tool = the biggest opportunity to get more done right?
However, the largest adoption was in those scrappy SMB (Small Medium Business) and start-up sized companies, with 44% of programmers that work in 11-20 employee sized companies using ChatGPT daily for some portion of their work.
In fact, the top 5 groups using ChatGPT daily were all those working at companies of less than 100 employees.
The results (daily usage)
One interesting note though is that although 501-1,000 employee companies had a lower daily usage, they had the highest weekly usage!
In fact, 30.1% of programmers at these companies are using it at least once a week.
We asked our survey audience to list out each task that they use AI tools for at work, and the overwhelming majority are using AI tools as a quasi-search engine (learning new topics and writing code), which makes sense.
On one hand, programming is problem solving.
A lot of times other developers have had the same problem or a similar one, so programmers spend a lot of time searching on Google and sites like StackOverflow for potential solutions to their problems (many times there are code snippets that people can re-use or slightly modify for their situation).
Given the fact that you can deeply customize the results that get sent back from ChatGPT (and other AI tools), as well as it being able to literally write snippets of code for you that fit those questions, and it makes a very compelling use case.
What like?
Standard tasks like writing SQL queries or regex are great examples of things that a developer might previously have had to Google to remember the correct syntax for. But now, ChatGPT can easily write these queries for you.
On another hand, programming and tech in general also changes so fast. Developers have to be constantly learning to stay up-to-date and almost always have to learn something new for every project they work on.
So instead of searching on Google or Youtube, it seems like people are getting ChatGPT to provide them with tutorials and "how-to" type content on these new things they're trying to learn.
Editor's Note: There are well documented risks and downsides to relying blindly on ChatGPT or other AI tools though so make sure to be aware of those.
But from our experience, if you know what to look for and how to properly use them, these AI tools are super useful.
Here's a little beginner's guide to using ChatGPT for coding (and the pitfalls to watch out for).
As a final point on this, it’s also not surprising that people are using this for search, because it's the lowest entry point to using the tool.
Anyone that can enter a question into Google can just as easily enter a question into ChatGPT, so it’s expected to be the most common use case (at least in these early days).
What was interesting to note was that survey respondents who were using it to write code, were almost always using it to help with other tasks as well, such as debugging, testing, writing documentation, pair-programming, and more.
Once you prompt, you just can't stop!
So, are these tools so helpful that some programmers are using them for a majority of their work? Or is it a case of them having success with ChatGPT to solve one problem, and now they're treating it like a hammer and thinking everything is a nail?
We might need to do some follow-up here...
We also asked our participants to share the volume of their work that they estimate they use AI tools to assist with.
According to our results, 70.5% of them are already using AI tools to help with at least 20% of their work.
There's a lot of metrics in this report so its easy to skim past them, but stop and think for a second, because this is more shocking than it first appears.
If you consider the fact that 20% of someone's work week would roughly equate to one total work day, that's a big difference in quality of life.
That's an entire days work (every week) that's semi-automated, outsourced, or simplified in some way!
Even more impressive?
20.9% of these people are using these tools to help with 50%+ of their work.
What does this mean? Are these people more likely to be replaced over time? Or are these the people that are going to have the first mover advantage and get themselves a leg up by working way more efficiently than their peers?
Either way, we have to confess to a mild level of jealousy to these people who are able to get assistance on 90% of their workload... we might have to reach out to these people for a follow-up article!
The results
Impressive right?
Let's break it down by role and see how that compares.
Because we have data on specific job roles and their estimated volume of work being assisted by AI tools, we wanted to see which roles are really pushing the envelope and using AI tools the most.
And so we decided to compare roles based on who is using these tools to help with 30% of their work.
Why 30%?
Well, using AI tools to help with 10% of your work is a good start but it doesn't feel like a game changer.
30% seems like a tipping point where a company could make a serious decision to not have to make an additional hire (ex: if their existing teams were 30%+ more efficient).
The results
Although front-end devs are the highest, it seems like there are many people across all these roles that are already finding a way to leverage AI tools for a big chunk of their work.
It's interesting that so many people feel so confident that their job isn't at risk but also that so many people are finding ways to essentially replace themselves.
Maybe companies don't realize how much work their employees are able to do with these tools?
Or maybe companies would happily take a productivity bump because these workers are now more efficient.
We have so many more questions!
We may have to follow up with some of these respondents to learn more about their processes, how they got past the learning curve, and what the exact tasks they are replacing that make up the 30% (or more) they are saying.
Here's where it gets really interesting.
Rather than just stay at the 30% mark, we decided to look deeper to see if there were any trends in specific roles that are pushing even higher.
Was there a particular role that stood out?
It turns out, there was.
The results
This makes sense, after all, Machine Learning is all about working with AI.
However, it's really interesting when you look at how high the percentages are for each other role on this list. Most of them never need to use an AI tool, and yet over 46% of Front-End Developers are using AI tools to help with at least 30% of their work (some are even using it to help with 90% of their workload!).
We're honestly surprised this isn’t a higher number.
Why?
Well, we’re kind of spoiled in tech in that these tools can help assist in far more areas of our day to day job, in an actual applicable way than in other industries.
That said, I imagine this number will rise each year from here on out.
10.7% of programmers who applied for a job in the last 12 months, stated that the job listing had ‘having experience using ChatGPT (or any other AI tool)’ as a requirement.
To put that into context, of the 2,115 people in our survey who applied for a new job in the last 12 months, 227 of them reported job listings requesting some kind of AI tool experience.
Will this rise over the next few years?
Honestly, we think it’s all going to come down to people embracing the learning curve and taking the time to apply these tools. Once that becomes standard, then we have to imagine that we’ll see a huge lift.
Our bet is that learning these tools is going to be important, whether explicitly stated as a job requirement or not.
OK, so what do managers and team leads think about using these AI tools?
That’s almost 700 managers providing insights here!
This allowed us to tailor a few questions to see what the thoughts and feelings are from those who have to wrangle the rest of us.
Let’s see what the data has to say.
Obviously this is a very exciting time, however team leads are still cautious. When we look at their concerns though, it does make sense:
Nothing too drastic and things that can be worked through. Heck, having to check code snippets from 3rd party sources before you implement them should be standard practice anyways right?
But still, these concerns and factors seem to be why there isn't yet a huge push by managers to require employees to learn these tools yet…
Only about a quarter of managers are requiring employees to use AI tools at this point, which makes sense given the responses we received to the previous question.
There are still a few hang ups to getting up to speed (like any new tool or product) and removing errors with these tools.
The big thing to watch over the next year is whether these concerns are adequately resolved by the various tools out there.
If they are, usage will rise. If not, maybe these tools aren't going to deliver on the productivity improvements that many people are hyping them up to be capable of.
It might be more likely that existing products employees are already using (and are comfortable using) will add in additional AI capabilities (ex: Github CoPilot) rather than relying on a single AI tool for all tasks (ex: ChatGPT).
Although only 27.9% of team leads are encouraging their employees to learn these tools, if we break it down by company size then it's the team leads at 1,000+ employee companies who are the biggest proponents.
We're not sure exactly what to make of this...
On one hand it makes sense right?
1,000+ employee companies are possibly more FAANG level and would expect their team members to be the most efficient coders they can be. Add in the fact that a 1% improvement in output across 1,000+ employees would be a huge impact.
Heck… imagine if they could get to the point where their team members are able to help assist 10-30% of their roles with AI tools, and how that would affect their bottom line!
On the other hand, it's a bit surprising because bigger companies tend to be slower to adopt new tools and technologies given all the red tape that exists.
Alright, the final section. Everyone loves to have an opinion right?
Let’s look at some general opinions around these tools and the future of them, from both an employee and team leader perspective.
Let’s find out.
This is pretty much the same sentiment across both employees and team leads.
The large majority of programmers are finding these tools to be at least a 7/10 or higher in terms of helpfulness, which is pretty damn good.
There is still room for improvement which shouldn't come as a surprise given we're still in the early days but given this rating, we're surprised managers aren't encouraging usage of these tools even more.
It's fascinating to see the actual usage data that people report vs. their subjective opinions.
Most people seem to find them quite helpful already so are those also the people using them weekly or monthly? Or do people just have a positive view of them but that isn't actually translating into regular usage?
We went through our data to see if there was any correlation:
As you might have guessed, the more people used the tools, the higher they scored it in terms of helpfulness.
The question becomes though... is this a chicken and egg situation?
Because many of these tools are still so new, we feel it's the simple fact that people are still learning how to use them.
The more they actually use them, the more they see how other people are benefiting from them and the more the tools themselves continue to improve, the more helpful they will be for programmers.
But until they learn to use them effectively, it could seem like yet another thing to have to learn and figure out.
Even if managers and team leads aren't mandating usage of these tools yet, most programmers believe the writing is on the wall.
It makes sense that people would feel this way. Once developers learn to use these tools effectively, their productivity should greatly increase (as we've already seen from some of the respondents).
Rather than just looking at the broader audience, we decided to further break down this opinion by years of experience.
Overall, the consensus was quite clear across the board, with ~70-80% of programmers at all levels of experience believing that these tools will become standard requirements in the future.
The results
What was really interesting to see though was how this was also the opinion of programmers with the most experience in their roles.
Why is this important?
Well, these people have been around a long time and have seen a lot of trends come and go (with it being quite rare that something survives and sticks around).
So if they think it's here to stay, then that's worth paying attention to.
So, only slightly higher than the employee consensus of 80.1%.
However, this is another interesting situation where the actions of team leads today (only ~28% requiring their teams to learn these tools) is drastically different from where they believe things are going.
They're not forcing people to use them yet, but they definitely think people will need to use them in the future.
Add in the fact that these team leads are the people who will have a strong say in deciding whether these skills will be required or not (whether from new coders or existing team members upskilling), and this gives a more accurate representation of what will happen down the line.
If you're not using these tools yet, it seems like you'll need to learn them in the coming years.
We talked about this before in our hard truths about being a software engineer post, but a lot of the time, it can feel like you're rushed to get things finished in coding.
This means less time for testing, documentation, etc, and so you might cut corners a little or miss tasks that you would like to get finished.
And let's be honest, no one really enjoys testing, QA, and documentation so they tend to be the things that are ignored.
How could AI tools change this?
Forget about the potential of AI tools helping write new code. AI tools can already help you test your code, spot bugs, suggest fixes and even write documentation for you.
Even if programmers just learned how to properly use these AI tools to help with some of these mundane and admin tasks, that could result in a huge increase in the quality of code out there and increase efficiency across the board.
We are total believers here, and even have a few new courses in the works that will show you exactly how to leverage ChatGPT and other AI tools to make your life as a programmer so much easier
Make sure to subscribe at the bottom of the post if you want to find out when we release these new courses.
In the meantime, get up to speed on the fundamentals from our ChatGPT / large language model intro course.
Only a slightly larger % than the general audience.
This probably ties into why team leads think that these tools will become standard but it's still strange then as to why such a smaller percentage of these same team leads are actually requiring or encouraging their team members to learn them.
What will be the tipping point?
We have to imagine it will be once someone creates a cohesive training program of how to use these tools effectively perhaps?
This would reduce those major barriers that we saw earlier (time and effort to learn), while also giving systems and processes for how to use it for actual ongoing tasks vs random ideas, as it might be being used for right now.
This makes sense. If you have a new job and are at entry-level, you might be worried about a whole bunch of things, let alone a tool that claims to be able to do your job for you!
Honestly though, our view is that this is more likely imposter syndrome and being new in a role, coupled with compounding fears of the heavily publicized tech layoffs that happened around the same time as these tools picked up speed.
You can see this mirrored in the fact that as experience level grows, confidence in job security rises.
To be honest, we don’t think these tools are at a level yet where they could replace a human in any role, other than basic $5 tasks.
The real threat comes from peers who have embraced them and become that ‘10x level’ developer, while others get left behind.
However, the overwhelming majority (76.9%) feel that this won’t be the case.
Is it possible that the majority could be wrong? Of course. But throughout human history there have always been new tools that have changed work as we know it. The key is adapting and embracing these new tools, and how they effect change in their industry.
Sure it might shake up other industries, but given that programmers are already constantly required to be keeping their skills up-to-date, there's no reason why they won't adapt to using these tools either.
tl;dr: Roles that don't require much ongoing learning and change might have a tougher time adapting, but if you're a lifelong learner and embrace learning new things... you'll be fine.
And when we look at many of the comments from these thousands of programmers, almost all of them feel the same way... that their job will simply evolve to incorporate the usage of AI tools.
In fact, we feel so strongly about this topic that the founder of ZTM (Andrei Neagoie even just dropped a video on how to actually thrive with AI:
So there you have it. Hopefully, this survey has shed some light on the future of programming and AI tools and if you're a programmer yourself, perhaps alleviates some worries you might have.
Heck, maybe it's got you excited for what's to come and made you want to start learning and applying this now! Just imagine how much easier your job could be if you could get AI assistance for 10-30% of it or more.
As a final note, we just want to give a huge thank you to everyone who took the time to fill out this survey. We're already excited to do it again next year so we can start looking at the trends in 2024 as well.
Since we know some people will ask what our thoughts are, we added this in. Maybe we'll do a longer post on this in the coming weeks.
Here's the 30-second version...
AI tools will be like any other tool. If used properly, they'll simply help produce a better product or make a programmer more efficient. But it won't replace them (at least no tools we've seen so far to date).
We're also likely to see a huge uptick in job listings including experience with AI tools. Programmers still need to be properly trained to understand the output these tools are providing them and understand how that fits into a larger code base.
Programming fundamentals + real-world experience + institutional knowledge (ex: specifically how things work at your company or the nuances of your industry) aren't being replaced. They are all still key.
Depending on who you ask or the stats you look at, we actually have the opposite problem of developers being replaced and there's actually a shortage of developers.
Agree? Disagree? Let us know.
Share it with someone! We purposefully made it free and no email gating so anyone can access it anywhere, anytime.
Due to popular demand from the ZTM community and the programming community at large, we've decided to open-source the data so that anyone can do their own data analysis as well.
Access the full ZTM State of AI 2023 data set here.
Feel free to reference it and use the charts or data (we just appreciate if you cite us 🙂). And if you come up with any interesting findings that we missed, definitely let us know!