<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/infoq-culture-and-methods-trends-report---2026-5jsk00yw2" -->

---
title: InfoQ Culture and Methods Trends Report - 2026 | daily.dev
description: The InfoQ Culture and Methods editorial panel's 2026 trends report examines how AI is reshaping software engineering teams, roles, and practices. Key themes...
canonical: https://daily.dev/posts/infoq-culture-and-methods-trends-report---2026-5jsk00yw2
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: InfoQ Culture and Methods Trends Report - 2026 | daily.dev
og:description: The InfoQ Culture and Methods editorial panel's 2026 trends report examines how AI is reshaping software engineering teams, roles, and practices. Key themes...
og:url: https://daily.dev/posts/infoq-culture-and-methods-trends-report---2026-5jsk00yw2
og:image: https://api.daily.dev/og/posts/5JSk00yw2.png
og:image:alt: InfoQ Culture and Methods Trends Report - 2026
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# InfoQ Culture and Methods Trends Report - 2026

**[InfoQ](https://daily.dev/sources/infoq)** · 20 min read · 0 upvotes · 0 comments

## Summary

The InfoQ Culture and Methods editorial panel's 2026 trends report examines how AI is reshaping software engineering teams, roles, and practices. Key themes include the need for risk-based AI adoption maturity frameworks, the widening gap between organizations with and without agile foundations, and the explosion of AI-generated code creating cognitive load and quality challenges. GitHub pull requests are predicted to grow 14x to 14 billion in 2026, with 300% more code producing 400% more bugs. Engineers are shifting from contributors to custodians — building guardrails, validating AI output, and enabling non-engineers to contribute safely. Teams are shrinking from two-pizza to one-pizza size, roles are blurring, and diversity of thought is at risk when everyone uses agents trained on the same corpus. The panel also addresses psychological safety under AI-driven work intensification, the changing career path for junior engineers, accountability gaps in AI-generated systems, and the environmental cost of AI token consumption.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.infoq.com/articles/culture-trends-2026>

## Questions this post answers

### What percentage of committed code is now AI-generated and how much do developers trust it?

AI accounts for forty-two percent of committed code according to Sonar's 2026 State of Code Developer Survey, yet ninety-six percent of developers don't fully trust it, and only forty-eight percent always verify AI-generated code before committing it. This adoption-trust contradiction is pushing engineers toward building more guardrails and platform tooling to increase confidence in AI output.

_Track how trust and verification practices around AI-generated code evolve by following coding and AI trend coverage on daily.dev._

### How much is GitHub pull request volume expected to grow due to AI-generated code?

GitHub pull request volume is expected to grow roughly fourteen-fold, from about one billion pull requests to a predicted fourteen billion, alongside separately cited figures of three hundred percent more code being released producing four hundred percent more bugs. This volume increase is prompting calls to redesign code review processes, since traditional pull request review was not built for AI-scale output.

_Developers rethinking code review workflows for AI-scale output can follow related engineering practice discussions on daily.dev._

### Why do some experts say junior engineers are still essential in an AI-driven development environment?

Junior engineers possess learning plasticity that AI agents lack: they learn from a mistake once and generalize the lesson, such as recognizing when a library choice conflicts with platform conventions, rather than repeating errors. Senior engineers are spending significant effort correcting agents that repeat mistakes, while juniors naturally internalize lessons, making their development critical to sustaining engineering judgment over time.

_Engineering leaders weighing how to develop junior talent alongside AI tools can find related discussions on daily.dev._

## Similar posts on daily.dev

- [Culture & Methods Trends 2026: The Human Side of AI Engineering](https://daily.dev/posts/culture-methods-trends-2026-the-human-side-of-ai-engineering-vevsio7oz) · InfoQ · 0 upvotes · 0 comments
- [The InfoQ Trends Reports 2025 eMag](https://daily.dev/posts/the-infoq-trends-reports-2025-emag-k8nrvnuyq) · InfoQ · 0 upvotes · 0 comments
- [AI-assisted engineering: Q1 2026 impact report](https://daily.dev/posts/ai-assisted-engineering-q1-2026-impact-report-uheo22vla) · Software Engineering Research · 0 upvotes · 0 comments
- [AI in engineering: Q2 2026 benchmarks & research readout](https://daily.dev/posts/ai-in-engineering-q2-2026-benchmarks-research-readout-a5bsn2lal) · Engineering Enablement · 10 upvotes · 0 comments

---

Tags: [#ai](https://daily.dev/tags/ai), [#leadership](https://daily.dev/tags/leadership), [#agile](https://daily.dev/tags/agile), [#platform-engineering](https://daily.dev/tags/platform-engineering)

[View this post on daily.dev](https://daily.dev/posts/infoq-culture-and-methods-trends-report---2026-5jsk00yw2)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"InfoQ Culture and Methods Trends Report - 2026","url":"https://daily.dev/posts/infoq-culture-and-methods-trends-report---2026-5jsk00yw2","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/infoq-culture-and-methods-trends-report---2026-5jsk00yw2"},"datePublished":"2026-08-07T09:02:28.845Z","dateModified":"2026-09-13T18:30:41.638Z","description":"The InfoQ Culture and Methods editorial panel's 2026 trends report examines how AI is reshaping software engineering teams, roles, and practices. Key themes...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/49d407de5bc92e5508a964c851d86c51?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/49d407de5bc92e5508a964c851d86c51?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"InfoQ","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"InfoQ","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/afc3bced3e1e4b188dd9127017a60e0c","url":"https://daily.dev/sources/infoq"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/infoq-culture-and-methods-trends-report---2026-5jsk00yw2","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai,leadership,agile,platform-engineering","timeRequired":"PT20M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"InfoQ","item":"https://daily.dev/sources/infoq"},{"@type":"ListItem","position":3,"name":"InfoQ Culture and Methods Trends Report - 2026"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/infoq-culture-and-methods-trends-report---2026-5jsk00yw2#faq","mainEntity":[{"@type":"Question","name":"What percentage of committed code is now AI-generated and how much do developers trust it?","acceptedAnswer":{"@type":"Answer","text":"AI accounts for forty-two percent of committed code according to Sonar's 2026 State of Code Developer Survey, yet ninety-six percent of developers don't fully trust it, and only forty-eight percent always verify AI-generated code before committing it. This adoption-trust contradiction is pushing engineers toward building more guardrails and platform tooling to increase confidence in AI output. Track how trust and verification practices around AI-generated code evolve by following coding and AI trend coverage on daily.dev."}},{"@type":"Question","name":"How much is GitHub pull request volume expected to grow due to AI-generated code?","acceptedAnswer":{"@type":"Answer","text":"GitHub pull request volume is expected to grow roughly fourteen-fold, from about one billion pull requests to a predicted fourteen billion, alongside separately cited figures of three hundred percent more code being released producing four hundred percent more bugs. This volume increase is prompting calls to redesign code review processes, since traditional pull request review was not built for AI-scale output. Developers rethinking code review workflows for AI-scale output can follow related engineering practice discussions on daily.dev."}},{"@type":"Question","name":"Why do some experts say junior engineers are still essential in an AI-driven development environment?","acceptedAnswer":{"@type":"Answer","text":"Junior engineers possess learning plasticity that AI agents lack: they learn from a mistake once and generalize the lesson, such as recognizing when a library choice conflicts with platform conventions, rather than repeating errors. Senior engineers are spending significant effort correcting agents that repeat mistakes, while juniors naturally internalize lessons, making their development critical to sustaining engineering judgment over time. Engineering leaders weighing how to develop junior talent alongside AI tools can find related discussions on daily.dev."}}]}
```

