Hugops to the folks at @github.com 🫶 having to deal with a major incident on a bank holiday is no fun
Leo Sjöberg
Leo Sjöberg
@phroggyy.dev
Product Engineer @incident.io, previously CTO @jobilla. Balance whisky and wine with triathlons. Love buying domains, bad at using them.
98 followers193 following84 posts
Leo Sjöberg reposted
Came across a good read about the performance improvements to Go maps in 1.24 themsaid.com/map-internal...
All you need is Postgres
Inspired by the post on HN yesterday about running graph queries on Postgres with recursive CTEs, my coworker installed the SQL/PGQ patches locally and ported all the examples to this native graph query language coming (eventually) to Postgres! www.enterprisedb.com/blog/represe...
The problem with "move fast and break things" is that most people underestimate the cost and probability of "break things" occurring. Works well when you're a startup, I suspect less so when you're the literal government processing a few trillion dollars annually, but let's see
New Exclusive building on Wired's reporting: Musk operatives have already pushed live to production extensive code changes to the Treasury Department payment system which makes 95% of fed govs payments. talkingpointsmemo.com/edblog/musk-...
I'm really looking forward to Christmas, but I'm *also* really excited to get back to work in January after my two weeks off. @incident.io's gonna be building some incredible stuff next year and I can't wait 🔥
Leo Sjöberg reposted
This week, we launched Scribe — an AI agent for incident calls, that: 1️⃣ transcribes in real time 2️⃣ shows the current topic in Slack/Web so you always know what's being discussed 3️⃣ surfaces key points and actions, and summaries on the go Genuinely one of the best things we’ve shipped this year! 🚀
Whenever I tell people I work on a paging product, I inevitable get asked a variation of "but if you use your own product, how do you get paged when it breaks?" It's a fun problem to solve, and Lawrence wrote a great post about how we do it 🔥
"Who watches the watchers?" is funny as a phrase, less so as a problem you need to solve, which it became when building on-call. It's possible for us to receive a page saying "paging is broken" and while I hope we never do, thought it would be fun to share how it works. incident.io/blog/who-wat...
I've found AI to be really good at reviewing code, and writing tests. In the last week, I've done a bit of work on some fairly critical code. For those changes, I've first asked AI to review it for bugs, and then to write tests for the functionality I've added, and it does a remarkably good job!
Past few days we've been doing TDD using LLMs. One LLM grades the output of the other and it's... amazing. It works incredibly well and it really helps write some tests that I usually wouldn't have because the criteria was too fuzzy ("make sure the text includes a mention of Anna and her car")
The Bluesky team has done such an incredible job, particularly over the last few weeks. They keep gaining millions of users and you never even notice it as a user, truly a testament to the calibre of their team
bluesky engineers: perhaps today it’ll be a little slower, we’ll catch our breath the internet: MORE!!