paprikati

3 ms·

1.
Tracking developer build times to decide if the M3 MacBook is worth upgrading(incident.io)
653 points by paprikati 3y ago|408 comments
2.
by paprikati 5y ago
Author here Being on-call is hard, and letting your pager load get out of control really sucks. We ran a short project to reduce our pager load, and found some good, low-hanging fruit to reduce our pager load while still being confident we&
3.
Write-up of a project to reduce pager load(incident.io)
2 points by paprikati 5y ago|1 comments
4.
by paprikati 5y ago
Hey - author here. Would love to hear what other folks do to start projects - ours is definitely a work in progress!
5.
Kicking off projects at a small startup(incident.io)
1 points by paprikati 5y ago|1 comments
6.
by paprikati 5y ago
Hey y'all, author here. I've had the luck to see some great incident responses, and tried to capture the most important cultural things that created those foundations. Would love to chat if you have any comments
7.
Three pillars of great incident response: clarity, transparency and calm(incident.io)
1 points by paprikati 5y ago|1 comments
8.
by paprikati 5y ago
Hey! I'm the author of the post. I changed career from consulting into engineering, and found incidents a super useful way to level up as an engineer. Now working at a super small startup focussing on incidents - hope y'all find t
9.
How to break a monolith: part 1(paprikati.github.io)
3 points by paprikati 5y ago|0 comments
10.
by paprikati 5y ago
Author here, and keen to discuss anything about the content :)