#SEV1
SEV1 ALERT: TOUCH MY BUTT TO ACKNOWLEDGE 🚨🚨🚨
November 10, 2024 at 12:02 PM
if you’ve never been part of a sev1 response team on a Friday night you’re not allowed to post about vibe coding on LinkedIn
March 15, 2025 at 2:30 PM
A máme tu víkendovou Sev1 u zákazníka a všechno běží podle obvyklého schématu 😎
October 18, 2025 at 3:52 PM
lol its just like some kind of sev1 issue in unity/steamdeck in a simple empty scene cool cool cool
May 23, 2025 at 10:18 PM
Me, every couple hours: why did I open bsky id rather be in sev1 incidents at work all day.
March 11, 2025 at 9:58 PM
What it’s like to work at Freeman & Forrest:

“Why don’t we have this emoji in Slack?”

“Hang on, this is a SEV1 emoji emergency.”
December 11, 2024 at 8:05 PM
(And, importantly, they are fucking killing it on the sev0 issues, and even some of the sev1 ones. The only really major sev1 that hasn't been dealt with yet is the impersonation problem, and it's actually 12 complex problems in a single sev1 trenchcoat and they're plugging away at most of them.)
December 8, 2024 at 8:17 PM
currently ass deep in the caves of qud Bug Mines working on research around a container contents 'pooledobject' serialization bug that's our only outstanding 1.0 sev1 issue
October 21, 2024 at 8:36 PM
Man, talk about P1 sev1 incident
Man, this F-35 crash report sounds like the pilot was flying a Tesla
August 27, 2025 at 7:42 PM
every company incident review has one dumbass memelord that just posts stupid jokes about the sev1 that's being reviewed on the call

at segment, that's me
November 21, 2024 at 5:16 PM
If you work in tech, particularly on the backend, data, and/or infrastructure sides, approximately how often in a week does your org experience Sev0 or Sev1 incidents?
May 23, 2026 at 3:59 PM
Sev1 incident 🤯
January 29, 2026 at 11:45 AM
I
Want
To
See
A team
Vibe
Code
Their
Way
Out
Of
A
Sev1
June 8, 2025 at 5:02 AM
guys we fixed the aws console

1. open cloud shell
2. npx opencode-ai
3. it already is authed with aws + will pickup bedrock models
4. ask it to do everything aws
5. cause a sev1 incident
March 22, 2026 at 12:39 AM
watching the SEV1 from home on my day off
a baby is laying on a couch with his hands behind his head and wearing a tom jerry shirt .
ALT: a baby is laying on a couch with his hands behind his head and wearing a tom jerry shirt .
media.tenor.com
October 20, 2025 at 3:59 PM
Spent most of the day on a sev1 issue on call. Now....

Kendrick.
November 22, 2024 at 7:39 PM
said "We got SEV1's at home, y'all come eat!"
June 29, 2026 at 10:30 PM
Welcome to SEV1 hours.
October 20, 2025 at 2:54 PM
it's not even really a sev1 showstopper because you can mouse over or touch the screen to restore input focus but it's annoying, and I definitely need to fix it pre-console
December 12, 2024 at 8:26 PM
Die Arbeiten auf der #Stammstrecke sind abgeschlossen ✅
Ab sofort können die S-Bahnen die #Stammstrecke wieder befahren ✅
Die Linien #S1 bis #S6, #S60 verkehren heute im 30 Min. Takt ✅
Der #SEV1 wird eingestellt ❌
🚧 #Drandenken 🚧

Die #Stammstrecke wird bis einschließlich 11. September modernisiert. 🏗️

🚌 #SEV1 fährt zwischen #StuttgartHbf, Arnulf-Klett-Platz und #Vaihingen.

Alle Infos dazu hier 👉 www.stammstrecke.info

#Stammstreckensperrung2026 #Stuttgart
September 12, 2026 at 3:16 AM
put it in the register, when i really do it this time generate an incident ticket as sev1 and escalate to appropriate teams
August 12, 2026 at 12:52 PM
⚠️ Am 26.07. von 6 bis 20 Uhr, kommt es beim #SEV1 zu Haltestellenänderungen:

Während des #CSD in #Stuttgart, können die Haltestellen #Feuersee und #Wilhelmsbau (#Stadtmitte) nicht angefahren werden.

In Richtung #Hauptbahnhof, hält der #SEV1 stattdessen an der #Marienstraße.
July 25, 2025 at 5:43 PM
Some thoughts I had for rating incidents on more than just severity:

surfingcomplexity.blog/2025/12/22/a...
Another way to rate incidents
Every organization I’m aware of that does incident management has some sort of severity rating system. The highest severity is often referred to as either a SEV1 or a SEV0 depending on the or…
surfingcomplexity.blog
December 23, 2025 at 5:08 AM