41 stories tagged developer-productivity, newest first.
116 points by theanonymousone | 201 comments
Blog essay comparing AI coding agents to past promises like FORTRAN ending programming, reviewing 2026 survey and METR data, and imagining a developer's day in 2031.
38 points by alexmolas | 22 comments
Will Larson describes Imprint's `small-change` process, which uses CI checks and AI review skills to fast-track approval of small, low-risk pull requests.
63 points by thegreatpeter | 64 comments
A blog post arguing software engineers should not spend time building personal AI-driven software factories and should instead build actual products.
303 points by gumby | 263 comments
Ars Technica article on a study finding AI coding agents increase code output but efficiency gains are absorbed by human code review bottlenecks.
11 points by bradleygibbs | 7 comments
Blog post by Bradley Gibbs on designing AI-assisted development loops to qualify generated code for human review, reduce wasted work, and measure verification value.
148 points by saibotk | 153 comments
Personal blog post about a developer spending a month without AI tools at work, reflecting on how AI use made them lazier and a worse developer.
6 points by fscaramuzza | 6 comments
Communications of the ACM research article on the gap between individual efficiency gains and overall throughput when using GitHub Copilot; page showed a Cloudflare check.
55 points by thecodemonkey | 21 comments
Geocodio engineering blog post on moving from bash scripts to full internal apps, keeping them maintainable, and deciding when to build versus buy.
300 points by julian_digital | 367 comments
A Linear engineering blog post explaining how AI-assisted coding increased CI load and how the team reworked its CI pipeline to keep up.
606 points by signa11 | 266 comments
A blog post arguing that small nuggets of programming knowledge boost productivity, sharing examples like fzf-powered ctrl+r and python3 -m http.server.
386 points by gpi | 93 comments
Engineering Leadership newsletter post by Gregor Ojstersek arguing that good team culture boosts productivity more than AI, which helps only when culture is right.
328 points by msephton | 142 comments
A blog post by Alex Kotliarskyi on frantic.im titled "The Productivity Mirage," likely about perceived versus real productivity gains.
417 points by RyeCombinator | 288 comments
A blog post by David Curlewis arguing that AI-era productivity metrics are repackaging lines of code as a measure of developer output.
785 points by koshyjohn | 556 comments
Blog post by Koshy John arguing engineers should use AI to augment their thinking rather than outsource it, distinguishing real leverage from self-inflicted irrelevance.
1001 points by jdkoeck | 445 comments
Blog post by developer Mario Zechner, dated 2026-03-25, reflecting on slowing down in software development, illustrated with a tortoise-and-hare drawing.
330 points by tanelpoder | 305 comments
Answer.AI blog post examining PyPI package creation and update data to look for evidence that AI coding tools have increased software output.
343 points by saikatsg | 242 comments
Blog post by Ivan Turkovic arguing that AI tools make producing code easier while making the broader job of being a software engineer harder.
408 points by pagade | 172 comments
Blog essay on rockoder about cognitive debt, where development velocity (e.g., via AI-generated code) outpaces engineers' understanding of their codebase.
441 points by weaksauce | 295 comments
A blog article on blundergoat.com arguing AI makes easy work easier and hard work harder; the captured page shows a 404 Page not found error.
618 points by chrisloy | 377 comments
Blog post by Chris Loy arguing that AI coding tools speed up typing code but risk neglecting the problem-solving that is the real work of software development.
370 points by elmsec | 395 comments
A personal blog post arguing that AI coding tools benefit senior developers more than juniors, outlining where AI helps and falls short in coding.
526 points by dbalatero | 319 comments
A Substack essay by Mike Judge arguing that claims of massive AI coding productivity gains aren't supported by evidence such as a surge in new software releases.
489 points by bkolobara | 446 comments
Blog post by Bernard Kolobara on Lubeno describing how Rust's initial productivity dip gives way to an unexpected productivity boost over time.
864 points by coltonv | 601 comments
Blog post by Colton Voege arguing AI is not making engineers 10x more productive and offering advice for engineers feeling imposter syndrome over such claims.
543 points by mike1o1 | 543 comments
Puzzmo blog post by Orta Therox reflecting on six weeks of using Claude Code and how it changed his approach to writing and maintaining code.
638 points by dheerajvs | 421 comments
METR research post on a randomized controlled trial finding that early-2025 AI tools made experienced open-source developers 19% slower on their own repositories.
626 points by phire | 309 comments
Blog post arguing that writing code was never the bottleneck in software engineering; reviews, knowledge transfer, testing, and coordination are.
380 points by ingve | 251 comments
Blog post by Juha-Matti Santala arguing that a pen and notebook are a developer's most important tools for thinking through problems.
323 points by matthewsinclair | 214 comments
Blog post by Matthew Sinclair arguing that LLM-powered programming tools act like a mech suit amplifying developers rather than replacing them.
448 points by rbanffy | 308 comments
Dan North's blog post about colleague Tim Mackinnon, who scored zero on individual productivity metrics because he spent his time helping teammates, and why North defended him.
762 points by stpn | 292 comments
David Crawshaw's blog post summarizing a year of personal experience using LLMs while programming, and introducing sketch.dev, a Go-focused tool.
482 points by mooreds | 369 comments
Addy Osmani's Substack essay on why AI coding tools get developers about 70% of the way, and how to rethink expectations of AI-assisted development.
493 points by marcusbuffett | 289 comments
A personal blog post in which a programmer lists advice he would give his younger self, such as fixing recurring team problems at their root.
332 points by ben_s | 162 comments
Engineer's Codex newsletter post about Meta's TestGen-LLM, an LLM-based tool that generates and filters unit tests to improve developer productivity.
593 points by paprikati | 378 comments
An incident.io engineering blog post analyzing collected developer build telemetry to compare M1, M2, and M3 MacBooks and decide whether upgrading is worthwhile.
613 points by vberg | 571 comments
A Ledger blog post offering strategies for software developers with ADHD to manage focus and productivity.
353 points by Zelphyr | 427 comments
Ask HN discussion asking why Microsoft abandoned Visual Basic and why no comparable rapid application development tool has replaced it.
1417 points by zdw | 571 comments
Dan North blog post about Tim Mackinnon, a colleague who scored zero on individual productivity metrics because he spent his time helping teammates.
423 points by damethos | 152 comments
MIT doctoral thesis by Daniel Sturtevant measuring how architectural complexity in software systems affects defect density, developer productivity, and staff turnover.
468 points by jeron | 220 comments
A ContextKeeper blog post from July 2022 on the cost of interruptions and context switching for programmers.
640 points by duck | 483 comments
Simon Willison blog post on how ChatGPT and Copilot make him more ambitious with side projects, illustrated by building a tool to archive ChatGPT conversations.