Luke

Luke

@lukehedger.dev

Software engineer. Building things for lego.com. Distributed systems, serverless, event sourcing, durable agents. Wrote Serverless Development on AWS (O’Reilly) https://lukehedger.dev/ https://lsh.pckt.blog/ 📍 London

433 followers116 following635 posts

want to start talking about agent workflows in the context of specific stacks, rather than just generally “this is how to work with agents”

my workflow for the last few months has been: spend 2-3 weeks thinking about/designing something and then build it in a few days with minimal iteration. then it’s immediately onto thinking about the next big/interesting problem for 2-3 weeks and build it in 2-3 days

Luke reposted

Replying to @sunshowers.io

Code that works at a point in time is mostly uninteresting. What matters is building structures to ensure code stays correct over time. That to me is the essence of engineering in software

“If the codebase still exposes services, controllers, repositories, managers, helpers, common folders, generic file names, and shared extension points, then those are exactly the shapes the agent will keep producing”

Luke reposted

If you're curious how all those newfangled domain names come to be -- I wrote a feature for WIRED on top-level domains and the people who make them I thoroughly enjoyed meeting all the kind and fascinating people in this wacky domain world. (And I promise it has nothing to do with cat thongs.)

WIRED@wired.com

Soon, hundreds of new top-level domains, including .meow and .fart, could be added to the internet. WIRED goes inside the backroom shenanigans of ICANN, the organization at the helm.

why did we think it was a good idea to pay money for an agent to call an API? we’ve been calling APIs for decades, for free!

100%

Nick Gerace@nickgerace.dev

Jev shaped releases are exciting and we’re thinking internally about confidence levels, alert filtering and how we can make better software rather than more software. I’m a bit over the speed part now. I am much more interested in agents for quality from now heading into 2027.

still trying to answer this question in 2026 (50 years later)! "there is a critical question facing software engineering today: How to modularize a software system so the resulting modules are both testable and maintainable?" A Complexity Measure, McCabe - 1976 literateprogramming.com/mccabe.pdf

Luke reposted

Claude Opus 5.5 is out. “It's ~30% faster and ~40% cheaper than Opus 5 per task. In Claude Code: - 5-hour session limits increase 20% today - Opus 5.5 is priced lower, so it goes 25% further within limits - Pro, Max, and Team users get a reset to use anytime” www.anthropic.com/claude-opus-...

anthropic.comIntroducing Claude Opus 5.5Claude Opus 5.5 leads in agentic coding and knowledge work, and costs 40% less to run than Opus 5 on typical workloads.

this is what my team has spent the last few months doing. the one thing in software engineering you never used to do is now the best thing you can be doing! the results are incredible - you can finally have the software you need to support all the features you want to ship!

Kate Holterhoff, PhD@kateholterhoff.com

... but also because this story continues a pattern of large-scale architectural changes that used to be dismissed as too risky or too expensive, that are getting done now that agents have changed the cost of writing and maintaining new code.

agents orchestrating agents? you’re doing it wrong durable, deterministic and efficient agentic engineering needs software calling agents

Timnit Gebru@timnitgebru.blacksky.app

Literally people in graduate school with the founders of Deepmind used to roll their eyes when they talked about "AI" extinction risks. They are in the TESCREAL bundle & attended all the singularity summits and such. You can read about it in one of my papers. dair-institute.org/projects/tes...

Luke reposted

As a coder, you need at least 2 AI providers in case one is offline. Use different models from those providers for different tasks.

Luke reposted

Replying to @dame.is

most people probably don't understand that agentic software development is now effectively the industry standard, even to the point that Zohran Mamdani's administration leverages agentic software development this is the reality we're working with, and it's a very tricky environment to navigate

Luke reposted

Replying to @flohofwoe.bsky.social

TL;DR is basically that I don't want to use LLMs to gain speed (e.g. add more features faster), but to increase robustness and quality (and I would even accept *losing* implementation speed for that).

