The State of Software Engineering in 2026: What Changed and What Did Not

Gergely Orosz reports from AI labs, startups and large technology companies.

GOGergely Orosz登壇者 · The Pragmatic Engineer
チャンネル
The Pragmatic Engineer
公開日
2026年10月6日
動画
29:39
読了時間
2 分
原文
英語
YouTube で開く
スクロールすると動画は右下に小さくなって再生を続けます。字幕は閲覧言語に合わせて切り替わります。
閲覧言語2 言語で読めます
この記事はまだ日本語に翻訳されていないため、英語の原文を表示しています。
要約

30 秒でわかる

Gergely Orosz examines agent-assisted coding, smaller projects, enduring team responsibilities and pressure on infrastructure. His September 2026 talk draws on company interviews and offers predictions about cloud agents and engineering practice.

  1. 1AI-assisted workMultiple agents and generated code are common in the organizations he visited.
  2. 2Company harnessesOrganizations integrate agents into their own development workflows.
  3. 3MigrationsMigration anecdotes need the context of earlier work.
  4. 4Teams still matterSmall projects still sit within teams responsible for software.
  5. 5Planning and validationFaster implementation does not eliminate planning or tests.
  6. 6Infrastructure pressureMore code can strain infrastructure; anecdotes alone cannot prove causes of defects.
  7. 7What comes nextOrosz expects more cloud agents and advises staying hands-on.

ポイント

  1. Multiple agents and generated code are common in the organizations he visited.
  2. Organizations integrate agents into their own development workflows.
  3. Migration anecdotes need the context of earlier work.
  4. Small projects still sit within teams responsible for software.
  5. Faster implementation does not eliminate planning or tests.
  6. More code can strain infrastructure; anecdotes alone cannot prove causes of defects.
  7. Orosz expects more cloud agents and advises staying hands-on.
全文

チャプターごとに整えた全文を読む

文字起こしのみ
01

What changed

Agents, harnesses and migration.

At LDX3 in September 2026, Gergely Orosz reports on conversations with AI labs, large technology companies and startups. His examples illuminate selected organizations rather than providing a representative survey of the whole industry.

Orosz observes that AI-generated code and multiple concurrent agents have become common in the organizations he visited. He cites engineers working across several tasks at once, but cautions that prominent AI companies are particularly advanced adopters.

Many companies are building their own agent harnesses. He describes tools that coordinate work, run in cloud environments and integrate with a company’s development processes; different organizations make different tradeoffs.

He gives examples of AI-assisted migrations, including Airbnb and Asana test-library transitions. Asana’s project had also benefited from years of earlier work, so short migration times should not be read without that context.

Some organizations report smaller project teams because individual engineers coordinate several agents. Orosz contrasts this with the continuing importance of teams that own software, share on-call responsibilities and cover for absences.

02

What stayed the same

Teams, planning and validation.

Planning and testing remain necessary: building the wrong thing faster is still wasteful, and generated code needs validation. He recounts a team’s experience that substantial testing effort remains alongside AI-written implementation.

03

What broke

Capacity, reliability and leadership pressures.

Orosz says the increase in code and pull requests strains existing assumptions and infrastructure. He also observes reliability problems in products he uses; his anecdotes do not by themselves establish their causes.

He describes CPU capacity constraints and long lead times reported by companies, as well as pressure on engineering leaders. These are time-specific reports and interviews, not universal claims about every cloud region or employer.

04

What comes next

Cloud agents and staying hands-on.

Looking ahead, Orosz expects more cloud agents, refactoring and investment in AI maturity. He advises engineers and leaders to stay hands-on, build supporting infrastructure and use AI to learn rather than delegate away their own understanding.

同じチャンネルの記事

1:41:17EN
The Pragmatic Engineer· 2026年10月28日ポッドキャスト · 2 人Titus Winters on Software Engineering, Teams and CS Educationゲスト Titus Winters · ホスト Gergely OroszA conversation on Google-scale refactoring, testing, AI and how engineers learn.Company BuildingLeadership
1:56:28EN
The Pragmatic Engineer· 2026年10月21日ポッドキャスト · 2 人Will Larson: The Revised Rules of Engineering Managementゲスト Will Larson · ホスト Gergely OroszThe 2010s taught engineering managers never to make a technical decision again. Will Larson, CTO of Imprint and author of Staff Engineer, argues that era is over: managers who cannot get back into the work are in a career trap.ManagementLeadershipCareer Growth+2
1:34:17EN
The Pragmatic Engineer· 2026年10月14日ポッドキャスト · 2 人Inside Uber’s Developer Infrastructure for AI Agentsゲスト Uday Kiran Medisetty · ホスト Gergely OroszUday Kiran Medisetty explains gateways, context, background coding and review.開発ワークフローとテストエージェント工学インフラとデプロイ
1:59:04EN
The Pragmatic Engineer· 2026年10月7日ポッドキャスト · 2 人Sam Newman on Resilient Distributed Systemsゲスト Sam Newman · ホスト Gergely OroszMicroservice tradeoffs, observability, retries and preserving understanding with AI.Software engineeringオブザーバビリティと信頼性
1:42:31EN
The Pragmatic Engineer· 2026年9月30日ポッドキャスト · 2 人Peter Mattis on Distributed Databases and Coding with AIゲスト Peter Mattis · ホスト Gergely OroszFrom Gmail and Colossus to CockroachDB, performance and agent-assisted engineering.Software engineeringインフラとデプロイコーディングエージェント
1:28:32EN
The Pragmatic Engineer· 2026年9月23日ポッドキャスト · 2 人Maggie Appleton on Design Engineering in the Age of Agentsゲスト Maggie Appleton · ホスト Gergely OroszSketches, live prototypes and human judgment in collaborative software design.プロダクトと UXSoftware engineeringエージェント工学