55 stories tagged software-development, newest first.
3 points by KentBeck | 1 comments
Kent Beck newsletter post arguing AI coding "genies" should remove toil while preserving the productive struggle that builds skill, using a RoboGym analogy.
44 points by sanketsaurav | 39 comments
Blog essay arguing that AI coding tools like Claude Code have ended the rationing of engineering effort, and software makers haven't yet adapted.
532 points by tosh | 188 comments
Blog post by Karri Saarinen arguing that good software products carry the experience, values, and perspective of the people who make them.
50 points by sklarsa | 53 comments
A blog post arguing that the non-deterministic output of LLMs is not a real obstacle to using AI as a primary software development tool.
26 points by ingve | 36 comments
Blog post by Nate Meyvis offering conjectural answers to why AI coding hasn't visibly produced more new, good software.
289 points by ilreb | 141 comments
Michael Lynch's Refactoring English article cataloguing common mistakes beginner software bloggers make, such as meandering intros and overreliance on links.
51 points by samtheDamned | 65 comments
Blog post on andreklein.net about vibecoding a Photoshop-like app and dealing with time and pressure; captured page shows a Cloudflare verification screen.
11 points by aray07 | 8 comments
A personal blog post by a developer of 18 years explaining how Claude Code with Opus 4.5 led him to stop writing code by hand entirely.
103 points by yedhukrishnan | 58 comments
A personal blog post arguing that writing detailed commit descriptions explaining what and why serves as a thinking tool, reconsidered in the era of AI coding.
33 points by ibobev | 37 comments
Essay by Simon Park on what makes software development an engineering discipline: a repeatable process that doesn't depend on individual brilliance.
18 points by JumpCrisscross | 8 comments
A personal blog post by Jake Goldsborough titled "Goodbye to the Hard Parts That Never Mattered," reflecting on software development work.
537 points by jmvldz | 468 comments
Blog post by Ayman Nadeem arguing that plan mode in AI coding tools is obsolete, reflecting on building the Nuanced desktop coding app around planning.
7 points by altras | 0 comments
Camplight blog post explaining what an AI software factory is and sharing lessons learned from three client deployments.
41 points by fagnerbrack | 29 comments
A Manager.dev newsletter post by Anton Zaides recounting a hackathon built with Lovable to explain to business people why building software is still hard.
6 points by meetpateltech | 0 comments
A blog post on jola.dev arguing that LLM assistants, by doing tasks for users instead of explaining them, undermine learning.
490 points by larsfaye | 479 comments
Blog essay by Lars Faye arguing that reliance on AI coding tools removes the friction needed to develop long-term programming expertise.
351 points by yusyd | 379 comments
Blog post using a steak-cooking analogy to argue AI speeds up software development but doesn't replace the judgment needed to build consistently good software.
414 points by erikschoster | 169 comments
Beej's blog essay "On Making" about finding fulfillment in building things yourself and feeling less of it when AI builds code at your request.
347 points by razin | 280 comments
A blog post by George Hotz arguing that adopting AI coding agents in software development is a costly mistake because their output is subtly broken.
2013 points by reasonableklout | 1180 comments
Mitchell Hashimoto's X post arguing some companies are in 'AI psychosis', relying on agents to fix bugs fast (MTTR) at the expense of reliability (MTBF).
407 points by Eighth | 247 comments
A personal blog post in which a software developer argues that relying on AI for writing code, articles, and documents is eroding his own writing and programming skills.
890 points by dropbox_miner | 558 comments
A developer's devlog post explaining why they are returning to writing code by hand after experimenting with fully AI-driven vibe-coding of a project.
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.
440 points by indigodaddy | 423 comments
A personal blog post by Stavros describing how he uses LLMs to write software and why he values making things over programming itself.
357 points by itunpredictable | 354 comments
A Technically newsletter essay comparing vibe coding with the maker movement, asking whether vibe-coded apps are throwaway projects or lasting value.
705 points by jamesrandall | 556 comments
Personal essay by a 50-year-old developer who began coding BASIC in 1983, reflecting on how the craft of programming has changed, including with AI.
747 points by mobitar | 544 comments
A Substack essay by Mo explaining why, after two years of relying on AI-assisted vibecoding, the author returned to writing code by hand.
544 points by glimshe | 428 comments
Blog post by Stephan Schwab on why businesses have tried to replace software developers every decade since 1969, from COBOL to AI.
1090 points by todsacerdoti | 1334 comments
Blog post by antirez arguing that, despite his reservations, LLMs are going to change programming forever and people shouldn't dismiss AI out of hand.
376 points by cdrnsf | 471 comments
A Codemanship blog post arguing that the future of software development still depends on human software developers.
335 points by Kerrick | 299 comments
A personal blog post by Kerrick in which a software developer shares professional confessions and vows to stop self-censoring.
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.
378 points by floverfelt | 347 comments
Martin Fowler's blog post sharing scattered thoughts on the state of LLMs and AI and their effect on software development.
458 points by Improvement | 130 comments
A personal blog post by a software developer reflecting snarkily on one year working at a large enterprise after a decade in startups and SMEs.
475 points by Stwerner | 368 comments
Scott Werner's Substack essay arguing nobody yet knows how to build software with AI, drawing on building Protocollie in four days without touching the code.
2326 points by dang | 845 comments
A Hacker News post by moderator dang urging US taxpayers to sign a letter to lawmakers to restore immediate deduction of software development expenses under Section 174.
466 points by bumbledraven | 261 comments
Blog post by David Crawshaw on using LLM-based agents for programming, defining an agent as a loop around an LLM that executes commands.
400 points by vinhnx | 156 comments
Addy Osmani's Substack article offering a playbook of prompt engineering techniques for getting better results from AI coding assistants.
2112 points by tabletcorry | 2518 comments
A Fly.io blog essay arguing that skeptical software developers are wrong to dismiss LLM-based coding assistants and agents.
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.
549 points by zdw | 209 comments
Blog post by Matthias Endler arguing that the advice not to reinvent the wheel is harmful because it discourages curiosity and exploration.
974 points by Lunar5227 | 401 comments
A personal blog essay about how programming skill creates a compulsion to build or fix every tool and problem one encounters.
533 points by rbanffy | 148 comments
A chapter from Michael Lynch's Refactoring English offering advice on writing blog posts that software developers will actually read.
609 points by emmorts | 147 comments
A personal blog essay on the ByteDrum blog about a developer's pile of unfinished side projects and the challenge of actually finishing them.
517 points by fagnerbrack | 113 comments
Blog post on Learn How To Learn describing a method for building projects extremely quickly, such as outlining first and filling in details later.
339 points by jamghee | 225 comments
A blog post by Nick Scialli explaining why he is skeptical of low-code platforms, based on client experiences during software consulting.
400 points by jarmitage | 133 comments
Communications of the ACM research article by Brown, Hermans, and Margulieux on ten findings about learning that software developers should know.
402 points by SigKill9 | 279 comments
Kitemaker blog post by Sigurd Seteklev arguing that teams can do more product work with fewer dedicated product managers.
733 points by signa11 | 297 comments
Blog post on olano.dev arguing that, beyond being read more than written, code is run more than read, extending the maxim about software priorities.
790 points by low_tech_love | 314 comments
A personal blog post by Preston Thorpe, an incarcerated software developer in Maine, describing how he became a programmer and open source contributor while in prison.
446 points by ShMcK | 191 comments
A Substack essay reflecting on debugging as a privilege software developers have compared to other professions where mistakes are harder to trace and fix.
409 points by mNovak | 186 comments
Tell HN post urging readers to submit public comments on IRS Notice 2023-63 about amortizing software development costs as R&E expenses under Section 174.
431 points by simonsarris | 159 comments
A humorous essay written in caveman-speak offering software development advice, especially about avoiding complexity, from the perspective of a 'grug brained' developer.
435 points by mtlynch | 148 comments
Michael Lynch's blog post revisiting Fog Creek's 2005 internship documentary Aardvark'd and the later careers of the people interviewed in it.
442 points by aarondf | 184 comments
A GitHub ReadME guide offering advice to developers on how to finish their software projects rather than abandoning them.