The developer will be an agent conductor, not a coder
„The era of manual coding is over: the developer's value lies in specification, control, and judgment, and working in the profession is impossible without agent usage.”
Counter-narrative
A significant portion of developers avoid AI or use it only superficially, lack trust in it, and experience burnout, dependency, and hollowed-out work, as shown by a viral post about 'Enter-key pressing'. This is represented by Stack Overflow and Coddy surveys, a Dutch statement, a CNN report, and Sridhar Vembu's warning that understanding should not be handed over to AI.
Carriers
JetBrains, DORA, and Stack Overflow surveys, Microsoft (David Fowler), AMD (IEEE Spectrum report), An Anthropic executive, Amazon developer guidelines, LeadDev, Hungarian business conference media (Economx), György Bőgel
Analysis
The narrative concerns the profession's self-image. Usage is nearly universal; according to reports (AMD), engineering work is shifting from manual implementation toward specification and validation, and managers are returning to code. The same surveys show the tension: high usage alongside declining trust and enthusiasm, an 80% sense of dependency, 45% longer working hours, and performative usage. The conductor image is carried mainly by toolmakers and large-enterprise players (Microsoft, an Anthropic executive, Amazon). A weakness is that, according to DORA, AI does increase productivity, but delegating the entire development cycle backfires, and the Hungarian time-saving figure is self-reported. Burnout and loss of understanding are a recurring theme in reports and warnings (a viral post, Vembu), but are not independent measurements. Amazon's guidelines are correcting toward moderate, outcome-based use, whereas Google explicitly expects AI proficiency.
What's at stake: Whether the new identity of the development profession captures genuine added value or masks a slow loss of understanding and professional autonomy.
Narrative sub-threads
Agent usage as a professional entry point
Weekly or daily use of AI coding agents is common among the vast majority of developers, and some companies now mandate it, even making it exclusive.
This branch is based on usage rates and corporate policies, not on changes in the content of work or in trust.
→ lasting · evidence: moderateSpecification and validation instead of writing code
The focus of engineering work is shifting from manual implementation to specification, agent management, and result verification.
This branch describes the restructuring of daily workflows based on corporate cases and professional statements, not survey data.
↗ rising · evidence: moderateAI fluency replaces the coding interview
At some employers, measuring AI proficiency and AI-based evaluation are replacing traditional coding tests in recruitment selection.
This branch is tied to the employer selection mechanism and examines recruitment practices, not the work of existing developers.
→ lasting · evidence: strongJudgment: usage without trust
Developers widely use AI but trust it little in important decisions, while leaders ask for understanding and preservation of business results instead of mere usage.
This branch highlights the trust and perception gap using surveys and leadership guidelines, including rejection and performative usage.
→ lasting · evidence: moderateThe cost of the conductor's job: burnout
Agent-driven work brings dependency, longer hours, accelerated pace, and exhausting review burdens to developers.
This branch focuses on employee workload and well-being, relying on employee surveys and personal accounts, not on productivity or trust.
Sub-thread stories
Agent usage as a professional entry point
JetBrains survey: 90% of professionals use an AI coding agent weekly, Claude Code leadsCTOAgent use is widespread, so the realistic goal is managed adoption and policy rather than a ban.tech leadYour team's agent use needs to be assessed and regulated before shadow use develops.junior developerUsing agents is a baseline expectation; the ability to verify their output is the distinguishing skill.Survey: Claude Code overtakes GitHub Copilot, 90% of programmers use AI agentsCTOCompare your own toolset with the market usage trend, and reassess the share of Copilot licences.tech leadSet shared practices for agent use, since everyone on the team probably already uses one.junior developerUsing agents has become a baseline expectation; the skill of checking their output is what sets people apart.At Hungarian economic forum: software development without AI agents now unthinkableCTOAt Hungarian companies, agent use is now a baseline expectation, and in regulated sectors controls must be designed too.senior developerUsing agents has become an expected skill.82% of Hungarian developers use AI daily, saving 6.5 hours a weekjunior developerDaily AI use can now be considered a baseline expectation, so it is worth adapting your own workflow to it.senior developerPart of the time saved is best spent on review and planning, not just on writing more code.tech leadThe 6.5-hour weekly average is a measurable team-level target that can be compared against your own team's data.CTOAgainst the Hungarian benchmark, licence and training budgets may be worth revisiting; according to the articles, education is not keeping pace.startup founderAI use is widespread in the Hungarian developer market, so it needs to be factored into capacity planning.Share of developers using AI to write half or more of their code rises from 12% to 42% in a yearsenior developerWhen half the code comes from AI, review becomes the main value-creating task.tech leadReview capacity and coding guidelines need to be sized to the share of AI-generated code.CTOThe industry figure lets a team compare its level of AI use with the market average.JetBrains survey: 90% of developers use AI coding agents at work at least weeklyCTOAgent use is now widespread, so a team operating without a policy and a budget takes on risk.tech leadAlign the team's agent practices and measure their impact.junior developerUsing agents is an expected baseline skill.Czech IT firms: programmers banned from writing code, some laid offsenior developerPrepare for roles to change: review and specification may become the main task instead of writing code.CTOCompanies in the region already have examples of coding bans, so it is worth planning your own policy and retraining.Epic pushes developers into "AI-first" mode as Disney shooter slipssenior developerA management AI mandate often comes with schedule slippage; agree in advance what counts as meeting AI-first expectations.tech leadIf the AI mandate comes from above, clarify the quality and deadline constraints.junior developerIn games-industry jobs, expect that using AI tools may be required.Atlassian survey: over 95% of developers use AI, but delivery friction remainstech leadTeams should identify the steps in their processes where work piles up after coding gets faster.CTOAlongside investment in AI tools, plan for improving the delivery process as well.
Specification and validation instead of writing code
AMD's agent swarms are rewriting its software development workflow, IEEE Spectrum reportssenior developerThe centre of gravity of the job is shifting toward writing specifications and validating results, so these are the skills to build.tech leadTasks need to be broken down so that agents can work in parallel, with human review acting as a gate.Microsoft engineer says typing code is over as Aspire gets agent-friendly CLIsenior developerIn .NET, agents can control Aspire applications through the CLI and MCP.Gergely Orosz: Codex has "taken over" OpenAI as an agentic software factory takes shapetech leadOpenAI's internal example can be used to design an agent-centred development process.CTOThe report is a practical reference for organisational transformation.Case studies: DATEV's agent-based modernisation and Akka's spec-driven AI delivery tested on 65 projectstech leadThe structure of the specification and automated validation shape agent results, so it is worth testing this in your own process.senior developerIn a modernisation project, the success of agent work depends on the quality of the specification.Hungarian debate asks what happens to programming as a profession in the age of AI agentsjunior developerAlongside writing code, specification, review and checking AI output will become key skills.senior developerThe engineering role shifts toward overseeing AI-generated code and toward architecture.Anthropic: AI wrote 90% of Claude Code's code, with 30,000 changes a daytech leadWith a high share of AI-written code, scale review and infrastructure to the volume of changes.
AI fluency replaces the coding interview
Nexon replaces coding test with AI assessment in intern recruitmentjunior developerBe prepared for the hiring assessment to measure working with AI and justifying the results as well.tech leadConsider whether your own technical interviews measure the real quality of work done with AI.HackerRank unveils AI interviewer for hiring developersjunior developerJob interviews may include an AI interviewer, so it is worth practising this format.tech leadAI screening can reduce the hiring workload, but bias has to be checked.Google brings Gemini into software engineer interviewsjunior developerPrepare for interviews in which you work with AI tools, and show that you can verify their output.tech leadConsider redesigning your own hiring process so that it also evaluates AI use.senior developerAI fluency will increasingly be an expected competency.Anthropic manager says the coding interview is dead; Google asks for AI proficiencyjunior developerPrepare for interviews by practising how to evaluate and critically check AI output, not only algorithm problems.tech leadIn the hiring process, consider a task that measures how candidates judge work done with AI.senior developerWhen assessing candidates, judgement should matter more than code generation.
Judgment: usage without trust
DORA: 90% of tech professionals use AI, but about 30% barely trust its codetech leadEven with AI in use, human responsibility and review checkpoints must stay in place.CTOGiven the trust gap, it is worth tracking rework and defect rates, not just speed.Zoho's Sridhar Vembu to engineers: use AI, but do not hand over understandingtech leadSet a team-level rule that the author understands and can defend AI-generated code.junior developerLearn to explain code written by AI.Stack Overflow survey: AI use keeps rising while trust and enthusiasm falltech leadBuild a verification step into AI outputs, because developer trust is low.CTOHigh usage combined with low trust calls for training and quality control.Stack Overflow 2026 survey: developers use AI daily but trust it little with big decisionstech leadWhen introducing AI tools, keep review and human sign-off for big decisions, because the team trusts the tool on that basis too.senior developerGiven the data on burnout and AI distrust, it is worth naming within the team which tasks go to AI and which do not.CTOWhen choosing tools, take into account that developers expect source attribution, and that Copilot ranks behind Claude Code in the survey.Half of Dutch developers use AI mainly for show, report saystech leadUsage rates may hide formal compliance, so the real impact needs to be measured.CTOThe success of tool adoption should be measured by the results actually achieved.Surveys: a large share of developers try to avoid AItech leadBefore mandating AI use, assess why the team resists, because making it compulsory may meet pushback.senior developerDecide in your own workflow where AI delivers measurable benefit, and back that position with facts.Stack Overflow survey: developers use AI but barely trust itsenior developerKeep human oversight for important decisions (architecture, security); treat AI output as a draft.tech leadWrite down which tasks require mandatory human approval for AI-generated code.junior developerAlways understand and check AI output before you submit it.Surveys: most developers use AI, but few trust it with critical decisionstech leadSet rules for checking AI output, because trust in critical decisions is low.CTOBuild the adoption strategy so that it also brings in sceptical developers.Amazon tells its 'Renaissance Developer' not to chase token usagetech leadMeasure the team by business outcomes rather than AI-usage metrics.senior developerBe able to justify when using AI is not worthwhile.CTOToken-consumption targets can distort behaviour, so review the metrics.Amazon memo warns engineers about AI productivity trapssenior developerLarge companies are setting expectations for AI use, so you need to take clear ownership of your own responsibility.tech leadDefine what counts as real productivity, and do not measure only the volume of generated code.
The cost of the conductor's job: burnout
Developers say AI coding is addictive and brings a wave of burnouttech leadTeam workload and the rhythm of AI use must be managed deliberately, not just the speed of output.senior developerPlan limits and breaks to handle the review burden that follows agents.Survey: 80% of developers describe AI coding as an addictiontech leadMonitor team workload and burnout; AI-driven speed-ups do not automatically mean shorter working hours.senior developerKeep up manual problem-solving practice to guard against tool dependence.CTODo not tie AI use to extra work.European game developers fear faster pace more than job losstech leadAI-accelerated schedules carry a burnout risk, so planning should keep deadlines realistic.senior developerPressure on pace calls for concrete working rules, not just tools.Engineer says Claude Code made his job 'soul-sucking', with 12-hour days of pressing Entersenior developerSupervising agents is a cognitive burden, so plan time for understanding and review.tech leadWatch the team's workload and its actual understanding of the code.junior developerDeep understanding of code remains a distinguishing skill even when using agents.AI-generated code is burning out senior engineers in code review, analysis sayssenior developerRecurring review feedback should be recorded as rules so that automation can check it.tech leadPlan how review load is shared and how AI reviewers are introduced before reviewers burn out.
Google search interest
Hungary
| Topic and search term | Weekly | Average |
|---|---|---|
| The developer will be an agent conductor, not a coderAI programming | 0.5 | |
| Agent usage as a professional entry pointclaude code | 31.8 | |
| Specification and validation instead of writing codevibe coding | 0.5 | |
| AI fluency replaces the coding interviewAI skills | 0 | |
| Judgment: usage without trustAI reliability | 0 | |
| The cost of the conductor's job: burnoutprogrammer burnout | 0 |
World
| Topic and search term | Weekly | Average |
|---|---|---|
| The developer will be an agent conductor, not a coderai programming | 3.6 | |
| Agent usage as a professional entry pointclaude code | 63.4 | |
| Specification and validation instead of writing codevibe coding | 5.8 | |
| AI fluency replaces the coding interviewai skills | 10.5 | |
| Judgment: usage without trustai trust | 7.3 | |
| The cost of the conductor's job: burnoutdeveloper burnout | 0 |
Google Trends relative search index over the period studied, weekly average. A narrative and its sub-threads appear in a single comparison: 100 is the group's most-searched day, and the figures can only be compared within the group. The search term was chosen by machine analysis; it measures how much the term is searched, not how widespread the narrative is.
Who is affected and how
- senior developer
- Your value lies in judgment and system knowledge, so do not fully hand over understanding to the agent. Regularly work manually on critical parts to prevent your debugging skills from atrophying.
- junior developer
- To take on the conductor role, one must first know an instrument. Recruitment practices are transforming: Google expects AI proficiency and conducts Gemini-assisted interviews, while an Anthropic executive states that coding interviews no longer provide signals. Practice AI usage and code comprehension.
- tech lead
- The risk of performative usage and burnout is real. In the team, measure business results, not token consumption (Amazon guideline), and watch for work hour drift.
- CTO
- Mandatory AI use is not the same as effective use: a Dutch statement says half of Dutch developers use AI for show due to management expectations. Therefore, implementation must be accompanied by training and trust-building practices.
Hungary
At a domestic economic forum presentation described by Economx, it was stated that in software development, it is practically inconceivable for a developer not to use any AI agent (2026-09-07-39). A survey shows 82% of Hungarian developers use AI daily, saving an average of 6.5 work hours per week based on self-reporting (2026-09-14-03). György Bőgel states programming is turning into conversation with machines (2026-10-19-32). Domestic burnout and trust data do not appear in the examined stories.
At Hungarian economic forum: software development without AI agents now unthinkableCTOAt Hungarian companies, agent use is now a baseline expectation, and in regulated sectors controls must be designed too.senior developerUsing agents has become an expected skill.82% of Hungarian developers use AI daily, saving 6.5 hours a weekjunior developerDaily AI use can now be considered a baseline expectation, so it is worth adapting your own workflow to it.senior developerPart of the time saved is best spent on review and planning, not just on writing more code.tech leadThe 6.5-hour weekly average is a measurable team-level target that can be compared against your own team's data.CTOAgainst the Hungarian benchmark, licence and training budgets may be worth revisiting; according to the articles, education is not keeping pace.startup founderAI use is widespread in the Hungarian developer market, so it needs to be factored into capacity planning.Hungarian debate asks what happens to programming as a profession in the age of AI agentsjunior developerAlongside writing code, specification, review and checking AI output will become key skills.senior developerThe engineering role shifts toward overseeing AI-generated code and toward architecture.
Weekly trend
Turning points
JetBrains survey: 90% of professionals use an AI coding agent weekly, Claude Code leadsAccording to JetBrains' measurement, between May and July 2026, 90% of professional developers used an AI coding agent at least weekly. This put mass usage data behind the conductor metaphor.Engineer says Claude Code made his job 'soul-sucking', with 12-hour days of pressing EnterSeveral publications covered the viral post about 12–13-hour workdays consisting mostly of pressing Enter, so the counter-narrative of hollowed-out work has become part of the professional conversation.Stack Overflow survey: developers use AI but barely trust itAccording to a Stack Overflow survey of 30,903 developers, only 7% trust AI output in important decisions, adding lack of trust to the conductor role.
Related narratives in the News magazine
Supporting stories
Engineering managers return to the codebase as AI lowers the barriertech leadConsider how much time to spend coding with AI and what remains for leading the team.Stack Overflow monthly questions fall to 1,304 in July 2026junior developerProblem-solving increasingly relies on AI assistants and documentation, so critically checking output matters.senior developerA team's internal knowledge sharing and documentation will become more valuable than relying on public Q&A.AMD's agent swarms are rewriting its software development workflow, IEEE Spectrum reportssenior developerThe centre of gravity of the job is shifting toward writing specifications and validating results, so these are the skills to build.tech leadTasks need to be broken down so that agents can work in parallel, with human review acting as a gate.JetBrains survey: 90% of professionals use an AI coding agent weekly, Claude Code leadsCTOAgent use is widespread, so the realistic goal is managed adoption and policy rather than a ban.tech leadYour team's agent use needs to be assessed and regulated before shadow use develops.junior developerUsing agents is a baseline expectation; the ability to verify their output is the distinguishing skill.Developers say AI coding is addictive and brings a wave of burnouttech leadTeam workload and the rhythm of AI use must be managed deliberately, not just the speed of output.senior developerPlan limits and breaks to handle the review burden that follows agents.Survey: 80% of developers describe AI coding as an addictiontech leadMonitor team workload and burnout; AI-driven speed-ups do not automatically mean shorter working hours.senior developerKeep up manual problem-solving practice to guard against tool dependence.CTODo not tie AI use to extra work.DORA: 90% of tech professionals use AI, but about 30% barely trust its codetech leadEven with AI in use, human responsibility and review checkpoints must stay in place.CTOGiven the trust gap, it is worth tracking rework and defect rates, not just speed.Microsoft engineer says typing code is over as Aspire gets agent-friendly CLIsenior developerIn .NET, agents can control Aspire applications through the CLI and MCP.At Hungarian economic forum: software development without AI agents now unthinkableCTOAt Hungarian companies, agent use is now a baseline expectation, and in regulated sectors controls must be designed too.senior developerUsing agents has become an expected skill.European game developers fear faster pace more than job losstech leadAI-accelerated schedules carry a burnout risk, so planning should keep deadlines realistic.senior developerPressure on pace calls for concrete working rules, not just tools.82% of Hungarian developers use AI daily, saving 6.5 hours a weekjunior developerDaily AI use can now be considered a baseline expectation, so it is worth adapting your own workflow to it.senior developerPart of the time saved is best spent on review and planning, not just on writing more code.tech leadThe 6.5-hour weekly average is a measurable team-level target that can be compared against your own team's data.CTOAgainst the Hungarian benchmark, licence and training budgets may be worth revisiting; according to the articles, education is not keeping pace.startup founderAI use is widespread in the Hungarian developer market, so it needs to be factored into capacity planning.Engineer says Claude Code made his job 'soul-sucking', with 12-hour days of pressing Entersenior developerSupervising agents is a cognitive burden, so plan time for understanding and review.tech leadWatch the team's workload and its actual understanding of the code.junior developerDeep understanding of code remains a distinguishing skill even when using agents.Zoho's Sridhar Vembu to engineers: use AI, but do not hand over understandingtech leadSet a team-level rule that the author understands and can defend AI-generated code.junior developerLearn to explain code written by AI.Stack Overflow survey: AI use keeps rising while trust and enthusiasm falltech leadBuild a verification step into AI outputs, because developer trust is low.CTOHigh usage combined with low trust calls for training and quality control.Stack Overflow 2026 survey: developers use AI daily but trust it little with big decisionstech leadWhen introducing AI tools, keep review and human sign-off for big decisions, because the team trusts the tool on that basis too.senior developerGiven the data on burnout and AI distrust, it is worth naming within the team which tasks go to AI and which do not.CTOWhen choosing tools, take into account that developers expect source attribution, and that Copilot ranks behind Claude Code in the survey.Surveys: a large share of developers try to avoid AItech leadBefore mandating AI use, assess why the team resists, because making it compulsory may meet pushback.senior developerDecide in your own workflow where AI delivers measurable benefit, and back that position with facts.Half of Dutch developers use AI mainly for show, report saystech leadUsage rates may hide formal compliance, so the real impact needs to be measured.CTOThe success of tool adoption should be measured by the results actually achieved.Stack Overflow survey: developers use AI but barely trust itsenior developerKeep human oversight for important decisions (architecture, security); treat AI output as a draft.tech leadWrite down which tasks require mandatory human approval for AI-generated code.junior developerAlways understand and check AI output before you submit it.Hungarian debate asks what happens to programming as a profession in the age of AI agentsjunior developerAlongside writing code, specification, review and checking AI output will become key skills.senior developerThe engineering role shifts toward overseeing AI-generated code and toward architecture.Anthropic manager says the coding interview is dead; Google asks for AI proficiencyjunior developerPrepare for interviews by practising how to evaluate and critically check AI output, not only algorithm problems.tech leadIn the hiring process, consider a task that measures how candidates judge work done with AI.senior developerWhen assessing candidates, judgement should matter more than code generation.Amazon tells its 'Renaissance Developer' not to chase token usagetech leadMeasure the team by business outcomes rather than AI-usage metrics.senior developerBe able to justify when using AI is not worthwhile.CTOToken-consumption targets can distort behaviour, so review the metrics.Amazon memo warns engineers about AI productivity trapssenior developerLarge companies are setting expectations for AI use, so you need to take clear ownership of your own responsibility.tech leadDefine what counts as real productivity, and do not measure only the volume of generated code.
Machine analysis based on story titles and summaries, with a verification pass. The source of the facts is the article linked at each story.