Good companies wouldn’t fire someone for this because:
There should be processes in place to prevent this, or recover from this, anyway. It’s a team/department failure and you would just be the straw that broke the camel’s back.
They now know you’ve experienced this and will hopefully know to never do it again. Bringing in someone else could just reintroduce the issue.
Yeah that’s what I thought too. Needs a hundred more mouths filled with sharp teeth. All screaming at once in a shattering howl that will darken your dreams for decades.
And eyes, eyes everywhere. Rolling in pain, or the deeper ecstasy of madness.
That is when you should have gone to sleep by now, but you just want to figure this out first, and of course it feels impossible because youaree far too tired to think
Or you mistimed the Balmer Peak managed to do an ungodly amount of progress, forgot to comment in any meaningful way, and the next day try to go through all the changes you did and figure out what the Fuck your were on about, and how this thing works when it seems it really shouldn’t.
Actually there’s also the breaking of the psychological state of Flow, which is the mental state of total focus and maximum productivity, which takes about 15 minutes to get to.
Years ago when I had to work as a programmer from the Trading Floor of a major Investment Bank (think Fishmongers’ Market but with Financial Assets) I bought some noise reduction earphones and have used those kind of things ever since as they really cut down on distractions and it mainly works.
It even cuts down on the “can you help me for a second” thing because other people actually have to get up and move to were you are to get your attention (as you can’t hear them unless they shout), so the zero-effort choice of just calling you from their seat to help them isn’t there anymore and one thingI learned pretty early in my career is that in the absence of a zero-effort help path through you for their problems, your colleagues will actually try to first solve their problems themselves and only come to you if they’re really stuck, whilst if you’re the least effort path to having their problems solve most will just default to breaking your focus and using your time to have their problem solved.
There’s a video somewhere by someone… Returning a blank document instead of an error code is sometimes a QoS decision. Clients won’t make a new request without the user intervention, so whatever resource that’s bottlenecked has time to catch up
programmerhumor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.