AI* and coding

Using AI to write better code more slowly

A lot of people seem convinced that the point of AI coding is to write low-quality code as fast as possible. Spew out barely-passable slop, open massive PRs, and merge them unvetted. Ship it! But t…

「コードは一行も書いていない」　アイドルの宮本佳林さん、AIで配信システムを丸ごと構築　“技術ブログ”が話題

元Juice=Juiceの宮本佳林さんが8月1日、10時間のYouTube生配信を支えるシステムをAIとともに自作したと自身のブログで公開した。プログラミング経験ゼロで作り上げた開発の裏側をつづった“技術ブログ”に、X上では驚きの声が広がっている。

【やじうま配信者Watch】 宮本佳林さん、コード記述ゼロで10時間生配信システムを構築したことが話題に

コードが書けないアイドルが、 AIと一緒に10時間配信のシステムを 全部作った話。https://t.co/IHDrEc55um 技術面でまとめたものも書きました。https://t.co/cW5CuIzF21 是非見てみてね！

宮本佳林：元アイドルがバイブコーディングできるようになるまで。

こんにちは！2020年までハロー！プロジェクト Juice=Juiceで活動をし、卒業以降はソロで音楽活動をしております。 宮本佳林です！はじめましての方もこ…

The AI Engineering Report 2026: The AI Acceleration Whiplash - Ten Takeaways

What two years of telemetry data from 22,000 developers reveals about AI's real impact on developer productivity, code quality, and business risk in 2026.

Google Employees Internally Share Memes About How Its AI Sucks

Google’s CEO says 75% of the company’s code is AI-generated. The people who write that code say the AI they’re using is overhyped.

Stuck in the middle: Being an engineer & artist in the AI era | Annie Sexton | Offprint

I'm an AI skeptic, through and through. But I also voluntarily use AI nearly every day. So naturally, you might be asking: what the heck?

Mitchell Hashimoto (@mitchellh)

I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out. I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really). It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely. The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture. We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying. I worry.

AI Code Is Producing a Quality Crisis Nobody Wants to Talk About

The productivity numbers look great. AI coding tools are everywhere.

AI-generated code is 'pain waiting to happen'

The boom is piling up technical debt, warns Lightrun's Moshe Sambol

Software Developers Say AI Is Rotting Their Brains

“It's making me dumber for sure.”

We are Changing our Developer Productivity Experiment Design

Our second developer productivity study faces selection effects from wider AI adoption, prompting us to redesign our approach.

Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity

Despite widespread adoption, the impact of AI tools on software development in the wild remains understudied. We conduct a randomized controlled trial (RCT) to understand how AI tools at the February-June 2025 frontier affect the productivity of experienced open-source developers. 16 developers with moderate AI experience complete 246 tasks in mature projects on which they have an average of 5 years of prior experience. Each task is randomly assigned to allow or disallow usage of early 2025 AI tools. When AI tools are allowed, developers primarily use Cursor Pro, a popular code editor, and Claude 3.5/3.7 Sonnet. Before starting tasks, developers forecast that allowing AI will reduce completion time by 24%. After completing the study, developers estimate that allowing AI reduced completion time by 20%. Surprisingly, we find that allowing AI actually increases completion time by 19%--AI tooling slowed developers down. This slowdown also contradicts predictions from experts in economics (39% shorter) and ML (38% shorter). To understand this result, we collect and evaluate evidence for 20 properties of our setting that a priori could contribute to the observed slowdown effect--for example, the size and quality standards of projects, or prior developer experience with AI tooling. Although the influence of experimental artifacts cannot be entirely ruled out, the robustness of the slowdown effect across our analyses suggests it is unlikely to primarily be a function of our experimental design.

Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity

We conduct a randomized controlled trial to understand how early-2025 AI tools affect the productivity of experienced open-source developers working on their own repositories. Surprisingly, we find that when developers use AI tools, they take 19% longer than without—AI makes them slower.

Study finds AI tools made open source software developers 19 percent slower

Coders spent more time prompting and reviewing AI generations than they saved on coding.

What Actually Happens When Programmers Use AI Is Hilarious, According to a New Study

As AI takes the programming world by storm, experienced devs are still the gold standard — and they're better off without AI assistance, too.

The Economics of Using AI to Churn Out Code Are Looking Worse Than Ever

Anthropic updated an estimate for how much developers will spend on its AI coding tool, signaling that the tech is only going to get costlier.