Stack Overflow Developer Survey 2026
AI in the workflow: Expect to use AI less for this by age
In the Under 18 years old group, 36% selected “Generating code in a familiar area”; in the 35-44 years old group, 13% did. Of the 19 answers tested, “Generating code in a familiar area” differs most by age, a small association: χ²(7, N = 5296) = 65.53, Holm-adjusted p < .001, V = .11. Respondents could select more than one answer, so the percentages add to more than 100%. These are unweighted respondents, not population estimates.
How results are checked
Named statistical review pending. Selected automated reference cases are published on the validation page.The table
The table
Question asked: Which parts of your workflow are you currently integrating into AI or using AI agents to accomplish? Will they be more or less integrated over the next year? Please select one for each scenario.
Respondents could select more than one answer. Shown by age, as the percentage of each group's respondents who selected each answer, with the number of respondents beneath. A respondent is counted in every row they selected, so a column adds to more than 100%.
| AI in the workflow: Expect to use AI less for this | Under 18 years old (A) | 18-24 years old (B) | 25-34 years old (C) | 35-44 years old (D) | 45-54 years old (E) | 55-64 years old (F) | 65 years or older (G) | Prefer not to say (H) | All |
|---|---|---|---|---|---|---|---|---|---|
| Answering complex or ambiguous technical questions | 26.6%38 | 24.7%204 | 27.8%482 | 24.9%365 | 22.4%162 | 20.9%56 | 17.0%17 | 34.4%11 | 25.2%1,335 |
| Generating code in an unfamiliar area | 28.7%41 | 31.8%DEF263 | 27.4%DEF476 | 22.1%324 | 19.6%142 | 16.8%45 | 18.0%18 | 34.4%11 | 24.9%1,320 |
| Reviewing code, pull requests, or design decisions | 19.6%28 | 18.9%156 | 20.2%351 | 20.5%301 | 15.7%114 | 16.4%44 | 20.0%20 | 12.5%4 | 19.2%1,018 |
| Debugging, troubleshooting, or refactoring code | 30.8%CDEfg44 | 20.9%173 | 18.9%328 | 16.8%246 | 17.1%124 | 17.5%47 | 14.0%14 | 34.4%11 | 18.6%987 |
| Architecture or technical design exploration | 23.8%F34 | 23.7%DEFg196 | 21.0%DEF364 | 16.4%241 | 14.5%105 | 10.8%29 | 10.0%10 | 12.5%4 | 18.6%983 |
| Writing emails, messages, summaries, or other communication | 12.6%18 | 12.7%105 | 16.0%277 | 20.0%Bc293 | 20.2%B146 | 25.7%BCa69 | 23.0%23 | 28.1%9 | 17.7%940 |
| Generating code in a familiar area | 36.4%BCDEFG52 | 20.8%D172 | 19.1%D332 | 13.4%196 | 16.2%117 | 16.0%43 | 16.0%16 | 28.1%9 | 17.7%937 |
| Answering straightforward technical questions | 19.6%28 | 15.5%128 | 17.3%301 | 16.7%245 | 15.1%109 | 16.0%43 | 20.0%20 | 21.9%7 | 16.6%881 |
| Writing tickets, requirements, plans, or project updates | 9.1%13 | 12.2%101 | 14.8%256 | 19.0%BCa279 | 17.7%b128 | 23.1%ABC62 | 16.0%16 | 21.9%7 | 16.3%862 |
| Deploying, operating, or troubleshooting production systems | 11.2%16 | 12.8%106 | 15.3%266 | 16.8%246 | 18.0%130 | 18.3%49 | 19.0%19 | 34.4%ABc11 | 15.9%843 |
| Writing documentation, comments, or knowledge base content | 16.8%24 | 15.6%129 | 16.0%278 | 14.5%213 | 15.7%114 | 15.3%41 | 15.0%15 | 21.9%7 | 15.5%821 |
| Creating or configuring development/test environments | 13.3%19 | 14.0%116 | 14.6%254 | 15.2%223 | 13.1%95 | 15.7%42 | 14.0%14 | 21.9%7 | 14.5%770 |
| Finding or fixing security issues | 14.0%20 | 15.7%130 | 13.6%236 | 13.4%197 | 15.9%115 | 16.8%45 | 16.0%16 | 18.8%6 | 14.4%765 |
| Understanding or onboarding to a new codebase | 18.9%27 | 15.0%124 | 12.0%208 | 12.5%183 | 11.6%84 | 12.7%34 | 14.0%14 | 12.5%4 | 12.8%678 |
| Searching, summarizing, or interpreting internal knowledge | 14.0%20 | 12.2%101 | 11.8%204 | 12.7%187 | 13.8%100 | 14.9%40 | 14.0%14 | 9.4%3 | 12.6%669 |
| Analyzing data, logs, metrics, or query results | 13.3%19 | 9.6%79 | 12.4%216 | 13.5%198 | 12.6%91 | 17.2%B46 | 9.0%9 | 18.8%6 | 12.5%664 |
| Writing or improving tests | 11.2%16 | 13.1%108 | 11.6%202 | 12.4%182 | 13.7%99 | 12.7%34 | 13.0%13 | 21.9%7 | 12.5%661 |
| Generating visual, audio, or multimedia elements | 10.5%15 | 7.9%65 | 10.4%180 | 12.3%B181 | 14.4%B104 | 16.8%Bc45 | 11.0%11 | 21.9%7 | 11.5%608 |
| Product, UX, or visual design | 14.0%20 | 11.9%98 | 10.7%186 | 10.0%147 | 10.8%78 | 13.1%35 | 11.0%11 | 25.0%8 | 11.0%583 |
| Respondents | 143 | 826 | 1,735 | 1,468 | 724 | 268 | 100 | 32 | 5,296 |
A letter beside a percentage names the columns it is significantly higher than (uppercase 95%, lowercase 90%; pairwise column tests, Bonferroni-corrected). 25,607 of 30,903 respondents have no answer to one of the two questions (not asked or not answered) and are left out.
Analysis
Results
Chi-square test of “Generating code in a familiar area”
χ² = 65.53
df = 7, Holm-adjusted p < .001
Effect size
Cramér's V = 0.111
a small association
The strongest answer, APA-style: χ²(7, N = 5296) = 65.53, Holm-adjusted p < .001, V = .11. Each answer is tested on its own, as the respondents who selected it against those who did not, across the 8 groups (N = 5,296). The p-values are Holm-adjusted for the 19 answers tested; 8 of them differ by age at the 0.05 level.
| Answer | Selected | χ² (df = 7) | Adjusted p | Cramér's V |
|---|---|---|---|---|
| Answering complex or ambiguous technical questions | 25.2% | 17.16 | .180 | 0.057 |
| Generating code in an unfamiliar area | 24.9% | 58.90 | < .001 | 0.105 |
| Reviewing code, pull requests, or design decisions | 19.2% | 10.72 | 1.000 | 0.045 |
| Debugging, troubleshooting, or refactoring code | 18.6% | 28.23 | .003 | 0.073 |
| Architecture or technical design exploration | 18.6% | 52.48 | < .001 | 0.100 |
| Writing emails, messages, summaries, or other communication | 17.7% | 44.54 | < .001 | 0.092 |
| Generating code in a familiar area | 17.7% | 65.53 | < .001 | 0.111 |
| Answering straightforward technical questions | 16.6% | 5.13 | 1.000 | 0.031 |
| Writing tickets, requirements, plans, or project updates | 16.3% | 37.36 | < .001 | 0.084 |
| Deploying, operating, or troubleshooting production systems | 15.9% | 21.70 | .034 | 0.064 |
| Writing documentation, comments, or knowledge base content | 15.5% | 2.70 | 1.000 | 0.023 |
| Creating or configuring development/test environments | 14.5% | 3.72 | 1.000 | 0.026 |
| Finding or fixing security issues | 14.4% | 6.47 | 1.000 | 0.035 |
| Understanding or onboarding to a new codebase | 12.8% | 10.59 | 1.000 | 0.045 |
| Searching, summarizing, or interpreting internal knowledge | 12.6% | 4.24 | 1.000 | 0.028 |
| Analyzing data, logs, metrics, or query results | 12.5% | 15.45 | .306 | 0.054 |
| Writing or improving tests | 12.5% | 5.17 | 1.000 | 0.031 |
| Generating visual, audio, or multimedia elements | 11.5% | 30.66 | .001 | 0.076 |
| Product, UX, or visual design | 11.0% | 11.13 | 1.000 | 0.046 |
How to read it
No single chi-square test covers this table. A respondent appears in every row they selected, so the rows are not separate groups of people, and a test of the whole table would count the same person several times. Each answer is tested on its own instead: did the share who selected it differ between the groups? Testing 19 answers gives 19 chances of a false alarm, so the p-values are Holm-adjusted to keep the chance of any false alarm in this table at 0.05.
For “Generating code in a familiar area” the test rejects independence at the 0.05 level (Holm-adjusted p < .001): differences this large between the groups are unlikely if selecting it did not depend on age. Cramér's V of 0.111 is in the small range, which is real but modest: knowing someone's group tells you only a little about their answer.
With 5,296 respondents, even small differences reach statistical significance. Read the percentages and the effect size before the p-value.
Limits
- The survey has no weights. These tables are unweighted counts of the people who answered, so they describe the respondents, not developers in general.
- The test treats respondents as a simple random sample. They are people who chose to answer a survey Stack Overflow promoted, not a random sample of developers, so a result holds for these respondents and may not hold beyond them.
- The adjustment covers the answers of this question by this group only, not the other tables in the library. The headline answer is the strongest of those tested, so its effect size is larger than a typical answer's.
- A difference between groups is not evidence that group membership causes the answer.
Next steps
Work with this table
Open the test of “Generating code in a familiar area” in the calculator
The link fills in the respondents who selected this answer and those who did not, by group. The whole table does not open there: its rows overlap, and the calculator's test needs rows that are separate people.
Open this question in the full file
The workspace opens all 30,903 respondents in your browser with this question selected. The survey has no weights, so the table there is unweighted too. Change the group, add a filter or export from there.
Open in the workspace →Run this on your own data — free, no signup
Upload a CSV, Excel, SPSS, Stata, SAS, R, Parquet or JSON file. Everything runs in your browser; your file never leaves your device.
Open the workspace →The same question by other groups
Other questions that differ by age
- Other work, school or life responsibilities by age
- How they learned to code in the past year by age
- Activities in a typical work week by age
- How they learned to code for AI in the past year by age
- Programming languages: Worked with in past year by age
- What prevents taking part in technical communities by age
Source
Stack Overflow. 2026 Developer Survey, https://survey.stackoverflow.co/2026, licensed under the ODbL 1.0. Tabulated by crosstabs.com. Variables AIWorkExpectLess (AI in the workflow: Expect to use AI or AI agents less for this) and Age. Stack Overflow licenses the survey data under the Open Database License (ODbL) 1.0 and its contents under the Database Contents License (DbCL) 1.0: credit Stack Overflow, keep the licence notice, and share any database made from the data under the ODbL. These tables and their downloads are offered on those terms.