by yuliyp on 1/1/24, 3:48 AM
I feel like the author of this must have installed spyware on my computer to build this scenario.
by chhopsky on 1/1/24, 4:44 AM
so this is where all the views are coming from! glad you liked it :)
by charles_f on 1/1/24, 9:56 AM
Morale of the story: if you want to make it, ignore slack, don't search by yourself, and expedite shit by altering data in prod manually.
by pomian on 1/1/24, 2:43 AM
This was actually a fun little game.
It opens a tiny window into what a whole pile of HN types seem to deal with.
Especially interesting for those of us not directly in computer development.
by nolongerthere on 1/1/24, 6:34 AM
2:00pm did a mix of safe and stupid. Still no clue what the actual issue was tho, so sounds like a regular day in the office for me.
by cpersona on 1/1/24, 5:07 AM
3:45, but I’m terrible at my job and this proves it. You should consider turning this into a testing process for interviews. I would say this is a pretty accurate proxy for my daily work in finance related work.
by tjpnz on 1/1/24, 2:26 AM
Played it like a professional and shipped at 14:30 - the bug can wait. How did the cowboys fare?
by JakeStone on 1/1/24, 8:48 AM
That was fun. Got it by 2:00, but also played a few hunches with a cowboy move here and there that may have saved time.
Still not going to convince me to respond to Slack that quickly, though.
by mantas on 1/1/24, 9:40 AM
This hits waaaaaay too close to home.
by mikewarot on 1/1/24, 6:46 AM
I got done at 3:08, but was still on time, somehow... 8)
by bbkane on 1/1/24, 2:22 PM
I want a bonus after fixing that bug
by xbar on 1/1/24, 4:53 AM
2:15, and I even tested my fix first.