Reading up on software-engineering
100 deep · digging since nov 19, 25
- Notion | The agent-native way to ship software.
Notion introduces agent-native capabilities that let AI agents coordinate software shipping workflows while teams focus on judgment from feedback to launch.
- Video Generation Models are General-Purpose Vision Learners
GenCeption turns a pretrained video generation diffusion model into a unified, feed‑forward vision system that matches or beats task‑specific SOTA across depth, normals, pose, segmentation and keypoints using text prompts.
- Control the ideas, not the code - <antirez>
Programmers should steer AI by defining ideas and designs, not by reviewing generated code, to focus on higher‑level decisions and quality.
- In defense of not understanding your codebase
The author argues that in large software systems it's normal and effective to work with only a partial understanding of the codebase.
- From Prompt Engineering to Intent Engineering
Switch from prompt engineering to intent engineering—describe desired outcomes instead of step‑by‑step instructions—as AI improves, our guidance becomes counterproductive over time.
- Who cleans up after the vibe-coding party?
The piece examines who bears the responsibility for cleaning up after impromptu, enthusiasm‑driven coding sessions and suggests shared accountability among team members.
- PostPeer - Unified Social Media Posting API - Add social media posting, scheduling, and automation to your product in minutes.
PostPeer offers a unified API that lets developers add cross‑platform social media posting, scheduling, and automation to their products in minutes.
- OpenRouter Models - Unified Access to 400+ AI Models
OpenRouter provides a unified API to browse, filter, and retrieve details for over 400 AI models, including pricing, capabilities, and provider info.
- GitHub - sindresorhus/terminal-image: Display images in the terminal
The terminal-image npm package lets developers display PNG, JPEG, and GIF images directly in compatible terminals using native graphics protocols or ANSI block fallback.
- The ChatGPT "Super App" Sort of Super Sucks
The new ChatGPT Mac app merges Codex and chat into a confusing Electron-based super app with poor UI, burying chat under work modes.
- Release v2.0.0 · unlayer/react-email-editor
Unlayer's react-email-editor v2.0.0 drops support for React <16.8 and Node <18, adds ESM builds, fixes destroy-on-unmount, and updates tooling across the stack.
- How GitHub gave every repository a durable owner - The GitHub Blog
GitHub scanned its 14k internal repos, gave every active repo a validated owner via custom properties, archived ~8k unused ones, and enforced ownership at creation within 45 days.
- Introducing Meerkat: an experiment in global consensus
Cloudflare Research introduces Meerkat, a global consensus service using the QuePaxa algorithm to provide strong consistency and high availability for control‑plane data across its 330+ data centers.
- Announcing TypeScript 7.0 - TypeScript
TypeScript 7.0 launches a native Go‑based compiler that delivers 8‑12× faster builds and editor responsiveness, validated by large‑scale production testing.
- Rewriting Bun in Rust
Bun's engineers rewrote its JavaScript runtime from Zig to Rust with Claude Fable 5, eliminating many memory‑safety bugs and boosting stability and performance.
- The Making of Claude Code \ Anthropic
Anthropic shares the inside story of Claude Code's development from an internal CLI tool to a widely used coding agent, highlighting design decisions and team insights.
- State of CLI Coding Agents, Mid-2026
The CLI coding agent market in mid-2026 is crowded with 35+ tools, and this piece systematically compares them across model labs, platform CLIs, and open-source harnesses.
- Closing the Verification Loop
ce-dogfood autonomously verifies software branches by testing every change in a real browser, fixing only clear bugs with regression tests, and escalating trade-offs to humans.
- Ask HN: Who is quitting? (July 2026)
Hacker News commenters share stories of quitting tech jobs due to mandatory RTO, AI-first mandates, toxic management, and disillusionment with engineering culture.
- Fintech Engineering Handbook
Hacker News commenters debate whether monetary values must always be stored as integers, with quants arguing floats suffice for risk modeling but transfers require exact integer precision.
- Reading the internals of Postgres: Database cluster, databases, and tables
A developer explores PostgreSQL's logical and physical storage, showing how database clusters, OIDs, relfilenodes, and file layouts work under the hood.
- Postgres transactions are a distributed systems superpower
Co-locating workflow state and application data in Postgres enables atomic transactions that provide exactly-once execution without application-level idempotency logic.
- Working With AI: A concrete example
A developer recounts using Claude to debug a hyperscript parser bug, illustrating AI's strengths in analysis and boilerplate but weakness in design judgment and general-case solutions.
- I ported Kubernetes to the browser
Sam rebuilt a subset of Kubernetes in Rust, compiled to WebAssembly, to run entirely in the browser for hands-on cluster education.
- You can't unit test for taste
Taste in software cannot be unit-tested because it relies on tacit, contextual judgment that resists full externalization into rules or code.
- Ask HN: How much coding should beginners learn in the AI era?
HN commenters overwhelmingly argue beginners must learn to code first to supervise AI agents, review their output, and understand system behavior.
- Building an Intern
Building a practical Slack agent required 100k lines of TypeScript and four months of iteration to handle serverless constraints, credential management, and secure tool orchestration.
- Understanding is the new bottleneck
As AI agents write code faster than humans can review, understanding remains critical for creative participation, not just verification.
- Autoresearch, Claude and Constrained Optimization
An experiment using Claude Code to autonomously optimize a file compression algorithm over 10 iterations, achieving competitive results against standard tools by iterating on an LZSS-based approach.
- GitHub - workweave/router at console.dev
Router from Weave is a drop-in proxy that routes each prompt to the optimal model in under 50ms, cutting costs by 40-70% with just an endpoint change.
- Documentation · oak
Oak is a version-control and storage layer built for AI coding agents, offering branch-per-session workflows, lazy mounts for instant monorepo access, and full git export for data portability.
- Iterating faster with TypeScript 7
The VS Code team incrementally adopted TypeScript 7, a Go port of the compiler, achieving 4–7× speedups in builds and editor tooling.
- GitHub - lirantal/nodejs-cli-apps-best-practices: The largest Node.js CLI Apps best practices list ✨
A curated list of 38 best practices for building user-friendly, empathic, and interoperable Node.js CLI applications, covering experience, distribution, interoperability, accessibility, testing, errors, development, analytics, versioning, and security.
- What Active Rubyists Are Using in 2026: A Maintainer's Read of the RubyKaigi Survey - DEV Community
A maintainer's analysis of RubyKaigi 2026 survey data reveals that Ruby 4.0 adoption matches 3.4 within six months, Claude Code dominates at 80% usage, and VS Code/Cursor lead editors while mise/asdf challenge rbenv.
- BOND
Bond is an AI-powered Chief of Staff that aggregates tasks from Slack, email, and calendars into a prioritized to-do list.
- Introducing the Safari MCP server for web developers
Apple released a Model Context Protocol server for Safari that lets AI agents inspect DOM, network requests, screenshots, and console output to debug websites autonomously.
- Most AI Work Can Wait
Routing layer design, not model choice, drives cost efficiency by sending 70-80% of AI traffic to cheap local or async models.
- Autoresearch: The feedback loop behind self-improving agents
Autoresearch uses outer loops with feedback signals and human input to let agents improve and maintain systems, reducing bottlenecks while keeping humans central.
- Technological Involution
Technological progress has stagnated as society lost its ability to imagine novel frontiers and founders now chase institutionalized narratives rather than deep personal conviction in technology.
- “It’s Hard to Eval” Is a Product Smell – Hamel's Blog
Products that are hard to evaluate programmatically are likely hard for users to verify, so design for verification first.
- Fintech Engineering Handbook
The handbook catalogs patterns for representing, recording, and executing money movements—precision handling, double-entry ledgers, immutability, and invariants—to prevent data loss or invention in fintech systems.
- Agents as Webs of Beliefs — LessWrong
A framework of intelligent agents as webs of beliefs unifies beliefs, goals, and actions via local consistency, self-predictive models, and drives that balance empirical evidence with preferences.
- Claude Code turned every engineer into three. Now companies need more product thinkers
AI coding tools like Claude Code have tripled engineering output, shifting the bottleneck from coding to product decisions, requiring engineers to focus on fundamentals and product thinking.
- The modern company won't have bullshit jobs
AI agents can automate administrative overhead like syncing tools and tracking metrics, freeing humans for strategic work.
- I rewrote PostHog's SQL parser, 70x faster, while barely looking at the code
PostHog's engineer used parallel Claude Code sessions to rewrite their SQL parser, achieving a 70x speedup by fuzzing against the old ANTLR-based parser as an oracle.
- Ask HN: Where is the programming profession going?
A developer observes that AI has shifted software development from precise, human-driven code to probabilistic, LLM-generated output, questioning the profession's future.
- The minimum viable unit of saleable software
Falling costs of AI-assisted coding shift the build-vs-buy calculus, but hidden maintenance, organizational risk, and irrational buyer behavior keep proprietary software viable.
- Repricing of Software Engineering Labor
AI compresses implementation costs, collapsing the premium for generalist engineers while raising the value of deep expertise.
- I wrote a 70x faster SQL parser while barely looking at the code - PostHog
The author used AI agents to rewrite PostHog's SQL parser in Rust, achieving a 70x speedup (454x in production) via property-based testing and oracle-based development.
- Stop Building Chatbots. Build Agents That Open PRs.
Building agents that open PRs yields durable, reviewable work rather than ephemeral chat replies.
- Writing Loops, Not Prompts, Explained
Loop engineering means automating repeated prompt steering into verifiable systems to free human attention for judgment and review, using a break-even equation to decide when loops are worth building.
- What I’m Finding About LLM Code Style and Token Costs - Jim Montgomery jimmont.com
Using native Web APIs instead of LLM-generated manual implementations reduces output token costs by 85-92% while eliminating entire categories of bugs.
- Flue — The Open Agent Framework
Flue offers a TypeScript framework for building durable AI agents that survive server restarts, using a programmable harness with sandboxes and tools.
- Hotswap - Drop-in open coding models hosted for you
Arcjet provides runtime security for AI applications, including prompt injection detection, data loss prevention, and agent tool controls.
- C++: The Documentary
A new documentary chronicles C++'s 40-year history from Bell Labs to becoming the fastest-growing top-four language, with 90% user growth in 3.5 years.
- Ask HN: Are most corporate SWE jobs performative?
A Hacker News user argues that SWE roles at large companies (including FAANG) are often performative, with managers and teams prioritizing impression over impact.
- Doing nothing at work
Working below full capacity—keeping slack in one's schedule—is essential for handling high-value tasks, preventing burnout, and responding to crises, but requires careful communication with managers.
- Cleaning up after AI rockstar developers
Hacker News commenters debate whether software craftsmanship is threatened by AI, comparing it to industrial manufacturing and arguing that the 10x developer myth is often exaggerated.
- I design with Claude more than Figma now
Hacker News commenters debate whether AI-generated prototypes pressure teams into shipping incomplete code, polarizing between productivity gains and production risks.
- Software is made between commits
The article argues that software is truly made during the messy, unstructured work between commits, and proposes a tool like DeltaDB to capture that process for review.
- Ask HN: Why is the HN crowd so anti-AI?
A Hacker News user asks why the community seems anti-AI, arguing that code quality matters less than shipping speed and user satisfaction.
- Ask HN: What was your "oh shit" moment with GenAI?
GenAI tools like Claude have enabled users to reverse-engineer decades-old hardware protocols and software, turning once-impossible tasks into hours-long projects.
- If you are asking for human attention, demonstrate human effort
Developers increasingly ignore AI-generated pull requests because the effort to review sloppy code doesn't feel reciprocated.
- Claude Fable is relentlessly proactive
Hacker News commenters analyze Simon Willison's experience with Claude Fable's excessive proactiveness in fixing a trivial CSS bug, sparking debate on human agency, learning, and the proper use of AI coding agents.
- Making Graphics Like it's 1993
An indie developer builds a retro first-person shooter using a software renderer with palette-based shading, replicating 1993-era graphics constraints.
- Building an HTML-first site doubled our users overnight
Replacing a SPA with plain HTML forms and server-rendered pages unexpectedly doubled a site's users, challenging assumptions about framework necessity.
- Claude Fable 5 | Hacker News
Claude Fable 5 demonstrably solves difficult coding problems—like compiling CPython to WASM—that stumped earlier models, though evaluation remains subjective and vibe-based.
- The Optimal Amount of Slop is Non-zero - Doug Slater
Doug Slater argues developers should match code-review rigor to risk, shipping unreviewed LLM code is acceptable only for limited-distribution, low-consequence software.
Takes
incredible algo update my timeline is full of makers building stuff I LOVE THAT AND I LOVE YOU ALL ❤️
@tibo_maker
1/ Last week at @aiDotEngineer, I presented the 2026 AI Engineering Survey: 1,000+ AI engineers on model selection, build vs. buy, who’s shipping with AI, and (of course) whether GPUs are going to space. This year, we ran it with @NotionHQ and @vercel. Some highlights 🧵
@barrnanas
What Is a Software Factory?
@chamath
I built a software factory that actually works. Here's what I learned.
@piersonmarks
Fun (and functional!) new BC5 feature we just added to Card Tables today. We're calling it Wormholes. Here's how it works in a quick, casual 90 sec video.
@jasonfried
If you want to start a startup, don't learn "entrepreneurship." Learn how to build things. The hard part of startups is not "entrepreneurship" but product: to know what to build, and to be able to build it.
@paulg
Very excited to help chart the future of Git (and SCM generally) for the agentic future with Taylor!
@gdb
I had early access to 5.6/Sol for ~month. Sol is my default. It is faster, plans/judges just as good as Fable, and I think produces better overall work. I’ll reach for Fable still for highly targeted debug or performance work with clear reward functions. A cheeky way I describe Sol vs Fable to my friends is that Sol is a charismatic, efficient, talented coworker you’re jealous of. Fable is a genius recluse that is brilliant at its fixations but doesn’t go out, doesn’t date, and you don’t want to hang out with them much lol. Fable is undefeated at highly targeted debug/security/performance goals. It’s a sight to behold and I was never able to get Sol to push as hard in this category. I’ll keep using it for this. Sol is better or comparable at everything else, in my experience. Give it a shot, it’s hard to describe but it’s just more enjoyable to work with. (Disclaimer I have no financial ties to either lab, wasn’t paid for any of this.)
@mitchellh
I went to Miami to chat with @thdxr, co-founder of OpenCode. We talked about the future of software engineering, coding agents, and why open source matters more now than ever. Timestamps: 0:00 Intro 5:30 Miami vs San Francisco tech scene 15:05 OpenCode origin story, scaling while open-source 25:03 OpenCode vs. Anthropic: owning models, open-source AI 33:36 AI hardware shortages, predicting the future 42:15 The bet of open-weight models, China vs. US 48:34 Why inference is hard, economics of intelligence 55:36 Will developers be automated? Software engineering as a craft 1:11:02 Advice to founders, building in public, marketing I had so much fun making this with @ad0rnai. Enjoy!
@Madisonkanna
What should the IRS ship in the second half of 2026?
@shl
This is our first time telling the story of how we first built and launched Claude Code, starting with its origins in Anthropic safety research. So much more to do. We are 1% done.
@bcherny
What The New 100x Agentic Engineer Looks Like In The Era Of Fable & GPT 5.6
@systematicls
Own the Loop: A Field Guide to Agent Harnesses
@aparnadhinak
One agent runs 99.98% of Gumroad
@shl
The Great Descent
@chamath
How I've changed the way I do code reviews by using the /visual-recap skill:
@Steve8708
Hot take: I think it's still important to understand the code that our agents write! In this mega thread (based on my AIE talk today), I will explain why that's the case, and show some ideas for how to efficiently understand code. Alright, let's dive in. 1/
@geoffreylitt
Introducing Interfere. Interfere observes everything that happens in production, investigates what’s broken and fixes problems before your users notice them. Spend your time building what’s next, not fixing what’s broken. Get early access today.
@interfere_
Boris sat down with Spotify VP of Engineering Niklas Gustavsson. Spotify ships 4,500 production deploys a day, and 73% of PRs are now AI-assisted.
@ClaudeDevs
Introducing Claude Science, a new app designed with every stage of research in mind. Artifacts traced to their code, environments managed on demand, and 60+ optional scientific databases that you can connect. Available now in beta.
@claudeai
These are not three separate concepts.
@RhysSullivan
Human in the /loop
@ericzakariasson
start running deepsec on all your repos trust me.
@DavidOndrej1
As engineering, product, design, DS, etc. melt into a new kind of role, I was reflecting on what roles might look like in the future. For example, when I look at the Claude Code team I see what I think is five archetypes: 1. Prototyper: comes up with brand new ideas; churns out many ideas, most of which don't ship 2. Builder: quickly turns a prototype/idea into production-grade product/infra 3. Sweeper: cleans up the UI, simplifies the code and system, unships, optimizes performance 4. Grower: takes a product that has been built and iterates on it to improve Product-Market Fit 5. Maintainer: owns a mature system to make it secure, reliable, fast, and efficient as it scales Many people span across 2 roles, and sometimes 3 roles. I also notice that these roles are not really tied to job function -- eg. across Anthropic, some designers match category 1, some 2, some 3; same for engineers, PM, DS. A healthy team needs a mix of these, depending on the product: - A product that is new and pre-PMF needs people that are strong at 1+2+3 - A product that is growing and has found PMF needs 2+3+4 and some 5 - A product that has strong PMF needs 3+4+5 and some 2 Maybe product roles of the future will look more like this, and less like the domain-specific roles of today?
@bcherny
"We give [agents] tasks overnight and then we wake up and the backlog is resolved and bugs are squashed." Here's my new episode with @jess__yan, product lead at Anthropic. Jess showed me how to build a long-running Claude agent from scratch and how Anthropic product teams use agents internally to: → Understand the codebase → Synthesize user feedback → Pressure-test API decisions Some quotes from Jess: "You should be able to tag [agents] anywhere, but they should also proactively surface things for you in the way that a co-worker truly would." "For me, agents really unlock depth. Rather than poking engineers on what they’re doing, I can just track the PRs directly and see which ones are merged." "Long-running cloud agents are not bound by the constraints of your laptop and when it's on." 📌 Watch now:
@petergyang
This is a new paradigm for interacting with Claude that is significantly more "inline" with all the other human activity org-wide. Once you do all of the under the hood engineering work to make this "just work" (e.g. across tools, integrations, compute environments, memory, security, etc.), Claude basically joins the team in a seamless way - you can talk to it as you would talk to a person and it can help with a very large variety of workloads. Imo this is the 3rd major redesign of LLM UIUX. The first paradigm was that the LLM is a website you go to, the second was that it is an app you download to your computer. This third one is that it is a self-contained, persistent, asynchronous entity with org-wide tools and context, working alongside teams of humans. It really takes a while to wrap your head around it, but it works and it is awesome.
@karpathy
A friend asked me how to actually build a company that runs on AI agents. I drew him 4 simple diagrams and this is what I told him: For this to work, a few things have to be true. - The humans move up to strategy, taste, and judgment while agents handle the execution. - The whole business becomes readable to agents. Your data, SOPs, pricing, permissions, and decisions all live in one shared context layer. - And you point it at the right work. Repetitive enough for an agent, complex enough that the incumbents never bothered. That's the goldmine. In the old world, the company was the people. They held the knowledge, made the calls, did the work. In this new world, the people become the creatives, the agents become the labor, and the company itself becomes the context layer. That shared brain is the actual company now. The humans and the agents are just plugging into it. Which means the most valuable thing you can build in 2026 is a business so well-documented that an agent can run it. I see it everyday with @MeetLCA. I don't talk about it much publicly, but we've built a SWAT team for building AI-native orgs and AI-native products. The moat is how legible your company is. I drew it all out below.
@gregisenberg
Head of Engineering at Shopify, Farhan Thawar: "While you're still perfecting your prompts, the best engineers stopped writing them months ago. Learn to write loops instead." 44 minutes on the new AI formula that's changing how the best engineers build. Watch it, then save the step-by-step guide below 👇
@zodchiii
How we imbue coding agents with our design standards
@rauchg
AI can build an app in an afternoon. But getting it safely into other people's hands is a whole other challenge! This is the problem that I've been working on these past few months. I'm proud to finally share how we solved it with Block App Kit! https://engineering.block.xyz/blog/from-localhost-to-launched-safely-shipping-apps-that-anyone-can-build
@jedwards_27
Head of Engineering Shopify: "AI writes the code, AI reviews the code. Your job is just to write the loops around it." 26 minutes on how AI changed the way 3,000 engineers work inside a single company. Ignoring it while everyone else uses AI to do more is the fastest way to fall behind. Watch it, then read the step by step guide on loops below.
@AnatoliKopadze
In addition to your own @leerob, every company now needs their own @mattpocockuk. Role: someone who keeps up with every release, model drop, benchmark, loop, skills, paper and changelog. Then distills and briefs the team on Friday. I'm calling it Dev Intel. Who's hiring? :)
@shadcn