Skip to content
Open navigation
OpenOpen workspace

Stack Overflow Developer Survey 2026

AI in the workflow: Expect to use AI more for this by age

In the 35-44 years old group, 36% selected “Writing tickets, requirements, plans, or project updates”; in the Under 18 years old group, 13% did. Of the 19 answers tested, “Writing tickets, requirements, plans, or project updates” differs most by age, a small association: χ²(7, N = 10189) = 125.66, 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.

Published by crosstabs.com · Last updated ·
How results are checkedNamed 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 more for this by age: percentage of each group's respondents who selected each answer, and respondent counts
AI in the workflow: Expect to use AI more for thisUnder 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
Finding or fixing security issues34.2%5332.6%37542.0%B1,22047.3%ABCG1,51446.1%B80045.3%B33636.5%9244.2%1943.3%4,409
Debugging, troubleshooting, or refactoring code35.5%5540.0%46043.2%1,25742.8%1,37140.8%70848.5%BEa36044.4%11239.5%1742.6%4,340
Analyzing data, logs, metrics, or query results25.8%4030.6%35241.9%AB1,21746.7%ABCG1,49645.3%ABg78745.0%AB33435.3%8953.5%AB2342.6%4,338
Writing documentation, comments, or knowledge base content27.7%4336.9%42440.8%A1,18543.4%AB1,39241.7%A72447.6%ABC35340.5%10237.2%1641.6%4,239
Searching, summarizing, or interpreting internal knowledge21.3%3331.6%36342.3%AB1,23043.6%AB1,39643.2%AB75043.0%AB31935.3%a8944.2%a1941.2%4,199
Writing or improving tests26.5%4137.3%42941.9%A1,21941.9%A1,34439.3%A68245.6%ABe33840.1%10127.9%1240.9%4,166
Understanding or onboarding to a new codebase32.3%5034.6%39742.1%BG1,22442.4%BG1,35741.6%BG72340.2%g29829.8%7534.9%1540.6%4,139
Generating code in an unfamiliar area26.5%4131.0%35637.8%B1,09842.0%ABC1,34542.8%ABC74446.6%ABC34642.5%AB10732.6%1439.8%4,051
Answering complex or ambiguous technical questions22.6%3533.4%38436.3%A1,05439.7%AB1,27139.5%AB68641.6%AB30934.9%8837.2%1637.7%3,843
Reviewing code, pull requests, or design decisions19.4%3028.4%32635.4%AB1,02941.5%ABC1,33140.5%ABC70438.8%AB28834.1%A8639.5%1737.4%3,811
Generating code in a familiar area22.6%3533.2%38236.8%A1,07037.9%A1,21438.2%A66440.7%AB30240.9%A10332.6%1437.1%3,784
Answering straightforward technical questions20.6%3229.2%33532.1%a93235.3%AB1,13234.8%AB60436.8%AB27336.5%A9251.2%Ab2233.6%3,422
Architecture or technical design exploration14.2%2225.2%a29032.7%AB95236.2%AB1,16134.9%AB60632.6%AB24229.0%A7327.9%1233.0%3,358
Creating or configuring development/test environments16.8%2624.5%28231.1%AB90335.3%ABC1,13234.0%AB59136.0%AB26732.1%A8137.2%1632.4%3,298
Writing tickets, requirements, plans, or project updates12.9%2021.8%25130.9%ABG89935.6%ABCG1,14235.1%ABGc61030.6%ABg22720.6%5225.6%1131.5%3,212
Product, UX, or visual design22.6%3526.7%30727.0%78431.1%C99731.8%Cb55330.5%22624.6%6225.6%1129.2%2,975
Deploying, operating, or troubleshooting production systems16.8%2619.5%22423.2%67528.3%ABC90830.2%ABC52529.6%ABC22023.8%6030.2%1326.0%2,651
Writing emails, messages, summaries, or other communication11.0%1717.7%20323.0%AB66925.9%ABG83026.4%ABG45822.1%A16416.7%4223.3%1023.5%2,393
Generating visual, audio, or multimedia elements12.3%1914.4%16617.5%51022.8%BCa73025.7%ABC44626.0%ABC19327.4%ABC6920.9%921.0%2,142
Respondents1551,1492,9073,2041,7377422524310,189

A letter beside a percentage names the columns it is significantly higher than (uppercase 95%, lowercase 90%; pairwise column tests, Bonferroni-corrected). 20,714 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 “Writing tickets, requirements, plans, or project updates”

χ² = 125.66

df = 7, Holm-adjusted p < .001

Effect size

Cramér's V = 0.111

a small association

The strongest answer, APA-style: χ²(7, N = 10189) = 125.66, 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 = 10,189). The p-values are Holm-adjusted for the 19 answers tested; 19 of them differ by age at the 0.05 level.

AI in the workflow: Expect to use AI more for this by age: the test of each answer, selected against not selected, by age
AnswerSelectedχ² (df = 7)Adjusted pCramér's V
Finding or fixing security issues43.3%92.27< .0010.095
Debugging, troubleshooting, or refactoring code42.6%20.38.0050.045
Analyzing data, logs, metrics, or query results42.6%122.27< .0010.110
Writing documentation, comments, or knowledge base content41.6%39.40< .0010.062
Searching, summarizing, or interpreting internal knowledge41.2%85.59< .0010.092
Writing or improving tests40.9%33.81< .0010.058
Understanding or onboarding to a new codebase40.6%42.38< .0010.064
Generating code in an unfamiliar area39.8%82.97< .0010.090
Answering complex or ambiguous technical questions37.7%40.03< .0010.063
Reviewing code, pull requests, or design decisions37.4%99.14< .0010.099
Generating code in a familiar area37.1%29.24< .0010.054
Answering straightforward technical questions33.6%40.59< .0010.063
Architecture or technical design exploration33.0%76.60< .0010.087
Creating or configuring development/test environments32.4%71.54< .0010.084
Writing tickets, requirements, plans, or project updates31.5%125.66< .0010.111
Product, UX, or visual design29.2%28.66< .0010.053
Deploying, operating, or troubleshooting production systems26.0%75.16< .0010.086
Writing emails, messages, summaries, or other communication23.5%61.30< .0010.078
Generating visual, audio, or multimedia elements21.0%104.18< .0010.101

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 “Writing tickets, requirements, plans, or project updates” 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 10,189 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 “Writing tickets, requirements, plans, or project updates” 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

Source

Stack Overflow. 2026 Developer Survey, https://survey.stackoverflow.co/2026, licensed under the ODbL 1.0. Tabulated by crosstabs.com. Variables AIWorkExpectMore (AI in the workflow: Expect to use AI More or AI agents more 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.

  1. [1]Stack Overflow: 2026 Developer Survey public results (survey_results_public.csv)survey.stackoverflow.co
  2. [2]Stack Overflow: Open Database License (ODbL) 1.0opendatacommons.org