# engineering-culture

A software-engineering concept concerning the practices, collaboration, and standards that shape how engineering teams develop and review software.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## DSF member of the month - Johannes Maron

DevFeed: [DSF member of the month - Johannes Maron](<https://devfeed.tech/articles/dsf-member-of-the-month-johannes-maron-146597.md>)

Original publisher: [Read original article](<https://www.djangoproject.com/weblog/2026/nov/20/dsf-member-of-the-month-johannes-maron/>)

Author: Sarah Abderemane

Published: 2026-11-20T13:00:00Z

Content type: article

Language: en

Sources: [The Django weblog](<https://devfeed.tech/sources/the-django-weblog.md>)

Topics: [Open Source](<https://devfeed.tech/topics/open-source.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Visual Studio Code](<https://devfeed.tech/topics/visual-studio-code.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [1-3](<https://devfeed.tech/tags/1-3.md>), [2025](<https://devfeed.tech/tags/2025.md>), [2026](<https://devfeed.tech/tags/2026.md>), [aws](<https://devfeed.tech/tags/aws.md>), [communication](<https://devfeed.tech/tags/communication.md>), [community](<https://devfeed.tech/tags/community.md>), [contributing](<https://devfeed.tech/tags/contributing.md>), [contributor](<https://devfeed.tech/tags/contributor.md>), [django](<https://devfeed.tech/tags/django.md>), [email](<https://devfeed.tech/tags/email.md>), [framework](<https://devfeed.tech/tags/framework.md>), [free](<https://devfeed.tech/tags/free.md>), [hijack](<https://devfeed.tech/tags/hijack.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [libraries](<https://devfeed.tech/tags/libraries.md>), [november-2026](<https://devfeed.tech/tags/november-2026.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [python](<https://devfeed.tech/tags/python.md>), [relay](<https://devfeed.tech/tags/relay.md>), [sentry](<https://devfeed.tech/tags/sentry.md>), [service](<https://devfeed.tech/tags/service.md>), [sms](<https://devfeed.tech/tags/sms.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### AI overview

Johannes Maron, a Django contributor and member of its Review and Triage team, says he began using Django for his first company and has used it at each company since. He helps maintain community projects, often taking over packages he needs when they are unmaintained; he favors extensible architecture, few settings, documentation improvements, and guiding users to implement some features themselves. He started recurring FOSS Fridays to help people contribute value by reviewing pull requests. He is wary of unsolicited feature proposals and resume-driven patches because they can create maintenance burdens. Maron describes relay as a communications service for email, SMS, and VoIP, and says he offers it free to nonprofits and community projects while aiming to return proceeds to the community. He distinguishes personal donations as appreciation from corporate sponsorship, which he considers structurally flawed, and hopes the Django Software Foundation can build assets and become less dependent on sponsorship.

### Source excerpt

For November 2026, we welcome Johannes Maron as our DSF member of the month! ⭐ Johannes has long been part of the Django community. He is a frequent contributor including project such as django-hijack which has more than 1.7K stars! He is part of the Django Review and Triage team. He is a DSF member since September 2025. You can learn more about Johannes by visiting Johannes' website and his GitHub Profile. Let's spend some time getting to know Johannes better! Can you tell us a little about yourself? (hobbies, education, etc) Johannes Maron, or joe, born Johannes Hoppe in the GDR. Raised in West Germany only to return to his home state for uni. Studied software engineering at the Hasso-Plattner institute, dropped out and lived the start-up life. I still live in Potsdam and have the most amazing pug, son and wife (in alphabetical order). I have an idea but where your nickname "codingjoe" comes from? I am joe, and I code. Honestly, I was young, and I am just happy it's not naughtyb0i420 and thus never changed it. How did you start using Django? I started using Django for my very first company, I believe it was version 1.3? I have used it for every company I build ever since, and would always do it again. What other framework do you know and if there is anything you would like to have in Django if you had magical powers? Who said I don't have magic powers? The magic of contributing, we all have it and I made good use of it over the years. But my biggest dream would probably be a browser working group to overcome Django's JavaScript hesitance. What projects are you working on now? relay, a communication as a service provider. Think Sentry but for email, SMS, or VoIP. Or like AWS, but instead of shooting Katy Perry into space I hope to funnel the proceeds back into the community that it's build upon. Diamond sponsor or die is what I am aiming for. Until I get there, I am offering all services for free to non-profits or community projects. Which Django libraries are your

## CEO Nadella Says "Not Everything Can Stay the Same": How 60,000 VEOs Relate to Microsoft's AI Transformation

DevFeed: [CEO Nadella Says "Not Everything Can Stay the Same": How 60,000 VEOs Relate to Microsoft's AI Transformation](<https://devfeed.tech/articles/ceo-nadella-says-not-everything-can-stay-the-same-how-60-000-veos-relate-to-microsoft-s-ai-transformation-144534.md>)

Original publisher: [Read original article](<https://joho-todai.com/en/nadella-ceo-veo-ai-transformation/>)

Author: Toru Misaki

Published: 2026-11-19T19:35:07Z

Content type: news

Language: en

Sources: [Joho no Todai](<https://devfeed.tech/sources/joho-no-todai.md>)

Topics: [Microsoft](<https://devfeed.tech/topics/microsoft.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Frontier AI](<https://devfeed.tech/topics/frontier-ai.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [acceptance](<https://devfeed.tech/tags/acceptance.md>), [acceptance-rate](<https://devfeed.tech/tags/acceptance-rate.md>), [account](<https://devfeed.tech/tags/account.md>), [added](<https://devfeed.tech/tags/added.md>), [after](<https://devfeed.tech/tags/after.md>), [ai](<https://devfeed.tech/tags/ai.md>), [can](<https://devfeed.tech/tags/can.md>), [ceo](<https://devfeed.tech/tags/ceo.md>), [change](<https://devfeed.tech/tags/change.md>), [company](<https://devfeed.tech/tags/company.md>), [employees](<https://devfeed.tech/tags/employees.md>), [exit](<https://devfeed.tech/tags/exit.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [offers](<https://devfeed.tech/tags/offers.md>), [organizational](<https://devfeed.tech/tags/organizational.md>), [podcast](<https://devfeed.tech/tags/podcast.md>), [program](<https://devfeed.tech/tags/program.md>), [satya-nadella](<https://devfeed.tech/tags/satya-nadella.md>), [teams](<https://devfeed.tech/tags/teams.md>)

### AI overview

Nadella said AI will change Microsoft's team sizes and workflows, and its 200,000-plus employees will need to be redeployed; he did not say the VEOs were a precursor to AI-driven layoffs. He encouraged employees on teams that have not adapted to move to other Microsoft teams, while saying he did not want them to leave. The VEO covers about 60,000 employees at level 70 or below in the United States, Canada, the United Kingdom, and India, with no age or tenure requirements; Microsoft expects under 5% acceptance. Nadella said AI writes 20-30% of Microsoft's code, making verification harder as code generation gets cheaper. He described plans to redeploy existing staff before adding graduates and identified customer-facing Forward Deployed Engineer roles as among the company's fastest-growing.

### Source excerpt

Microsoft CEO Satya Nadella, whose company offered a voluntary exit program to 60,000 employees, addressed the relationship between AI-driven organizational change and the exit offers on a podcast. He said plainly that the shape of teams will change.

## Perceived Effectiveness of Social Debt Mitigation Measures: A Preliminary Vignette-Based Survey

DevFeed: [Perceived Effectiveness of Social Debt Mitigation Measures: A Preliminary Vignette-Based Survey](<https://devfeed.tech/articles/perceived-effectiveness-of-social-debt-mitigation-measures-a-preliminary-vignette-based-survey-142139.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.23263>)

Author: Philipp M. Z\\"ahl, Tom Siegel, Robin Kha, Chaitanya Chikkala, Zo\\'e Lermusiaux, Anika Hennig

Published: 2026-11-19T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [knowledge-management](<https://devfeed.tech/topics/knowledge-management.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [abstract](<https://devfeed.tech/tags/abstract.md>), [advanced](<https://devfeed.tech/tags/advanced.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [based](<https://devfeed.tech/tags/based.md>), [bayesian](<https://devfeed.tech/tags/bayesian.md>), [best](<https://devfeed.tech/tags/best.md>), [bottleneck](<https://devfeed.tech/tags/bottleneck.md>), [but](<https://devfeed.tech/tags/but.md>), [change](<https://devfeed.tech/tags/change.md>), [channel](<https://devfeed.tech/tags/channel.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [communication](<https://devfeed.tech/tags/communication.md>), [consider](<https://devfeed.tech/tags/consider.md>), [convenience](<https://devfeed.tech/tags/convenience.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [design](<https://devfeed.tech/tags/design.md>), [effectiveness](<https://devfeed.tech/tags/effectiveness.md>), [mitigation](<https://devfeed.tech/tags/mitigation.md>), [social](<https://devfeed.tech/tags/social.md>), [survey](<https://devfeed.tech/tags/survey.md>)

### AI overview

A vignette survey of 23 IT professionals and advanced students found one clear favorite among 41 social debt mitigation measures: consolidating communication into a single primary channel for Communication Breakdown (P(best)=0.91). For the other five problem dimensions, preferred measures--including structured knowledge transfer and blameless retrospectives--had only moderate support (P(best)=0.38-0.58). Structural measures that reorganize information, decisions, and knowledge scored 0.3-0.4 points higher than role-based or attitudinal measures across scenarios, though not in every scenario. The small convenience sample makes these exploratory findings, rather than firm recommendations.

### Source excerpt

arXiv:2611.23263v1 Announce Type: new Abstract: Software engineering is a socio-technical discipline in which unresolved social and organizational problems accumulate as social debt, gradually eroding collaboration and project health. The literature offers a solid vocabulary for these problems but says little about which countermeasures practitioners consider effective. We address this gap with a vignette-based survey: six social debt problem dimensions (Organizational Silo, Newcomer Isolation, Communication Breakdown, Knowledge Bottleneck, Cultural and Geographical Distance, Psychological Safety Deficit) were presented as realistic team scenarios, and 23 IT professionals and advanced students rated 41 literature-derived mitigation measures. Rankings were analyzed with paired t-tests and a hierarchical Bayesian model that accounts for the within-subject design and yields, for each measure, the probability of being the best option in its scenario. Only for Communication Breakdown is the answer unambiguous: consolidating communication into a single primary channel is almost certainly preferred (P(best)=0.91). For the other five dimensions, the model identifies favorites with moderate evidence (P(best) between 0.38 and 0.58), such as structured knowledge transfer and blameless retrospectives. Across scenarios, structural measures that change how information, decisions, and knowledge are organized were rated higher than role-based or attitudinal measures (by 0.3 to 0.4 scale points), although not in every scenario. Given the small convenience sample, the results are exploratory, but they offer software engineering managers an evidence-graded starting point for selecting mitigation measures.

## Two decades of The Apache Way: Celebrating 20 years of Google and the Apache Software Foundation

DevFeed: [Two decades of The Apache Way: Celebrating 20 years of Google and the Apache Software Foundation](<https://devfeed.tech/articles/two-decades-of-the-apache-way-celebrating-20-years-of-google-and-the-apache-software-foundation-144106.md>)

Original publisher: [Read original article](<http://opensource.googleblog.com/2026/11/two-decades-of-the-apache-way-google-asf-20-years.html>)

Author: Google Open Source (noreply@blogger.com)

Published: 2026-11-18T19:30:00Z

Content type: article

Language: en

Sources: [Google Open Source Blog](<https://devfeed.tech/sources/google-open-source-blog.md>)

Topics: [Open Source](<https://devfeed.tech/topics/open-source.md>), [open source maintenance](<https://devfeed.tech/topics/open-source-maintenance.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Cloud Dataflow](<https://devfeed.tech/topics/cloud-dataflow.md>), [Apache Spark](<https://devfeed.tech/topics/spark.md>), [Open Source Models & Datasets](<https://devfeed.tech/topics/open-source-models-datasets.md>), [Machine learning](<https://devfeed.tech/topics/machine-learning.md>), [gemma](<https://devfeed.tech/topics/gemma.md>)

Tags: [2006](<https://devfeed.tech/tags/2006.md>), [2016](<https://devfeed.tech/tags/2016.md>), [ai](<https://devfeed.tech/tags/ai.md>), [airflow](<https://devfeed.tech/tags/airflow.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [apache](<https://devfeed.tech/tags/apache.md>), [apache-2-0](<https://devfeed.tech/tags/apache-2-0.md>), [apache-airflow](<https://devfeed.tech/tags/apache-airflow.md>), [apache-software-foundation](<https://devfeed.tech/tags/apache-software-foundation.md>), [apache-spark](<https://devfeed.tech/tags/apache-spark.md>), [asf](<https://devfeed.tech/tags/asf.md>), [batch](<https://devfeed.tech/tags/batch.md>), [beam](<https://devfeed.tech/tags/beam.md>), [big-data](<https://devfeed.tech/tags/big-data.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-dataflow](<https://devfeed.tech/tags/cloud-dataflow.md>), [code](<https://devfeed.tech/tags/code.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [communities](<https://devfeed.tech/tags/communities.md>), [community](<https://devfeed.tech/tags/community.md>), [google](<https://devfeed.tech/tags/google.md>), [google-supports-oss](<https://devfeed.tech/tags/google-supports-oss.md>), [open-source](<https://devfeed.tech/tags/open-source.md>)

### AI overview

Google's relationship with the Apache Software Foundation (ASF), formalized in 2006, continues through sponsorship, upstream contributions, and shared support for open, vendor-neutral, community-led development. Google says its contributor license agreements draw on ASF models and Apache 2.0 is its preferred code license, also used for open hardware and models such as Gemma 4. Examples of collaboration include donating Dataflow SDK components that helped establish Apache Beam; managed Google Cloud services built on Airflow and Spark; and BigQuery support for Apache Iceberg. Google was the ASF's first Platinum Sponsor and contributes funding and cloud infrastructure; Googlers also serve as committers and PMC members, while ASF has participated in Google Summer of Code for over 20 years. The text points to open data, cloud infrastructure, and AI as areas for future collaboration.

### Source excerpt

by Mike Bufano, Open Source Programs Office In 2006, Google formalized its relationship with the Apache Software Foundation (ASF) as one of its first corporate sponsors and twenty years later, that partnership continues through ongoing sponsorship and upstream contributions. At the core of our collaboration is a shared belief in "The Apache Way" and its principles of open, vendor-neutral, and community-led development. From the early days of corporate open source to modern machine learning and open data systems, Google and ASF communities have collaborated on widely used open source software. Shaping how Google does open source When we established Google's open source contribution workflow, we drew on established ASF practices. Both our Individual and Corporate Contributor License Agreements (CLAs), which external developers sign before contributing to a Google-owned open source project, are based on the ASF's CLAs. The Apache 2.0 license also remains Google's preferred open source license for code. Alongside our traditional software releases, we also use Apache 2.0 for open hardware designs and open models like Gemma 4. Co-engineering upstream and in the cloud Across Google Cloud, our engineering teams contribute code upstream alongside Apache project communities and build managed services directly around those open standards: Google Cloud Dataflow & Apache Beam: Drawing on Google's internal Flume and Dataflow systems, Google donated the original Dataflow SDK and runners to the Apache Incubator in 2016 to help establish Apache Beam as a vendor-neutral open standard for unified batch and stream processing. Google Cloud Managed Service for Apache Airflow & Apache Airflow: Managed workflow orchestration built on Apache Airflow, helping engineering and data teams author, schedule, and monitor complex pipelines. Google Cloud Managed Service for Apache Spark & Apache Spark: Managed big data and analytics processing built on Apache Spark, running directly on Google's clou

## Who protects the antivirus? How we secure Malwarebytes itself

DevFeed: [Who protects the antivirus? How we secure Malwarebytes itself](<https://devfeed.tech/articles/who-protects-the-antivirus-how-we-secure-malwarebytes-itself-140620.md>)

Original publisher: [Read original article](<https://www.malwarebytes.com/blog/inside-malwarebytes/2026/11/who-protects-the-antivirus-how-we-secure-malwarebytes-itself>)

Author: Anna Tukhtarova

Published: 2026-11-18T13:32:54Z

Content type: article

Language: en

Sources: [Malwarebytes](<https://devfeed.tech/sources/malwarebytes.md>)

Topics: [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>), [malware scanners](<https://devfeed.tech/topics/malware-scanners.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-models](<https://devfeed.tech/tags/ai-models.md>), [ai-security](<https://devfeed.tech/tags/ai-security.md>), [antivirus](<https://devfeed.tech/tags/antivirus.md>), [attack-surface](<https://devfeed.tech/tags/attack-surface.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [background](<https://devfeed.tech/tags/background.md>), [backlog](<https://devfeed.tech/tags/backlog.md>), [buffer](<https://devfeed.tech/tags/buffer.md>), [bug](<https://devfeed.tech/tags/bug.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [build-tools](<https://devfeed.tech/tags/build-tools.md>), [built-in](<https://devfeed.tech/tags/built-in.md>), [engineers](<https://devfeed.tech/tags/engineers.md>), [inside-malwarebytes](<https://devfeed.tech/tags/inside-malwarebytes.md>), [malwarebytes](<https://devfeed.tech/tags/malwarebytes.md>), [prevent](<https://devfeed.tech/tags/prevent.md>), [product](<https://devfeed.tech/tags/product.md>)

### AI overview

Malwarebytes says it protects its high-privilege Windows antivirus through a continuous prevent, detect, fix, and learn process. Its UI runs as the signed-in user while a background service runs as SYSTEM; because other same-user processes can call the service's COM methods, the service authenticates callers and checks authorization for each privileged operation. Practices described include threat modeling, least privilege, minimal interfaces, secure coding and compiler protections, static and dynamic analysis, internal AI scanning and pull-request review, fuzzing, and continuous repository checks. Findings are reproduced, scored, assigned owners and deadlines, then fixed and shipped in signed updates; each fix adds regression tests and fuzz inputs, and teams search for similar flaws. AI helps investigate and propose fixes, but engineers verify findings and changes. The approach costs roughly 10-20% of sprint time, generates review noise, adds tests to maintain, and imposes runtime overhead. Fixes must also preserve protection, performance, and system stability.

### Source excerpt

Imagine a piece of malware that can disable your antivirus and leave you unprotected. That's exactly what we as engineers work to prevent.

## Building InnerSource practices with an internal developer portal

DevFeed: [Building InnerSource practices with an internal developer portal](<https://devfeed.tech/articles/building-innersource-practices-with-an-internal-developer-portal-141888.md>)

Original publisher: [Read original article](<https://www.port.io/blog/building-innersource-practices>)

Author: Aidan O'Connor

Published: 2026-11-18T06:30:48Z

Content type: article

Language: en

Sources: [Port](<https://devfeed.tech/sources/developer-experience-platform-engineering-blog-port.md>)

Topics: [internal developer portal](<https://devfeed.tech/topics/internal-developer-portal.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [internal developer platform automation](<https://devfeed.tech/topics/internal-developer-platform-automation.md>), [Platform Engineering](<https://devfeed.tech/topics/platform-engineering.md>)

Tags: [ai-software-factory](<https://devfeed.tech/tags/ai-software-factory.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [developer-portal](<https://devfeed.tech/tags/developer-portal.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [innersource](<https://devfeed.tech/tags/innersource.md>), [internal-developer-portal](<https://devfeed.tech/tags/internal-developer-portal.md>), [practices](<https://devfeed.tech/tags/practices.md>)

### AI overview

An internal developer portal can help make InnerSource practical, though the article says no single tool ensures adoption. It outlines five uses: publish trusted committers, their contribution guidance and schedules; catalog repositories across separate source control systems so teams can discover service ownership and contribution details without exposing source code; route repository access requests to the appropriate approver; scaffold new services with InnerSource documentation such as README.md and CONTRIBUTING.md; and use service scorecards to track compliance gaps and guide time-bound improvements. These steps aim to improve reuse and cross-team contribution while reducing the need to consolidate repositories or coordinate setup through separate tickets. The excerpt notes that trusted committers spend time mentoring and reviewing rather than coding, and suggests recording that work through portal metrics.

### Source excerpt

Learn how to build inner source practices to improve collaboration, code reuse, and cross-team innovation in engineering organizations.

## More Secure Software Development via Cultural Analysis: How could Log4Shell happen?

DevFeed: [More Secure Software Development via Cultural Analysis: How could Log4Shell happen?](<https://devfeed.tech/articles/more-secure-software-development-via-cultural-analysis-how-could-log4shell-happen-137951.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.18565>)

Author: Lutz Prechelt, Lasse Fischer

Published: 2026-11-17T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Application Security](<https://devfeed.tech/topics/application-security.md>), [code security](<https://devfeed.tech/topics/code-security.md>)

Tags: [cs-se](<https://devfeed.tech/tags/cs-se.md>), [log4shell](<https://devfeed.tech/tags/log4shell.md>), [secure-software-development](<https://devfeed.tech/tags/secure-software-development.md>)

### AI overview

The abstract proposes cultural analysis as a way to help prevent vulnerabilities: identify the team values that contributed to a past vulnerability, then change those values to reduce future risk. It suggests that repeated studies could reveal broader patterns useful to software developers. The excerpt does not provide specific findings about how Log4Shell occurred.

### Source excerpt

arXiv:2611.18565v1 Announce Type: new Abstract: There is little progress avoiding vulnerabilities. Cultural analysis may help: For a given team, find the specific cultural values that led to a past vulnerability, then modify the values accordingly for the future. After enough such studies, patterns will likely emerge that are useful for the development community at large.

## Where AI Use Is Normalized, Author Seniority but Not AI Disclosure Biases Code Review

DevFeed: [Where AI Use Is Normalized, Author Seniority but Not AI Disclosure Biases Code Review](<https://devfeed.tech/articles/where-ai-use-is-normalized-author-seniority-but-not-ai-disclosure-biases-code-review-137958.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.18572>)

Author: Jenna Butler, Emerson Murphy-Hill, Constance Hadley, Alexa Tipton, Nancy Baym, Sankeerti Haniyur, Jina Suh

Published: 2026-11-17T05:00:00Z

Content type: news

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Code review](<https://devfeed.tech/topics/code-review.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>)

Tags: [abstract](<https://devfeed.tech/tags/abstract.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-disclosure](<https://devfeed.tech/tags/ai-disclosure.md>), [ai-use](<https://devfeed.tech/tags/ai-use.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [bias](<https://devfeed.tech/tags/bias.md>), [but](<https://devfeed.tech/tags/but.md>), [can](<https://devfeed.tech/tags/can.md>), [code](<https://devfeed.tech/tags/code.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [commit](<https://devfeed.tech/tags/commit.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [disclosure](<https://devfeed.tech/tags/disclosure.md>), [display](<https://devfeed.tech/tags/display.md>), [effectiveness](<https://devfeed.tech/tags/effectiveness.md>), [embedded](<https://devfeed.tech/tags/embedded.md>), [engineers](<https://devfeed.tech/tags/engineers.md>), [evaluations](<https://devfeed.tech/tags/evaluations.md>), [experiment](<https://devfeed.tech/tags/experiment.md>), [information](<https://devfeed.tech/tags/information.md>), [review](<https://devfeed.tech/tags/review.md>)

### AI overview

In a within-subjects experiment at an organization where AI use was normalized, 447 software engineers reviewed four code snippets with AI-use disclosure and author-seniority labels shown in commit messages. Disclosure did not bias perceived code effectiveness or author competence, while seniority labels significantly biased both. The result indicates no detected penalty for disclosed AI use in this setting; it does not establish that disclosure has no effect in other settings.

### Source excerpt

arXiv:2611.18572v1 Announce Type: new Abstract: Code-review tools increasingly display whether an author used AI when preparing pull requests. Recent studies report that AI disclosure makes reviewers rate otherwise identical work as less competent, with the penalty falling hardest on already-marginalized authors. In a within-subjects experiment in an AI-normalized organization, 447 software engineers each reviewed the same four code snippets under an AI-use disclosure embedded in the commit message and author-seniority labels. AI disclosure did not bias perceptions of code effectiveness or author competence, whereas a seniority label significantly biased both. Together, these findings show no detected penalty for disclosed AI use in this setting, while confirming that the author information shown in code review can still bias evaluations.

## Level Up! AI-Driven Challenges and Adaptations to Code Review Practices

DevFeed: [Level Up! AI-Driven Challenges and Adaptations to Code Review Practices](<https://devfeed.tech/articles/level-up-ai-driven-challenges-and-adaptations-to-code-review-practices-137975.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.18939>)

Author: Kaia Newman, Christian Bird, Jenna Butler, Emerson Murphy-Hill

Published: 2026-11-17T05:00:00Z

Content type: news

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Code review](<https://devfeed.tech/topics/code-review.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [ai code review](<https://devfeed.tech/topics/ai-code-review.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>)

Tags: [abstract](<https://devfeed.tech/tags/abstract.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [attention](<https://devfeed.tech/tags/attention.md>), [authoring](<https://devfeed.tech/tags/authoring.md>), [bottleneck](<https://devfeed.tech/tags/bottleneck.md>), [can](<https://devfeed.tech/tags/can.md>), [challenges](<https://devfeed.tech/tags/challenges.md>), [changes](<https://devfeed.tech/tags/changes.md>), [code](<https://devfeed.tech/tags/code.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [company](<https://devfeed.tech/tags/company.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [design](<https://devfeed.tech/tags/design.md>), [developers](<https://devfeed.tech/tags/developers.md>), [practices](<https://devfeed.tech/tags/practices.md>), [review](<https://devfeed.tech/tags/review.md>), [up](<https://devfeed.tech/tags/up.md>)

### AI overview

A mixed-methods study at a large multinational software company (24 interviews and a 2,590-person survey) found that AI-assisted coding shifts reviewers toward design and intent while adding review burden through reduced author stewardship and larger or more numerous pull requests, with potential downstream debt. Use of AI for review was not correlated with less difficulty keeping up with pull request volume, so it alone did not resolve the challenge. Developers identified organizational support and resourcing for review, moving review work upstream, and focusing reviewer attention on the most important concerns as useful strategies.

### Source excerpt

arXiv:2611.18939v1 Announce Type: new Abstract: AI can write code faster than humans can review, causing a bottleneck and necessitating changes to code review practices. This bottleneck is hotly debated, giving rise to two extreme and orthogonal imagined futures: one where humans continue to be firmly entrenched in the review process, and one where AI agents merge pull requests entirely without human involvement. Yet, these futures remain rooted in folk wisdom. Through a mixed-methods study of interviews ($n = 24$) and a survey ($n = 2{,}590$) at a large, multinational software company with widespread access to AI, we identify AI-driven code review challenges and strategies reported as effective to meet them. We found that AI enables, necessitates, and complicates a shift in the human reviewer's role toward high-level concerns (e.g., design and intent). We found that AI-assisted authoring results in increased burden for reviewers due to challenges such as a lack of author stewardship and PR volume and size, potentially leading to downstream debt. Our survey showed AI review usage was not correlated with less difficulty keeping up with PR volume, indicating using AI for review alone is not sufficient for solving AI-driven review challenges. Developers found the most useful strategies to be organizations supporting and resourcing review, pushing review burden upstream, and prioritizing reviewer attention on the concerns that matter most.

## The Human Side of ML Engineering: Analyzing the Collaboration and Communication Skills in ML Job Postings

DevFeed: [The Human Side of ML Engineering: Analyzing the Collaboration and Communication Skills in ML Job Postings](<https://devfeed.tech/articles/the-human-side-of-ml-engineering-analyzing-the-collaboration-and-communication-skills-in-ml-job-postings-137363.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.18915>)

Author: Aidin Azamnouri, Phuong Thao Le, Justus Bogner, Stefan Wagner

Published: 2026-11-17T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>), [arXiv: Machine Learning](<https://devfeed.tech/sources/arxiv-machine-learning.md>)

Topics: [Machine learning](<https://devfeed.tech/topics/machine-learning.md>), [AI Engineering](<https://devfeed.tech/topics/ai-engineering.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>)

Tags: [collaboration](<https://devfeed.tech/tags/collaboration.md>), [communication](<https://devfeed.tech/tags/communication.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-cy](<https://devfeed.tech/tags/cs-cy.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [job](<https://devfeed.tech/tags/job.md>), [ml](<https://devfeed.tech/tags/ml.md>), [skills](<https://devfeed.tech/tags/skills.md>)

### AI overview

In a sample of 1,000 job postings from five continents, collaboration appeared in 88.6% of ML postings and communication in 72.2%; about one fifth and one quarter of those requirements, respectively, were expressed only implicitly. The study used a taxonomy and two human annotators plus an LLM to capture context-dependent references. Collaboration mainly meant integrating across role boundaries, while communication was often generic and fewer than half of postings named its intended audience. ML and software engineering postings demanded interpersonal skills at statistically indistinguishable levels but emphasized different forms: presentation and audience-facing interaction in ML, team practices in SE. Within ML, advertised role distinguished interpersonal profiles more sharply than the other dimensions examined.

### Source excerpt

arXiv:2611.18915v1 Announce Type: cross Abstract: Studies of Machine Learning (ML) practice highlight the importance of combining technical expertise with interpersonal capabilities, particularly collaboration and communication. However, evidence on how ML job postings express these skills is scarce, and prior work largely relies on keyword-based analyses that overlook implicit expression. We analyze demand for these skills in ML job postings across regions, industries, and seniority levels, and compare it with software engineering (SE) roles. We collected 1,000 postings (500 ML, 500 SE) from five continents via a semi-automated pipeline. For annotation, we synthesized a taxonomy of collaboration and communication sub-categories from prior work and used an LLM as a third annotator alongside two humans, enabling detection of context-dependent and implicit skill references. Collaboration appeared in 88.6% of ML postings and communication in 72.2%, far above prior keyword-based estimates for AI roles. Roughly one in five collaboration and one in four communication requirements were expressed only implicitly. Decomposing these requirements into the taxonomy's sub-categories reveals what aggregate figures conceal. Collaboration is demanded predominantly as integration across role boundaries rather than team membership. Communication is mostly required in generic terms, with fewer than half of the postings requiring it naming whom the candidate must communicate with. ML and SE postings demand interpersonal competence at statistically indistinguishable levels but orient it differently, SE toward team practices and ML toward presentation and audience-facing interaction. Within ML, the advertised role separates interpersonal profiles more sharply than any other dimension, including the contrast with SE.

## The hard part of AI coding is deciding what to keep

DevFeed: [The hard part of AI coding is deciding what to keep](<https://devfeed.tech/articles/the-hard-part-of-ai-coding-is-deciding-what-to-keep-135978.md>)

Original publisher: [Read original article](<https://coderabbit.ai/blog/the-merge-ryan-vogel-deciding-what-to-keep>)

Author: Hendrik Krack

Published: 2026-11-16T18:12:39.425207Z

Content type: article

Language: en

Sources: [CodeRabbit](<https://devfeed.tech/sources/coderabbit.md>)

Topics: [Code review](<https://devfeed.tech/topics/code-review.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [ai code review](<https://devfeed.tech/topics/ai-code-review.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [codex](<https://devfeed.tech/topics/codex.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [bug](<https://devfeed.tech/tags/bug.md>), [business-logic](<https://devfeed.tech/tags/business-logic.md>), [caching](<https://devfeed.tech/tags/caching.md>), [challenge](<https://devfeed.tech/tags/challenge.md>), [code-generation](<https://devfeed.tech/tags/code-generation.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [coding](<https://devfeed.tech/tags/coding.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [comment](<https://devfeed.tech/tags/comment.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [english](<https://devfeed.tech/tags/english.md>), [featured](<https://devfeed.tech/tags/featured.md>), [pr](<https://devfeed.tech/tags/pr.md>), [review](<https://devfeed.tech/tags/review.md>)

### AI overview

The harder part of AI-written code is deciding whether a change belongs, not merely reviewing whether it passes. Ryan Vogel recommends stating the app's needs, challenging unnecessary architecture, and using a separate agent to check intermediate work against the original direction. For code review, Harjot Gill says CodeRabbit reconstructs change order and reviews from data and schema through logic and APIs to interface and tests, helping reviewers trace dependencies. The discussion also favors testable evidence over confident claims: an agent should be able to ask questions or run checks, and suspected bugs should be tested before becoming findings. Clear-end tasks suit agents better; open-ended design needs more frequent human decisions. Handoffs should expose decisions, dependencies, evidence, and remaining human judgment, with review effort scaled to a change's consequences.

### Source excerpt

A PR can pass review while nobody decides if the change belongs. Harjot Gill and Ryan Vogel discuss engineering judgment in agent-written code.

## How We Reached 99% Line Coverage in a React Native App

DevFeed: [How We Reached 99% Line Coverage in a React Native App](<https://devfeed.tech/articles/how-we-reached-99-line-coverage-in-a-react-native-app-134517.md>)

Original publisher: [Read original article](<https://hackernoon.com/how-we-reached-99percent-line-coverage-in-a-react-native-app?source=rss>)

Author: John Adib

Published: 2026-11-15T13:37:46Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [React Native](<https://devfeed.tech/topics/react-native.md>), [Expo](<https://devfeed.tech/topics/expo.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [mobile devops](<https://devfeed.tech/topics/mobile-devops.md>), [Instrumentation](<https://devfeed.tech/topics/instrumentation.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Spec Driven Development](<https://devfeed.tech/topics/spec-driven-development.md>)

Tags: [automated-regression-testing](<https://devfeed.tech/tags/automated-regression-testing.md>), [ci](<https://devfeed.tech/tags/ci.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [jest](<https://devfeed.tech/tags/jest.md>), [maestro](<https://devfeed.tech/tags/maestro.md>), [maestro-testing](<https://devfeed.tech/tags/maestro-testing.md>), [mobile-app-testing](<https://devfeed.tech/tags/mobile-app-testing.md>), [react-native](<https://devfeed.tech/tags/react-native.md>), [react-native-testing](<https://devfeed.tech/tags/react-native-testing.md>), [react-native-unit-tests](<https://devfeed.tech/tags/react-native-unit-tests.md>), [test-coverage](<https://devfeed.tech/tags/test-coverage.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

The team reached 99.26% line coverage in October by making tests part of completing changes, expanding Jest unit tests, and bringing Maestro device flows into CI. The figure covered 22,903 of 23,072 eligible lines across four Jest shards; branch coverage was 95.55%, and CI thresholds were pinned to that measured baseline. The team excluded test helpers, Storybook, development-only code and other files from the production-code scope. Inventory counts grew from 113 unit-test files and 14 Maestro YAML files in April to 2,257 and 404 in October, but file counts did not establish behavioral coverage. Although repository leaf flows reached all 99 non-exempt product routes, CI-run leaves reached only 28. The article cautions that coverage cannot show whether assertions catch defects or what happens on iOS and Android; regression tests that fail against the old defect, plus device runs, screenshots and recordings, supplied other review evidence.

### Source excerpt

How one engineering team scaled React Native testing with Jest, Maestro, and CI, reaching 99.26% line coverage while improving verification.

## Software engineering when code is cheap

DevFeed: [Software engineering when code is cheap](<https://devfeed.tech/articles/software-engineering-when-code-is-cheap-134477.md>)

Original publisher: [Read original article](<https://read.theaimerge.com/p/software-engineering-when-code-is-cheap>)

Author: Alex Razvant

Published: 2026-11-15T11:31:10Z

Content type: opinion

Language: en

Sources: [Neural Bits](<https://devfeed.tech/sources/neural-bits.md>)

Topics: [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [coding assistant](<https://devfeed.tech/topics/coding-assistant.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Spec Driven Development](<https://devfeed.tech/topics/spec-driven-development.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Loop Engineering](<https://devfeed.tech/topics/loop-engineering.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [reliable codebases](<https://devfeed.tech/topics/reliable-codebases.md>), [Learning](<https://devfeed.tech/topics/learning.md>)

Tags: [agentic-software-factory](<https://devfeed.tech/tags/agentic-software-factory.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding-tools](<https://devfeed.tech/tags/ai-coding-tools.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [bottleneck](<https://devfeed.tech/tags/bottleneck.md>), [clicks](<https://devfeed.tech/tags/clicks.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### AI overview

The author's central finding is that AI makes it easy to start more code changes than engineers can understand, review, and safely ship. They recommend using agents first to gather project context, investigate the actual problem, and challenge a proposed plan; then choose a justified change, define checks that measure the requirement, and plan a rollback. Code generation is cheap, but review, integration, migration, and production responsibility still take human time. Automated reviews can help with low and medium impact work, while someone who knows a production service should judge readiness. The author also urges teams to protect senior reviewers' capacity and give junior engineers real problems, mentorship, and time to learn. They value simple task definitions and relevant context over elaborate agent setups, and note that long agent sessions can lose important details as context changes or gets summarized.

### Source excerpt

I can start more changes with AI than I can understand. Here's how I deal with that, and why it's a team problem too.

## How the groundcover team works now: Slack for people, Linear for agents

DevFeed: [How the groundcover team works now: Slack for people, Linear for agents](<https://devfeed.tech/articles/how-the-groundcover-team-works-now-slack-for-people-linear-for-agents-134508.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/slack-for-people-linear-for-agents>)

Author: Anais Dotis

Published: 2026-11-15T10:03:00Z

Content type: article

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [Linear](<https://devfeed.tech/topics/linear.md>), [Slack](<https://devfeed.tech/topics/slack.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-code-review](<https://devfeed.tech/tags/ai-code-review.md>), [apis](<https://devfeed.tech/tags/apis.md>), [audits](<https://devfeed.tech/tags/audits.md>), [automated-remediation](<https://devfeed.tech/tags/automated-remediation.md>), [autonomous-infrastructure](<https://devfeed.tech/tags/autonomous-infrastructure.md>), [ci-cd-pipelines](<https://devfeed.tech/tags/ci-cd-pipelines.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [groundcover](<https://devfeed.tech/tags/groundcover.md>), [investigations](<https://devfeed.tech/tags/investigations.md>), [linear](<https://devfeed.tech/tags/linear.md>), [root-cause-analysis](<https://devfeed.tech/tags/root-cause-analysis.md>), [slack](<https://devfeed.tech/tags/slack.md>)

### AI overview

The team uses agents to handle lookup, ticket upkeep, and first-pass code review so engineers can focus on design and judgment. Engineers discuss work in Slack; agents create and update Linear tickets from specs and answer questions by checking documentation. Most changes now go directly to pull requests, where reviewers assess both implementation and approach; line-by-line review remains for high-risk areas such as scale, data correctness, and customer-facing APIs. The team bounds retries, checks invariants before saving, keeps interfaces simple, maintains design documents, and rejects code likely to create technical debt. Agents can produce tests but do not yet choose what new information a feature should measure or how to present it. For remediation, groundcover proposes human-reviewed fixes first; teams may later opt into automation. Its existing infrastructure tool allows cluster-by-cluster adoption, logs changes, and can restore prior values. The planned CI/CD integration would compare pre-deploy signals with post-deploy data to flag regressions.

### Source excerpt

Building groundcover Investigations changed more than our product and how you can use groundcover to perform root cause analysis and roll out fixes. It also changed how the team building groundcover Investigations works day to day. Agents now handle much of the lookup work, the ticket updates and the first pass of code review. The engineers spend more of their time making decisions.

## Podcast: Doing The Right Thing: Accountability In The Age Of AI Coding Summary

DevFeed: [Podcast: Doing The Right Thing: Accountability In The Age Of AI Coding Summary](<https://devfeed.tech/articles/podcast-doing-the-right-thing-accountability-in-the-age-of-ai-coding-summary-131629.md>)

Original publisher: [Read original article](<https://www.infoq.com/podcasts/accountability-age-ai-coding-summary/>)

Author: Hugo Venturini

Published: 2026-11-13T09:00:00Z

Content type: opinion

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [responsible-ai](<https://devfeed.tech/topics/responsible-ai.md>), [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [Boilerplate](<https://devfeed.tech/topics/boilerplate.md>)

Tags: [accountability](<https://devfeed.tech/tags/accountability.md>), [accountability-age-ai-coding-summary](<https://devfeed.tech/tags/accountability-age-ai-coding-summary.md>), [agile](<https://devfeed.tech/tags/agile.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [ai-development](<https://devfeed.tech/tags/ai-development.md>), [ai-risks](<https://devfeed.tech/tags/ai-risks.md>), [architect](<https://devfeed.tech/tags/architect.md>), [boilerplate](<https://devfeed.tech/tags/boilerplate.md>), [career](<https://devfeed.tech/tags/career.md>), [code](<https://devfeed.tech/tags/code.md>), [code-generation](<https://devfeed.tech/tags/code-generation.md>), [code-generator](<https://devfeed.tech/tags/code-generator.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [coding](<https://devfeed.tech/tags/coding.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [culture](<https://devfeed.tech/tags/culture.md>), [culture-methods](<https://devfeed.tech/tags/culture-methods.md>), [distributed-team](<https://devfeed.tech/tags/distributed-team.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineering-culture-podcast](<https://devfeed.tech/tags/engineering-culture-podcast.md>), [hugo](<https://devfeed.tech/tags/hugo.md>), [infoq](<https://devfeed.tech/tags/infoq.md>), [leadership](<https://devfeed.tech/tags/leadership.md>), [podcast](<https://devfeed.tech/tags/podcast.md>), [product-management](<https://devfeed.tech/tags/product-management.md>), [psychological-safety](<https://devfeed.tech/tags/psychological-safety.md>), [quality](<https://devfeed.tech/tags/quality.md>), [roles](<https://devfeed.tech/tags/roles.md>), [safety](<https://devfeed.tech/tags/safety.md>), [software-craftsmanship](<https://devfeed.tech/tags/software-craftsmanship.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [team-collaboration](<https://devfeed.tech/tags/team-collaboration.md>), [teamwork](<https://devfeed.tech/tags/teamwork.md>), [transparency](<https://devfeed.tech/tags/transparency.md>), [trust](<https://devfeed.tech/tags/trust.md>)

### AI overview

Hugo Venturini argues that people remain accountable for AI-generated code and its outcomes. He says pull-request scale predates AI; his team uses trust and judgment to decide what needs review, relying on automated checks for routine work and seeking review for product-critical changes, while acknowledging that review volume remains an open problem. Recalling Microsoft's 2014 merger of engineering and testing roles, he says shared responsibility raised quality, and warns that blaming AI can undermine ownership. As AI blurs roles such as engineer, tester, architect, and product manager, he argues organizations should help people learn to ask better questions. To make that responsibility safe, he describes honest, no-blame Q&As, anonymous questions, and focusing criticism on solutions rather than individuals. He says such transparency can start within a team and spread, though cultural change takes patience.

### Source excerpt

In this podcast, Shane Hastie, Lead Editor for Culture & Methods, spoke to Hugo Venturini about who is accountable when AI writes the code, how AI is reshaping code review and traditional engineering roles, and how leaders build a culture of transparency and psychological safety. By Hugo Venturini

## AI Is Dividing Product Designers: Exploring vs. Building

DevFeed: [AI Is Dividing Product Designers: Exploring vs. Building](<https://devfeed.tech/articles/ai-is-dividing-product-designers-exploring-vs-building-131030.md>)

Original publisher: [Read original article](<https://hackernoon.com/ai-is-dividing-product-designers-exploring-vs-building?source=rss>)

Author: Andrii Bondar

Published: 2026-11-12T22:18:32Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [AI-enhanced product development](<https://devfeed.tech/topics/ai-enhanced-product-development.md>), [UI/UX Design](<https://devfeed.tech/topics/ui-ux-design.md>), [designer developer handoff](<https://devfeed.tech/topics/designer-developer-handoff.md>), [AI in frontend development](<https://devfeed.tech/topics/ai-in-frontend-development.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [product mindset](<https://devfeed.tech/topics/product-mindset.md>), [implementation](<https://devfeed.tech/topics/implementation.md>), [Figma](<https://devfeed.tech/topics/figma.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>)

Tags: [adoption](<https://devfeed.tech/tags/adoption.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-coding-tools](<https://devfeed.tech/tags/ai-coding-tools.md>), [ai-generated-research](<https://devfeed.tech/tags/ai-generated-research.md>), [ai-in-product-design](<https://devfeed.tech/tags/ai-in-product-design.md>), [ai-in-ux-design](<https://devfeed.tech/tags/ai-in-ux-design.md>), [ai-trends](<https://devfeed.tech/tags/ai-trends.md>), [ai-workflow-automation](<https://devfeed.tech/tags/ai-workflow-automation.md>), [building-with-ai](<https://devfeed.tech/tags/building-with-ai.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [code](<https://devfeed.tech/tags/code.md>), [design](<https://devfeed.tech/tags/design.md>), [design-engineer](<https://devfeed.tech/tags/design-engineer.md>), [design-engineering](<https://devfeed.tech/tags/design-engineering.md>), [designers](<https://devfeed.tech/tags/designers.md>), [engineer](<https://devfeed.tech/tags/engineer.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [exploring](<https://devfeed.tech/tags/exploring.md>), [figma](<https://devfeed.tech/tags/figma.md>), [product](<https://devfeed.tech/tags/product.md>), [product-design](<https://devfeed.tech/tags/product-design.md>), [product-development](<https://devfeed.tech/tags/product-development.md>), [ux](<https://devfeed.tech/tags/ux.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

The article describes two approaches to AI in product design: cautious experimentation within existing processes and integrating AI across research, prototyping, design, and implementation. It argues that tool adoption and faster cycles alone do not create value; teams should identify workflow friction and apply AI where it improves existing work. The author reports shifting from mostly Figma to roughly 90% Claude Code, enabling more direct building and iteration with fewer handoffs, while emphasizing that designers need not become full-time engineers. AI can also help create interactive prototypes for specific devices without production code. The article cautions that AI-assisted research can be generic or shallow, so designers must guide and critically evaluate results. Lasting gains depend on shared workflows, quality standards, and attention to technical rigor, security, and reliability.

### Source excerpt

Design Engineer Andrii Bondar about PUSH UX and how AI is transforming product design, UX workflows, and design engineering, from Figma to Claude Code

## We Promised Three Months. It Took Nine.

DevFeed: [We Promised Three Months. It Took Nine.](<https://devfeed.tech/articles/we-promised-three-months-it-took-nine-131444.md>)

Original publisher: [Read original article](<https://newsletter.techworld-with-milan.com/p/we-promised-three-months-it-took>)

Author: Dr Milan Milanović

Published: 2026-11-12T16:02:49Z

Content type: article

Language: en

Sources: [Tech World With Milan Newsletter](<https://devfeed.tech/sources/tech-world-with-milan-newsletter.md>)

Topics: [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [bus factor](<https://devfeed.tech/topics/bus-factor.md>), [software development triangle](<https://devfeed.tech/topics/software-development-triangle.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [modular-monolith](<https://devfeed.tech/topics/modular-monolith.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [Tech Debt](<https://devfeed.tech/topics/tech-debt.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [api](<https://devfeed.tech/tags/api.md>), [bus-factor](<https://devfeed.tech/tags/bus-factor.md>), [conway-s-law](<https://devfeed.tech/tags/conway-s-law.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [laws](<https://devfeed.tech/tags/laws.md>), [software](<https://devfeed.tech/tags/software.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### AI overview

The billing-system rewrite took nine months despite a three-month estimate, illustrating how software laws can point in different directions because they apply under different conditions. The article recommends checking each law's assumptions, measuring outcomes with counter-metrics to discourage gaming, and diagnosing team problems by listing relevant forces, selecting three to five applicable laws, then addressing the strongest force first. Its examples include coordination costs from adding people, token boards rewarding usage rather than quality, and AI-generated services creating contract, comprehension, and integration problems. Practical responses described include agreeing on API contracts before code is written, documenting core modules, starting with a working modular system and extracting services as needed, preserving compatibility with users' observed dependencies, and budgeting time for integration, testing, documentation, handover, and deployment. In the rewrite, the author says the unrealistic deadline was the strongest force; reducing the initial launch scope to one country was the proposed correction.

### Source excerpt

What to do when software engineering laws point in opposite directions

## Forrester Consulting Finds IntelliJ IDEA Delivered 155% ROI and Highlights Open Approach to AI

DevFeed: [Forrester Consulting Finds IntelliJ IDEA Delivered 155% ROI and Highlights Open Approach to AI](<https://devfeed.tech/articles/forrester-consulting-finds-intellij-idea-delivered-155-roi-and-highlights-open-approach-to-ai-131036.md>)

Original publisher: [Read original article](<https://blog.jetbrains.com/idea/2026/11/forrester-consulting-finds-intellij-idea-delivered-155-roi-and-highlights-open-approach-to-ai/>)

Author: Colette Des Georges

Published: 2026-11-12T14:43:36Z

Content type: news

Language: en

Sources: [JetBrains](<https://devfeed.tech/sources/the-jetbrains-blog.md>)

Topics: [IntelliJ IDEA](<https://devfeed.tech/topics/intellij-idea.md>), [jetbrains-ai](<https://devfeed.tech/topics/jetbrains-ai.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Developer Enablement](<https://devfeed.tech/topics/developer-enablement.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-adoption](<https://devfeed.tech/tags/ai-adoption.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-generated-code](<https://devfeed.tech/tags/ai-generated-code.md>), [ai-models](<https://devfeed.tech/tags/ai-models.md>), [ai-tools](<https://devfeed.tech/tags/ai-tools.md>), [code-intelligence](<https://devfeed.tech/tags/code-intelligence.md>), [code-quality](<https://devfeed.tech/tags/code-quality.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [forrester](<https://devfeed.tech/tags/forrester.md>), [intellij-idea](<https://devfeed.tech/tags/intellij-idea.md>), [news](<https://devfeed.tech/tags/news.md>), [open](<https://devfeed.tech/tags/open.md>), [roi](<https://devfeed.tech/tags/roi.md>)

### AI overview

Forrester's commissioned study estimates 155% three-year ROI for a composite financial services organization with 2,000 IntelliJ IDEA developers: $18.4 million net present value, $30.3 million in benefits against $11.9 million in costs, and nine-month payback. The model draws on interviews with nine customer organizations and attributes its largest benefit to code quality, including a projected 15-20% reduction in PR cycle time across three years. It also estimates productivity and retention value from faster code creation, onboarding, and refactoring. Interviewees praised IntelliJ IDEA's understanding of large codebases and its open AI approach, which lets teams use JetBrains and third-party models and agents. Reported AI output gains varied; one engineering leader said slower review and verification left total presubmit-to-production time about unchanged. The excerpt describes the study's composite estimates and interview reports, not measured results for every customer.

### Source excerpt

We're excited to share Forrester's newly released Total Economic Impact™ (TEI) study of IntelliJ IDEA, which JetBrains commissioned to understand how IntelliJ IDEA has delivered value historically and how it continues to do so. Forrester interviewed nine senior engineering and technology leaders whose organizations have between 400 and 4,000 IntelliJ IDEA seats. Based on those [...]

## The AI-Native Organization: Smaller Teams, Faster Execution, Fewer Roadmaps

DevFeed: [The AI-Native Organization: Smaller Teams, Faster Execution, Fewer Roadmaps](<https://devfeed.tech/articles/the-ai-native-organization-smaller-teams-faster-execution-fewer-roadmaps-130195.md>)

Original publisher: [Read original article](<https://hackernoon.com/the-ai-native-organization-smaller-teams-faster-execution-fewer-roadmaps?source=rss>)

Author: Aditya Vithaldas

Published: 2026-11-12T07:23:15Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [AI tools for developers](<https://devfeed.tech/topics/ai-tools-for-developers.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [knowledge-management](<https://devfeed.tech/topics/knowledge-management.md>), [roadmaps](<https://devfeed.tech/topics/roadmaps.md>), [Linear](<https://devfeed.tech/topics/linear.md>), [Shopify](<https://devfeed.tech/topics/shopify.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [accountability](<https://devfeed.tech/tags/accountability.md>), [adapting](<https://devfeed.tech/tags/adapting.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-native](<https://devfeed.tech/tags/ai-native.md>), [ai-native-organizations](<https://devfeed.tech/tags/ai-native-organizations.md>), [ai-organizational-structure](<https://devfeed.tech/tags/ai-organizational-structure.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineering-management](<https://devfeed.tech/tags/engineering-management.md>), [execution](<https://devfeed.tech/tags/execution.md>), [future-of-work](<https://devfeed.tech/tags/future-of-work.md>), [linear](<https://devfeed.tech/tags/linear.md>), [meta](<https://devfeed.tech/tags/meta.md>), [organization](<https://devfeed.tech/tags/organization.md>), [product](<https://devfeed.tech/tags/product.md>), [product-management](<https://devfeed.tech/tags/product-management.md>), [ramp](<https://devfeed.tech/tags/ramp.md>), [roadmaps](<https://devfeed.tech/tags/roadmaps.md>), [shopify](<https://devfeed.tech/tags/shopify.md>), [small-team-structures](<https://devfeed.tech/tags/small-team-structures.md>), [teams](<https://devfeed.tech/tags/teams.md>), [tech-company-restructuring](<https://devfeed.tech/tags/tech-company-restructuring.md>)

### AI overview

The article describes a shift toward small, outcome-owning teams and shorter planning cycles as AI tools make building cheaper and more accessible. It cites Meta's three-to-five-person pods, LinkedIn's engineer-designer-PM trios, and examples of one-person teams. Roles are becoming more fluid, while small central platform teams maintain shared AI harnesses such as Ramp's Inspect and Shopify's River, which the article says help employees outside engineering build and execute work. Specialists can support multiple pods, and frontier teams track new developments. Long feature roadmaps are giving way to leader-set three-to-six-month direction, weekly reprioritization, and execution cycles measured in weeks; teams test plans by shipping previews or early-access releases. Speed still has limits: the article says high-risk security, stability, and compliance matters require review, and Shopify still has a human review every production PR. Its recommendations include cross-functional teams, shared practices, decisive leadership, and visible token spending.

### Source excerpt

How Anthropic, Ramp, Shopify, Meta and Linear are organizing product and engineering teams for 2027, and what it means for yours.

## How to Write Professional Git Commit Messages: 4 Essential Rules

DevFeed: [How to Write Professional Git Commit Messages: 4 Essential Rules](<https://devfeed.tech/articles/how-to-write-professional-git-commit-messages-4-essential-rules-130190.md>)

Original publisher: [Read original article](<https://hackernoon.com/how-to-write-professional-git-commit-messages-4-essential-rules?source=rss>)

Author: William

Published: 2026-11-12T07:00:35Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Git](<https://devfeed.tech/topics/git.md>), [version-control](<https://devfeed.tech/topics/version-control.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Learning](<https://devfeed.tech/topics/learning.md>)

Tags: [atomic](<https://devfeed.tech/tags/atomic.md>), [body](<https://devfeed.tech/tags/body.md>), [bug](<https://devfeed.tech/tags/bug.md>), [bug-fix](<https://devfeed.tech/tags/bug-fix.md>), [button](<https://devfeed.tech/tags/button.md>), [commit](<https://devfeed.tech/tags/commit.md>), [commits](<https://devfeed.tech/tags/commits.md>), [database](<https://devfeed.tech/tags/database.md>), [database-schema](<https://devfeed.tech/tags/database-schema.md>), [developer](<https://devfeed.tech/tags/developer.md>), [git](<https://devfeed.tech/tags/git.md>), [git-5072-rule](<https://devfeed.tech/tags/git-5072-rule.md>), [git-commit](<https://devfeed.tech/tags/git-commit.md>), [github](<https://devfeed.tech/tags/github.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [messages](<https://devfeed.tech/tags/messages.md>), [professional-github](<https://devfeed.tech/tags/professional-github.md>), [rules](<https://devfeed.tech/tags/rules.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [version](<https://devfeed.tech/tags/version.md>), [version-control](<https://devfeed.tech/tags/version-control.md>), [write](<https://devfeed.tech/tags/write.md>)

### AI overview

The article recommends four practices for readable Git history: write subjects in the imperative mood, as in "Fix bug," so they describe what the commit will do; keep the subject to 50 characters and, when needed, add a body after a blank line wrapped at 72 characters; use Conventional Commit prefixes such as `feat:`, `fix:`, `chore:`, and `refactor:` to categorize changes and support changelog generation and regression tracing; and keep each commit atomic so reverting one change does not undo an unrelated fix. These are presented as conventions the author is learning to apply to a more professional GitHub presence.

### Source excerpt

To write professional GitHub commits, learn to follow the unspoken rules of version control.

## AI Is Changing Software Engineering Forever | Gregor Ojstersek

DevFeed: [AI Is Changing Software Engineering Forever | Gregor Ojstersek](<https://devfeed.tech/articles/ai-is-changing-software-engineering-forever-gregor-ojstersek-129778.md>)

Original publisher: [Read original article](<https://dataengineeringcentral.substack.com/p/ai-is-changing-software-engineering>)

Author: Daniel Beach

Published: 2026-11-11T13:25:32Z

Content type: article

Language: en

Sources: [Data Engineering Central](<https://devfeed.tech/sources/data-engineering-central.md>)

Topics: [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>)

Tags: [advice](<https://devfeed.tech/tags/advice.md>), [age-of-ai](<https://devfeed.tech/tags/age-of-ai.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-generated-code](<https://devfeed.tech/tags/ai-generated-code.md>), [book](<https://devfeed.tech/tags/book.md>), [career](<https://devfeed.tech/tags/career.md>), [code](<https://devfeed.tech/tags/code.md>), [computer-science](<https://devfeed.tech/tags/computer-science.md>), [cto](<https://devfeed.tech/tags/cto.md>), [data-engineering](<https://devfeed.tech/tags/data-engineering.md>), [developer](<https://devfeed.tech/tags/developer.md>), [engineer](<https://devfeed.tech/tags/engineer.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineering-jobs](<https://devfeed.tech/tags/engineering-jobs.md>), [engineering-leadership](<https://devfeed.tech/tags/engineering-leadership.md>), [engineering-management](<https://devfeed.tech/tags/engineering-management.md>), [engineers](<https://devfeed.tech/tags/engineers.md>), [fundamentals](<https://devfeed.tech/tags/fundamentals.md>), [software](<https://devfeed.tech/tags/software.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### AI overview

The episode's central takeaway is that writing code may matter less as AI changes engineering work, while engineering fundamentals, problem-solving, and leadership remain important. Gregor Ojstersek discusses how AI may affect junior through principal roles, engineering management, and the path to CTO; the risks of AI-generated code, weak engineering practices, and losing fundamental skills; and why choosing the right work matters. The excerpt also describes his journey from self-taught programmer to CTO, his book The Multiplier Mindset, and the growth of his Engineering Leadership Newsletter to over 200,000 subscribers. It lists topics and chapter timestamps but does not provide the detailed discussion or specific advice.

### Source excerpt

From Engineer to CTO

## How to Win Back Your Agency from Cognitive Surrender

DevFeed: [How to Win Back Your Agency from Cognitive Surrender](<https://devfeed.tech/articles/how-to-win-back-your-agency-from-cognitive-surrender-128948.md>)

Original publisher: [Read original article](<https://spin.atomicobject.com/preserve-shared-understanding/>)

Author: Matt Sweda

Published: 2026-11-11T13:00:22Z

Content type: opinion

Language: en

Sources: [Atomic Object](<https://devfeed.tech/sources/atomic-object.md>)

Topics: [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Machine Intelligence](<https://devfeed.tech/topics/machine-intelligence.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [AI Context Management](<https://devfeed.tech/topics/ai-context-management.md>)

Tags: [agentic-software](<https://devfeed.tech/tags/agentic-software.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-assistance](<https://devfeed.tech/tags/ai-assistance.md>), [ai-for-developers](<https://devfeed.tech/tags/ai-for-developers.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [cognitive-surrender](<https://devfeed.tech/tags/cognitive-surrender.md>), [coherence](<https://devfeed.tech/tags/coherence.md>), [conversations](<https://devfeed.tech/tags/conversations.md>), [craft](<https://devfeed.tech/tags/craft.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [development](<https://devfeed.tech/tags/development.md>), [discovery](<https://devfeed.tech/tags/discovery.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [knowledge-transfer](<https://devfeed.tech/tags/knowledge-transfer.md>), [llm](<https://devfeed.tech/tags/llm.md>)

### AI overview

The author argues that AI-assisted coding can weaken shared understanding when developers use prompts in place of conversations with teammates or clients. LLMs can help produce code quickly, but that speed may shift the effort of understanding to reviewers and maintainers, while different assumptions surface later as incompatible implementations. Specs help document context but cannot ensure people interpret it alike or resolve ambiguity. The author favors writing implementations oneself and using LLMs to find holes, generate counterexamples, and answer questions, while keeping human judgment central. They recommend questioning unclear output, clarifying assumptions with others, and holding AI-generated changes to the same standards of explanation and review as other code.

### Source excerpt

If you haven't yet read The Decoherence Trap by Kristen Maevyn, I highly suggest you do, because in a way this is my extension of those great ideas. Maevyn describes how individually reasonable changes can accumulate into a system that becomes increasingly difficult to change. What I want to explore is how we're losing the [...] The post How to Win Back Your Agency from Cognitive Surrender appeared first on Atomic Spin.

## How LinkedIn, Netflix & DoorDash Run Agents, Evals & Inference in Production: QCon AI New York 2026

DevFeed: [How LinkedIn, Netflix & DoorDash Run Agents, Evals & Inference in Production: QCon AI New York 2026](<https://devfeed.tech/articles/how-linkedin-netflix-doordash-run-agents-evals-inference-in-production-qcon-ai-new-york-2026-128003.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/11/qcon-ai-newyork-2026-program/>)

Author: Artenisa Chatziou

Published: 2026-11-11T11:00:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [QCon Software Development Conference](<https://devfeed.tech/topics/qcon-software-development-conference.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [AI Architecture](<https://devfeed.tech/topics/ai-architecture.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Netflix](<https://devfeed.tech/topics/netflix.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [agent-permissions](<https://devfeed.tech/tags/agent-permissions.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-code-review](<https://devfeed.tech/tags/ai-code-review.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [ai-ml-data-engineering](<https://devfeed.tech/tags/ai-ml-data-engineering.md>), [ai-systems](<https://devfeed.tech/tags/ai-systems.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [deepmind](<https://devfeed.tech/tags/deepmind.md>), [doordash](<https://devfeed.tech/tags/doordash.md>), [evals](<https://devfeed.tech/tags/evals.md>), [guardrails](<https://devfeed.tech/tags/guardrails.md>), [harvey](<https://devfeed.tech/tags/harvey.md>), [inference](<https://devfeed.tech/tags/inference.md>), [linkedin](<https://devfeed.tech/tags/linkedin.md>), [ml-data-engineering](<https://devfeed.tech/tags/ml-data-engineering.md>), [netflix](<https://devfeed.tech/tags/netflix.md>), [new-york](<https://devfeed.tech/tags/new-york.md>), [news](<https://devfeed.tech/tags/news.md>), [openai](<https://devfeed.tech/tags/openai.md>), [pinterest](<https://devfeed.tech/tags/pinterest.md>), [production](<https://devfeed.tech/tags/production.md>), [qcon-ai-new-york-2026](<https://devfeed.tech/tags/qcon-ai-new-york-2026.md>), [qcon-ai-newyork-2026-program](<https://devfeed.tech/tags/qcon-ai-newyork-2026-program.md>), [qcon-software-development-conference](<https://devfeed.tech/tags/qcon-software-development-conference.md>), [retrieval-augmented-generation](<https://devfeed.tech/tags/retrieval-augmented-generation.md>), [security](<https://devfeed.tech/tags/security.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### AI overview

QCon AI New York's December 15-16, 2026 program describes production AI systems and the operational choices behind them. LinkedIn's Kubernetes operations agent spans 500,000+ nodes and 5M+ pods, with server-side rate limits, delete protection, and peer approval for production changes. Figma reports that warm pools cut agent provisioning latency by 90% and raised availability from 99% to 99.95%. DoorDash checks changes before launch using an LLM judge calibrated against human reviewers and shared rubrics for simulated and real sessions. Netflix serves about 1 million inference requests per second across 300+ models on a consolidated platform; Pinterest presents a vision-language serving stack built for heavy prefill and KV-cache pressure. LinkedIn's code review system handles tens of thousands of pull requests weekly, with over 60% of sampled suggestions accepted after validation filtering. Other talks cover agent identity, organization-wide evaluations, and engineering adoption.

### Source excerpt

QCon AI New York has published its full program for December 15-16, 2026. Engineers from LinkedIn, Netflix, DoorDash, Figma, Pinterest, Honeycomb, Harvey, Google DeepMind and OpenAI describe AI systems they run in production. Talks cover agent permissions and guardrails, eval loops, inference cost, AI code review, and team adoption. By Artenisa Chatziou

## Compile-Gated Lean Proof Refactoring with Enterprise Agent Practices: A Model per Step under a US\\$3 Cap, Followed by Programmatic Rewrite Rules

DevFeed: [Compile-Gated Lean Proof Refactoring with Enterprise Agent Practices: A Model per Step under a US\\$3 Cap, Followed by Programmatic Rewrite Rules](<https://devfeed.tech/articles/compile-gated-lean-proof-refactoring-with-enterprise-agent-practices-a-model-per-step-under-a-us-3-cap-followed-by-programmatic-rewrite-rules-128235.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.13011>)

Author: Bobber Cheng

Published: 2026-11-11T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>), [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Lean](<https://devfeed.tech/topics/lean.md>), [qualitygates](<https://devfeed.tech/topics/qualitygates.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [agent observability](<https://devfeed.tech/topics/agent-observability.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-lo](<https://devfeed.tech/tags/cs-lo.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [model](<https://devfeed.tech/tags/model.md>), [practices](<https://devfeed.tech/tags/practices.md>), [rewrite](<https://devfeed.tech/tags/rewrite.md>), [rules](<https://devfeed.tech/tags/rules.md>)

### AI overview

The closed-track Lean proof refactoring entry scored 86.31 across 60 problems, ranking 8th at the deadline, for $166.33 total under a $3-per-problem cap; its mean cost was $2.772 per problem. The team selected models by measured cost effectiveness across nine models: GPT-6.1 Sol for early sessions and style rewrites, GPT-6.1 Terra for later sessions and the tail, and Gemini 4 Argon for review and repair. It converted lessons from development runs into compiler-checked rewrite rules, reporting +0.93 points from rules fixed before release and in-sample gains of +0.26 and +0.30 from later passes. Calls were recorded and reviewed before changes; all nine board scores were within -0.063 to +0.015 points of the team's meter predictions. The abstract says the full bill and spread across three runs are reported, but does not provide those run details.

### Source excerpt

arXiv:2611.13011v1 Announce Type: cross Abstract: Our closed-track entry (Arena username Vexorium-Agent) scored 86.31 points on the final board (L = 77.07, H = 81.86, Z = 100) over the 60 final problems, against 33.33 for the reference proofs, 8th at the deadline (top: 92.57), for US\$166.33 at list prices with every call counted (per problem: mean US\$2.772, at most US\$2.874; US\$3 cap). Three practices carry the entry. First, each paid stage runs the model that measured best per dollar for it among the 9 we tested in our own harness: GPT-6.1 Sol the early sessions, GPT-6.1 Terra the later ones and the tail at 70% of Sol's cost per turn, and Gemini 4 Argon the review and repair; Sol also runs the style rewrite. Second, what our development and research runs learned ships as compiler-checked programmatic rewrite rules rather than prompt text (+0.93 points from rules fixed before the release; +0.26 and +0.30, in sample, from passes built or switched on after the release). Third, every call is recorded and reviewed before each change (all 9 board scores came within -0.063 to +0.015 points of our meter's prediction). The harness, gate and many of these rules also serve our open-track entry. We report the full bill and the spread of three runs.

[Next page](<https://devfeed.tech/topics/engineering-culture.md?cursor=WyIyMDI2LTExLTExVDA1OjAwOjAwKzAwOjAwIiwgIjhkYmQ2ZDc3LTBiNDQtNDI1YS04Yjg1LTBhNWY0ZmFiOWZlZCJd>)