# BugBash'26 Afternoon of Day 1

DevFeed: [BugBash'26 Afternoon of Day 1](<https://devfeed.tech/articles/bugbash-26-afternoon-of-day-1-41835.md>)

Original publisher: [Read original article](<https://muratbuffalo.blogspot.com/2026/04/bugbash26-afternoon-of-day-1.html>)

Author: Murat (noreply@blogger.com)

Published: 2026-04-27T12:24:00Z

Content type: opinion

Language: en

Sources: [Metadata](<https://devfeed.tech/sources/metadata.md>)

Topics: [Development](<https://devfeed.tech/topics/development.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [Testing](<https://devfeed.tech/topics/testing.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [code-generation](<https://devfeed.tech/tags/code-generation.md>), [development](<https://devfeed.tech/tags/development.md>), [formal-methods](<https://devfeed.tech/tags/formal-methods.md>), [llm](<https://devfeed.tech/tags/llm.md>), [testing](<https://devfeed.tech/tags/testing.md>), [trip-report](<https://devfeed.tech/tags/trip-report.md>)

## AI overview

Notes from BugBash'26 examine how LLMs and agents change software development. The discussion argues that agents move work but do not eliminate difficult tasks such as design, discovery, integration, correctness, interface design, and testing.

## Source excerpt

These are my notes from the afternoon sessions of BugBash'26. We had a 75 minute lunch break. Nice lunch, but there were no vegetarian entries, which made Peter Alvaro hangry. I don't blame him, I would be too. Informal methods Ben Eggers, Member of Technical Staff @ OpenAI This was a fun and also thought provoking talk. The premise is "Nothing has changed about software development". Really? After the LLMs eating software like a wildfire, and particularly rocking at code generation in the last 3 months?? And this is coming from an OpenAI infrastructure engineer, who was once a 8th highest 7d token user. How come? The talk has two parts: writing code was where the hard parts surfaced agents move the work, but do not obviate it Ok, now it makes more sense. Both of these are sensible statements. Ben followed with a couple disclaimers, that he is talking about deep narrow systems, and not about broad high surface area systems, because he has experience in the former, and didn't want to make claims for the latter. Ben is a funny guy, and refreshingly honest. He made fun of LLMs mistake in code generation through 3 popup quizzes through out his talk. Part 1: Writing code has always been where the hard part surfaced Ben harkened back to Will Wilson's claim that before LLMs, 50% of the time was spent in writing code, and 50% in testing. Ben asked, hey, what happened to design, discovery, integration, and correctness? He made the case that these were the hard parts, and writing code forces people to address them: decide intent discover the shape of the problem turn boundaries into contracts notice weirdness before anyone else does fill in the code This is a long arduous process. The slowness of writing code was load-bearing! When you notice your code start crossing boundaries, this exposed bad interfaces in your components. Wiring paths end-to-end helped expose missing cases. Writing tests (yes this was the first thing we lost to the LLM wildfire) forced expected behavior t