Leo Sjöberg

@enunomaduro We looked into this last year when the M3s came out and the answer was: upgrade from M1, but not M2! incident.io/blog/festive-m…

Currently using a 2021 Apple M1 Pro (14”, 16GB). Considering upgrading to a 2024 M4 Max (16”, 36GB). Tasks: Chrome, coding (PHPStorm, etc.), streaming with Streamlabs, video editing, external monitor usage, gaming, etc. Is it worth upgrading?

This week, we launched Scribe — an AI-powered agent for incident calls. No more "can someone take notes" or "can someone catch me up" moments. Scribe has you covered. 1️⃣ Every word on incident calls is now captured and transcribed in real-time. 2️⃣ We surface the current topic in Slack/Web - never wonder what’s being discussed and monitor multiple calls in real-time. 3️⃣ Key discussion points, decisions, actions, comments and call summaries are surfaced live in Slack. I've been using it for the past few weeks and it's one of the best things we've shipped this year 🚀 It honestly feels like magic ✨

@enunomaduro It's also fine if some of your application has duplicated code. Copy-paste is allowed in business logic, not *every* duplication needs an abstraction!

it's fine if some of your tests have duplicated code. copy-paste is allowed in tests, and there's no need for "abstractions" in your test suite

Having flown in from London, it's bizarre to me how many software engineering tooling ads there are in San Francisco. Easy to say that this is the centre of tech, but different (and cool!) to see how that translates in the real world

Super quick tip I use all the time but people may not be aware - @github maintains a list of gitignores (with 161k ⭐️!) for every single language and you can clone them into your project with a oneliner: npx gitignore <language> just in case someone here doesnt know, now you do

@wesbos Emergency bypass on phone calls but also rely primarily on our app to send emergency bypass push notifications (we build an on-call and incident management platform, so being on call is also a great dogfooding exercise!).

Postmark was down for 9.5 hours because of an expired SSL cert, and didn't jump on it for 4 hours into the outage - maybe because they were sleeping? For those who are on-call / do pager duty for systems, do you get woken up by your phone? How do you have it setup?

After over a year here, it's still insane to me that I can be in reasonably central London, and have one bar of 4G and be unable to load a website.

I find that defaulting to easily copied code forces you to write more readable code, and ultimately lets you move faster as you don't need to spend time planning an abstraction and considering all possible future uses.

This doesn't mean we have no reusable components either, we have loads! But it means we won't default to abstracting everything. Build the abstraction once you have a pattern, rather than trying to build the pattern in advance.

One of the things I love about how we think about code at @incident_io is precisely this. A lot of the time, we try to write copy-pasteable code, accepting that not every use case is the same, instead of trying to squeeze divergent behaviour into a single component/function

@r0ryma We just need to rewrite all the world's software in the latest language every 5 years

“Can you believe that POSIX has time_t, struct timeval, and struct timespec!!!!! This is USELESS and written by IDIOTS”

This is week 2 of Java stuff - so, so tired of this type of baiting

And of course impossible to talk about observability without a shoutout to @martyhambert who did an excellent job alongside @lawrjones building out and then writing about our observability strategy, probably one of my top 3 reads of this year. incident.io/hubs/building-…

I absolutely *love* our observability setup at @incident_io. Makes it so easy to track down performance problems, and makes it extremely visible when it's fixed, like the work @r0ryma did today 🔥

Which companies have you worked for that cared deeply about INTERNAL Developer experience? I see @monzo and @incident_io blog in this space - who else is doing great work here?

Our customers count on us to sound the alarm when their systems go sideways—so keeping our on-call service up and running isn’t just important; it’s non-negotiable 💯 To nail the reliability our customers need, we lean on some serious observability (or as the cool kids say, #o11y) to keep things running smoothly. Read all about it in our latest blog post 👀 ⬇️

I'm a massive proponent of remote work, but that doesn't mean wfh is *necessarily* good for the business. Structured correctly, managed correctly, and with the right tools available, it can be as good for business and bring other benefits, but it's not an easy thing to do!

"WFH is faster for IC work but slower for team work" 💯 This entire thread is really good, but that in particular.

Me 10 years ago could only dream of a world where people as forgetful as myself don't have to worry about forgetting to charge things.

It's wild to me how quickly things charge nowadays. My AirPods died on my run, and when I got back I forgot to put them in the case. As I was about to leave for the shop, I put them in the case. 10% by the time I had my shoes tied. 19% by the time I'd taken the lift down 🤯

Our on-call team has spent some time the last couple weeks making things just feel nicer overall, and I'm so proud of the work we ship every week 😍 incident.io/changelog/easi…