Luke reposted

Frontier AI models are converging on similar intelligence, yet cost per task can still vary 10x-60x across vendors. That seems unsustainable as models become more substitutable. A lot of frontier lab economics depend on customers paying huge premiums for increasingly marginal intelligence gains.

skills are a gamble - they are loaded into context non-deterministically and the instructions inside them are unenforceable. correctness is deferred to verification, which is unnecessarily late

if you know exactly what you want the agent to do, bake it into the system prompt for a specialist agent directly take a writing skill for example - switch this for a Writer subagent and get the orchestrating agent to spawn it whenever something needs to be written

does the same existential threat apply to internal platform teams too? if product teams are best placed to design tools to fit their use and can now build them to exact specifications, the generic solutions platform teams provide are no longer worth the hassle

Luke@lukehedger.dev

the existential threat to companies building ai-based devtooling seems to be personal software devtooling appears to be heading towards bespoke software written by you/your org for you/your org build vs buy for devtools will settle to build if you need and can design it, your agent can build it

Luke reposted

Replying to @masnick.com

Multiple people I know have told me that they love the idea of Bluesky, and want it to succeed, but have abandoned it for X because the use agentic tools in their work and find them incredibly useful, and feel that any mention of their usage here leads to hate and ridicule.

AI is always going to be polarising but it is a shame that we can’t have considered debates yet - it always has to be “it’s perfect” or “it’s evil”. Neither extreme is true and it’d be nice to chat about the spectrum in between on here

Luke reposted

Load-bearing seams relitigate the honest takes, and that’s where the ratchet bites

wrote up some thoughts on the yegge Thunderdome post build your own harness, CD is dead, code review is long dead! lsh.pckt.blog/harnesses-ga...

lsh.pckt.blogharnessesdon’t put all your yegges in one basket
Luke@lukehedger.dev

if you haven’t read the latest from yegge you should. “I don't care how much money you have; your spouse is not going to let you spend almost ninety thousand dollars a month on your hobby game. I didn't even bother asking.” yegge.ai/essays/the-s...

Luke reposted

What’s one side project you moved to serverless/Workers that you’ll never go back to traditional hosting for? #CloudflareChat

ooo this looks like a good rival to the GitHub Copliot app, which I’ve been using lately as the main driver of agents. the multiplayer aspect will be super cool to see how it feels let me in @zed.dev !

Zed@zed.dev

Today we’re introducing Delta. Delta is a multiplayer environment for coding with agents and reviewing what they build, powered by DeltaDB. The first invites to our private beta are going out now. zed.dev/blog/introducing-delta

the existential threat to companies building ai-based devtooling seems to be personal software devtooling appears to be heading towards bespoke software written by you/your org for you/your org build vs buy for devtools will settle to build if you need and can design it, your agent can build it

if you haven’t read the latest from yegge you should. “I don't care how much money you have; your spouse is not going to let you spend almost ninety thousand dollars a month on your hobby game. I didn't even bother asking.” yegge.ai/essays/the-s...

yegge.aiThe Shape of Things to Come, Part 1: The Continuous Thunderdome — Steve YeggePart 1: The Continuous Thunderdome. Loops and graphs, Wheelhouse and Beads, the end of human code review, the Land Rush that replaces CI/CD, and the Wish Factory — a field report from 12 months in the...

this is great advice!

Corey Leigh Latislaw@colabug.bsky.social

Would encourage you to stop inspecting a particular PR and let the agents continuously improve the code base as the feature/software comes together. If you are reviewing the PRs, identify the class of problem where it fails and improve the harness to produce better code next time.

who is working on deterministic automation for agents?

Hacker News Companion@hncompanion.com

The counterargument was that general models gracefully handle messy edge cases where smaller models fail. Other commenters pointed out that many repetitive tasks assigned to small models don't need AI at all — traditional deterministic code is still faster and cheaper. #programming 2/4