182 stories tagged software-engineering, newest first.
46 points by eigenBasis | 21 comments
Daniel Miessler blog post arguing that written intent, via an 'Ideal State Artifact', rather than code should be the source of truth when building software with AI.
46 points by alxgsv | 84 comments
Personal blog essay by Uploadcare CTO Alex Gusev reflecting that AI coding agents have removed the engineering challenge that once motivated him.
857 points by ltratt | 744 comments
Dan Luu essay arguing that advancing AI coding models let developers build more ambitious software, citing pgrust, a regex engine, ripgrep fork, and board game AI projects.
219 points by albertodenia | 141 comments
Blog essay by iOS developer Alberto Denia arguing agentic coding makes code malleable like clay, contrasting hands-on 'artisan' and automated 'factory' workflows.
534 points by rzk | 650 comments
An Ask HN thread asking how engineers cope with shipping AI-generated code they don't fully understand, citing a Meta engineer's LinkedIn post.
58 points by azhenley | 69 comments
CMU School of Computer Science news article announcing a Microsoft partnership to train early career software engineers.
18 points by mmarvramm | 35 comments
A blog post by Mihai Avram discussing how to verify code written by AI, as AI increasingly takes over code generation.
56 points by vismit2000 | 13 comments
ACM Digital Library page for the 1982 Communications of the ACM article "The future of programming" by Anthony I. Wasserman and Steven Gutz.
407 points by pretext | 386 comments
An Anthropic engineering blog post by Addy Osmani describing how the Claude Code team reviews the high volume of code produced by AI agents while minimizing human review time.
28 points by speckx | 27 comments
A personal blog post on pinecoder.dev reflecting on how the author's previous job now feels distant.
5 points by epeicher | 0 comments
OpenStation blog post by Roberto Aranda about deleting 168,000 lines of code comments and finding his AI coding agent performed no differently.
65 points by ilreb | 85 comments
Personal blog essay by Peter Bryant arguing that software engineers may be better understood as blue-collar skilled tradespeople than white-collar workers.
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.
162 points by jllyhill | 196 comments
A personal blog post by Cendyne describing losing an engineering job after leadership decided an LLM called Fable was cheaper than their compensation.
197 points by rafiss | 89 comments
Cockroach Labs blog post describing a five-month experiment using a hospital-style workflow where bugs are patients and AI coding agents act as a medical team.
2038 points by muglug | 236 comments
MIT News obituary reporting the death at 90 of Margaret Hamilton, the computing pioneer who led software development for the Apollo program.
30 points by signa11 | 32 comments
A blog post on the Structure and Interpretation of Computer Programmers blog listing reasons to dislike AI-assisted coding.
38 points by brugidou | 37 comments
A Criteo Tech blog post on the skills junior engineers must build themselves rather than relying on AI tools.
71 points by ibobev | 25 comments
A blog post by Daniel Lemire on his blog titled "Ephemeral testing," a short essay about a software testing approach.
60 points by birdculture | 39 comments
A blog post by GNOME developer Michael Catanzaro titled "The Era of Software Quality, or the Era of Ostriches?" discussing software quality.
15 points by cliffclimber | 0 comments
Chain of Thought newsletter post featuring npm co-founder Laurie Voss on how AI-cheapened coding shifts value from software engineering to product engineering and context.
216 points by citelao | 103 comments
A personal blog post by a software engineer who became an EMT in 2024, ranking 21 reasons he delayed getting certified.
28 points by vinhnx | 64 comments
Blog post by Michael Catanzaro on GNOME blogs discussing whether the industry is entering an era of software quality or ignoring quality problems.
73 points by haute_cuisine | 40 comments
A Substack essay by Alex Martsinovich arguing that agentic coding causes four problems: slop, alienation, deskilling, and team fallout.
58 points by speckx | 22 comments
Personal blog post criticizing coworkers who relay AI (Claude) answers instead of their own expertise, arguing it signals lack of authority and leads to overengineered software.
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.
458 points by firstSpeaker | 459 comments
Alex Ewerlöf's opinion essay arguing that AI and LLM coding tools have not solved software coding, drawing on his experience building AI systems.
142 points by utiiiD | 88 comments
Adaptive Capacity Labs blog post arguing that code review involves more than defect detection that can be automated.
4 points by dimonomid | 0 comments
A personal blog essay using Cato the Younger's speech on the Catiline conspiracy, as recorded by Sallust, to reflect on how the software field names things.
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.
14 points by fagnerbrack | 7 comments
A blog post by Fagner Brack on Medium describing what an AI-native approach to software development with stable infrastructure looks like.
311 points by dimonomid | 438 comments
Blog post by Alexandru Nedelcu arguing that AI lacks wisdom and that relying on it for coding, skipping code reviews and reading code, erodes developers' own judgment.
138 points by perrygeo | 77 comments
An htmx.org essay by Carson Gross arguing that Markdown is becoming source code and should be checked into /src, with code and tests derived from it rather than ephemeral prompts.
426 points by jaykru | 552 comments
Personal blog essay by Jay Kruer arguing LLMs remain overhyped despite headline results like Navier-Stokes, citing poor generalization, reward hacking, and specification costs.
362 points by rglover | 137 comments
A blog essay arguing that the conditions of software work—speed, money, complexity, abstraction, and freedom to change—make normal people lose their sense of proportion.
378 points by davidmckenna | 239 comments
Dan Luu essay arguing that most people encounter the same software bugs he does but fail to notice them, and that products often ship badly broken.
401 points by sebg | 221 comments
Geoffrey Litt's written version of an AI Engineer conference talk arguing developers still need to understand agent-written code, with ideas for understanding it efficiently.
877 points by florianherrengt | 785 comments
Blog post arguing that AI-generated code floods senior engineers with huge PRs and is hollowing out the middle tier of software engineering roles.
392 points by 0xedb | 448 comments
Google for Developers blog post by Cameron Balahan and Richard Seroter arguing that Go is well suited to AI-assisted software engineering.
761 points by senko | 446 comments
Blog post by Senko Rašić arguing that the claim "code was never the hard part" amid LLM coding hype is an insult to programmers.
1278 points by MaxMussio | 527 comments
Blog post by Sean Goedecke arguing that the most important skill in prompting LLMs is expertise in the domain being prompted for.
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.
702 points by pchm | 526 comments
Blog essay arguing that despite hype about AI solving coding and an 'Agentic Era', software quality keeps getting worse.
1264 points by crowdhailer | 634 comments
Ray Myers blog post contrasting the Zig creator's stance on AI with Anthropic's campaign to replace software engineering.
560 points by backlit4034 | 431 comments
Personal blog post by a software engineer explaining why he stopped arguing with people over technical correctness and what he learned about arguments.
321 points by BerislavLopac | 157 comments
Charity Majors' Substack essay arguing that AI-assisted development requires more engineering discipline, comparing it to the shift from pet servers to immutable infrastructure.
1613 points by jjfoooo4 | 477 comments
Blog post arguing that people forwarding AI-generated text to colleagues should first digest it and demonstrate their own effort before asking for others' attention.
334 points by Sukram21 | 116 comments
Blog post by Sean Goedecke arguing engineers should work fewer hours at ~80% utilization because tech company performance is dominated by outlier, high-impact events.
1029 points by poisonfountain | 967 comments
A personal blog post by a software engineer with 10 years of experience reflecting on how LLMs are eroding their career and their uncertainty about what to do.
387 points by Ekami | 645 comments
An Ask HN post asking why Hacker News commenters are skeptical of AI coding tools, arguing that shipping speed matters more than code elegance.
338 points by jsve | 242 comments
Blog post by Sumner Evans arguing against the Conventional Commits standard, saying it encourages focus on the wrong things and fails to deliver on its promises.
774 points by aaronbrethorst | 484 comments
Blog post arguing that agentic AI shifts software's binding constraint from building code to judging correctness, making domain expertise the real moat.
1102 points by signa11 | 407 comments
Blog post by Nolan Lawson arguing that LLMs can be used to write higher-quality code more slowly, such as finding bugs, rather than producing low-quality code fast.
742 points by nilirl | 314 comments
Essay by Tuhin Nair on why senior software developers struggle to communicate their expertise to others.
826 points by indigodaddy | 877 comments
A Medium essay by Noah Mitchem questioning whether Python remains the best language choice when AI tools write most of the code.
380 points by movis | 624 comments
Sean Goedecke's blog post arguing that because AI use reduces learning on the job, software engineering may no longer be a lifelong career.
331 points by cratermoon | 99 comments
James Shore blog post arguing that AI coding agents must cut software maintenance costs proportionally to how much they speed up code writing.
441 points by laurentlb | 286 comments
Blog post by Laurent Le Brun recounting the history of IDEs and code editors used internally at Google for its main codebase.
640 points by jeromechoo | 308 comments
A blog essay by Steven Langbroek titled "Programming Still Sucks," an 8-minute read on programming, leadership, and AI.
441 points by Brajeshwar | 229 comments
Blog post by Ibrahim Diallo arguing that developers, not AI tools, are responsible when an AI agent deletes a production database.
343 points by BOOSTERHIDROGEN | 168 comments
Addy Osmani's blog post introducing Agent Skills, an attempt to make AI coding agents follow senior-engineer practices like specs, tests, reviews, and scope discipline.
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.
1039 points by milkglass | 713 comments
Substack essay comparing the West's loss of defense manufacturing capacity to declining junior software engineer hiring and the erosion of coding skills.
317 points by theorchid | 86 comments
A Martin Fowler "Fragments" blog post with short notes, including a Pragmatic Summit interview with Kent Beck and thoughts on technical, cognitive, and intent debt.
1092 points by milanm081 | 495 comments
A website cataloging 56 laws, principles, and patterns that shape software systems, teams, and decisions, with a companion book.
363 points by walterbell | 224 comments
A blog post by Ashley Rolfmore titled "Stop trying to engineer your way out of listening to people"; the captured screenshot instead shows her post on playing Traitors at home.
576 points by jakelsaunders94 | 401 comments
Personal blog post by Jake Saunders expressing fatigue with the constant discussion of AI in software and tech circles.
334 points by jryio | 357 comments
A personal essay arguing that software engineers shouldn't tie their identity to their job title as machines increasingly automate their work.
566 points by stevekrouse | 419 comments
Steve Krouse blog post arguing that code will not be replaced by AI-written specs, since a sufficiently detailed spec is itself code.
535 points by signa11 | 291 comments
A Haskell for all blog post, built around a comic strip, arguing that a specification detailed enough to generate a program is effectively code itself.
456 points by greyface- | 272 comments
Blog post on apenwarr arguing that each added layer of review in an organization slows work down by roughly an order of magnitude.
545 points by ndr42 | 435 comments
Ars Technica article (via Financial Times) reporting Amazon will require senior engineers to approve AI-assisted code changes after AWS outages linked to AI tools.
811 points by aamederen | 451 comments
A Terrible Software blog post arguing that engineering organizations reward complex work over simple solutions when deciding promotions.
364 points by flail | 259 comments
A Manager.dev newsletter post by Anton Zaides arguing that engineers should reconsider accepting promotions to engineering manager roles.
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.
634 points by ColinWright | 737 comments
Nolan Lawson's blog post lamenting how AI coding tools are reducing programmers to code reviewers and mourning the loss of the programming craft.
867 points by anurag | 350 comments
Mitchell Hashimoto's blog post describing his step-by-step journey adopting AI coding agents, from dropping chatbots to always having an agent running.
519 points by swah | 265 comments
Sean Goedecke's blog essay on loving his software engineering job because he is driven by being useful, drawing on Gogol's The Overcoat.
1555 points by cdrnsf | 643 comments
Addy Osmani's blog post sharing 21 lessons from 14 years as an engineer at Google, focused on people, alignment, and navigating work beyond code.
537 points by yuppiepuppie | 263 comments
Blog post by Andrew Graham-Yooll on the promotion advice "try to take my position": doing the next-level job and taking on responsibility before getting the title.
474 points by rishabhaiover | 511 comments
An X (Twitter) post by Andrej Karpathy reflecting on feeling behind as a programmer amid rapid AI-driven changes; the post content did not load.
356 points by mooreds | 174 comments
A Terrible Software blog post discussing what actually makes a software engineer senior.
777 points by simonw | 599 comments
Simon Willison blog post arguing developers must prove their code works through manual and automated testing before submitting it, especially when using LLM tools.
999 points by birdculture | 499 comments
Final Round AI blog post on AWS CEO Matt Garman's three reasons AI shouldn't replace junior developers and how AI should be used at work.
782 points by evankhoury | 394 comments
Martin Kleppmann blog post predicting that AI will bring formal verification with proof assistants like Rocq, Isabelle and Lean into mainstream software engineering.
380 points by mooreds | 281 comments
Blog post on the Helmet Hair blog arguing that most technical problems in software teams, such as accumulated technical debt, are really people problems.
348 points by gfysfm | 236 comments
Sean Goedecke blog post explaining why competent engineers at big tech companies produce sloppy code, citing short tenures and engineers working outside their expertise.
580 points by pseudolus | 536 comments
IEEE Spectrum feature article examining why large, expensive software and IT projects continue to fail despite trillions in spending.