You started it all wrong. First step is to tell Kiro: “Prod is down, fix now, no mistakes, take as long as you need, credits are not a problem. Don’t stop until it’s fixed”
2026-08-16 00:28:45
44
⚜️Lou⚜️ :
What if going back version reopens up a patched exploit 🧐
2026-08-16 00:30:03
10
user18644624626 :
Senior dev would also make sure the change is reverted after rollback to ensure it’s not re-released
2026-08-16 01:25:54
11
Zach M :
Oh man, feeling sick, PTO the rest of the day. Good luck fellas.
2026-08-16 16:17:15
6
Tawfik_404 :
isnt rolling back is the first step then find the root cause?
2026-08-16 00:53:32
0
RobinBanks :
whos doing this manually?
2026-08-16 03:14:56
0
lkahuwxl927 :
principal: login to prod, open vi, fix it , call it a day.
2026-08-16 12:54:41
3
Tosin FikTok :
Nice
2026-08-16 18:31:28
0
Felipe Mathias :
I’d just “Claude, system is down, fix it”
2026-08-16 19:56:01
0
Gareth Rowlands :
Dashboards first, then logs. Rollback is typically only applicable if your deployment caused the problem - and if that’s the likeliest scenario rather than your dependencies, you may want to look at that.
2026-08-16 11:04:16
1
To see more videos from user @arjay_mccandless, please go to the Tikwm
homepage.