IT jobs explained with a broken lightbulb
-
Woah there buddy, you can't just jump straight into the (non-)solution like that! You skipped the planning refinement! And the planning pre-refinement! And the pre-planning pre-refinement! And we'll still discuss all of this in the post-planning refinement!
(Yes, every one of these are real, distinct meetings, lasting at minimum one hour but sometimes two or more. EVERY WEEK. Kill me now please? 🥺)
Fuck me am I glad I'm out of the corporate world
-
Fuck me am I glad I'm out of the corporate world
I keep trying to escape, but I do need a paycheck so... [rolls up sleeves] back into the fray I go, once more!
-
[clicks light switch off and on repeatedly]
Welp, I guess we’re closed for the week.
That's the end user.
-
I wish users would report their problem istead of what they think is the solution.
And when they do report the problem, they should report the actual problem they had and not what they think the problem is.
So instead of eg. "my computer's been hacked!", it's actually "I saw a scary error dialog I didn't understand"
That sounds roughly related. I see ones like: excel file broken!!! Actual issue: it's dark so the computer screen is too bright and when they put sunglasses on due to the brightness, they can't read the numbers. Solution is to turn the lights on.
-
That's the end user.
no no, the end user will somehow find the exact position in which the switch starts arcing and then they'll work by the light of the fire in their walls.