Two kinds of senior engineers right now:
One is dabbling with AI and waiting to see how it all shakes out.
The other has already pushed the agents to their breaking point, has hard-won opinions about where they fail, and is shipping in hours what used to take weeks.
We’re hiring the second one. Fully remote. https://t.co/GGAKVHvXOk
I refuse some of the most important real-world systems in aviation cannot handle 200 QPS
It’s almost an inconsequential amount of traffic for any modern system
While I understand aviation is not considered “modern” by tech industry standards - come on…
AI interfaces nowadays are still pretty much turn-based.
In my PhD thesis, I thought about what interaction would look like if we could go beyond taking turns.
One example is intra-turn interaction:
Best framing I’ve seen of the new responsibilities of a software engineer in the agentic era. Hardly the extinction of the role. The future demands more engineering, not less!
Skills should be made reactively when the agent struggles with something
Not proactively
And always ask the agent how it could've done better; often a skill isn't the answer
Finally, ask the agent to eval your skill
So apparently any updates to the Digital Ocean firewall (web, api, doctl) pull the whole list, make the local change, and replace everything? What a terrible design. Just begging for race conditions.
i learnt this lesson this year. it's helped me follow through on my ideas and not get stuck overthinking it
don't ask if you should do the thing. do it, then come back with a demo or something tangible
you can just do things
The "code doesn't matter anymore" crowd is wrong. It's clear that AI models perform better when they're working in a well maintained codebase. The people on here whose AI is shipping major bugs are working in the sloppiest codebases known to man. The software engineers are fine.
To make something *truly* great, you always have to put in more time and effort than you want.
The good news is most don’t, so if you do, it’s all the more likely it’ll stand out.
we will need to rebuild and rewrite much of software to adapt to a new, faster pace.
code used to arrive one drop at a time. soon, if not already, code will be written as if it were a continuous stream, like a violent river twisting and turning as it pleases.
this is not a new thing: big tech cos have had to deal with this with the enormous scale of their engineering teams. but now ai has brought an incredibly elastic and capable workforce wielded by every engineer. this is your problem now, and the only way to adapt is to evolve your systems so agents - even and especially the ones with little context about the right way of doing things - can thrive. make the easy thing the right thing.
your codebase is becoming organic architecture. agent contributions grow around the constraints and guardrails you’ve designed. good software engineering matters even more now! and no, the continuous stream of code is not something you have to watch helplessly. be more ambitious and design systems, frameworks, and languages to control the chaos.
the time for mourning coding is long over
Madness - 12 hours into the outage. Microsoft is posting regular updates but they have not figured out what is causing servers to die when brought back online
From their updates it sounds like it’s a thundering herd + some other weird issue they’ve yet to pinpoint