IT jobs explained with a broken lightbulb
-
found in my archives
wrote on last edited by [email protected]Climate Scientists:
- The lightbulb is broken, and there's reason to believe that the ceiling might cave in
- Offers advice on how to fix the contacts, or to replace the bulb entirely, or put up struts to support the ceiling in an impassioned plea to the higher ups.
- CTO is committed already to candles, CFO wants to wait and see what happens, and CEO labels it as a marketing problem.
-
Product Manager: Make a step by step guide of how they think the lightbulb is going to be fixed without explicitly mentioning the 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? 🥺)
-
found in my archives
Dwh:
- the light bulb is broken.
- asks marketing what kind they want, after a week they answer halogen.
- dwh then asks backend who says halogen is deprecated, and says only LED is available, due to fire risks.
- in the meantime, marketing got tired of waiting, orders a halogen bulb and doesn't tell dwh, and manages to install it, even though it's the wrong socket.
- The light flickers and could break any second, but marketing is happy
-
And then complain that the light bulb wasn't fixed in the time that a different team projected on the L1 from 3 years ago.
-
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? 🥺)
And after all that it is discovered that it was the wrong solution all along because the requirements were poorly specified, so the process must be started all over again
-
And after all that it is discovered that it was the wrong solution all along because the requirements were poorly specified, so the process must be started all over again
The circular justification of a PM's job, see how much value they add!?
-
The circular justification of a PM's job, see how much value they add!?
So something I don't understand is the logic behind my job. I'm a software engineer, that effort makes sense to me to develop and solution and configure.
But I've been given a product owner role. And then I have a product manager I work with who isn't technical.
I really don't feel like I do much other than stress out
-
So something I don't understand is the logic behind my job. I'm a software engineer, that effort makes sense to me to develop and solution and configure.
But I've been given a product owner role. And then I have a product manager I work with who isn't technical.
I really don't feel like I do much other than stress out
Tbf that seems like the proper response to me.:-)
Normal human ways of thinking go like: however you do it, so long as the job gets done it's fine!
️PM thinking: even if nothing ever gets done, so long as
I collect a salarywe continue to have 3 hours of meetings most days every week, it's all good!
🤯Also, afaik, the conflict between the PO and PM roles is somehow literally the point? You get blamed if the tasks don't get done, while the PM ensures that endless reports get generated - I doubt the vast most of which are ever read, and I know that I for one can never find one of those later, in part bc there are so many of them and they encompass everything else into them as well (Jira tickets, Slack messages, hundreds of emails per day mostly saying "this Jira ticket or that Confluence page has been edited", the former of which for the life of me I cannot figure out how to turn off!).
So... not only I but we all feel your pain! Otoh, that seems one of the first job roles that will soon be replaced by AI?
-
And then complain that the light bulb wasn't fixed in the time that a different team projected on the L1 from 3 years ago.
Exactly. Also, prediction they're referencing from 3 years ago was to build a lemonade stand.
-
Tbf that seems like the proper response to me.:-)
Normal human ways of thinking go like: however you do it, so long as the job gets done it's fine!
️PM thinking: even if nothing ever gets done, so long as
I collect a salarywe continue to have 3 hours of meetings most days every week, it's all good!🤯Also, afaik, the conflict between the PO and PM roles is somehow literally the point? You get blamed if the tasks don't get done, while the PM ensures that endless reports get generated - I doubt the vast most of which are ever read, and I know that I for one can never find one of those later, in part bc there are so many of them and they encompass everything else into them as well (Jira tickets, Slack messages, hundreds of emails per day mostly saying "this Jira ticket or that Confluence page has been edited", the former of which for the life of me I cannot figure out how to turn off!).
So... not only I but we all feel your pain! Otoh, that seems one of the first job roles that will soon be replaced by AI?
I have a feeling AI won't take my role, AI will force me to take ownership of more products. I worry greatly about that.
-
I’d say I feel seen, but it’s really dark in here.
Who said that?
-
Who said that?
[clicks light switch off and on repeatedly]
Welp, I guess we’re closed for the week.
-
Climate Scientists:
- The lightbulb is broken, and there's reason to believe that the ceiling might cave in
- Offers advice on how to fix the contacts, or to replace the bulb entirely, or put up struts to support the ceiling in an impassioned plea to the higher ups.
- CTO is committed already to candles, CFO wants to wait and see what happens, and CEO labels it as a marketing problem.
I came here to laugh, not to cry!
-
found in my archives
Support would be like
User reports lightbulb is broken.
Tries to talk user through troubleshooting.
Problem resolved by turning on light. -
I accidentally read the second to last comic as "hands out fleshlights". Would also work.
"by toggl Goon Squad"
-
Support would be like
User reports lightbulb is broken.
Tries to talk user through troubleshooting.
Problem resolved by turning on light.User can not find switch. Guided to switch, user said switch operation is too complicated and refused further troubleshooting. Escalated.
-
Support would be like
User reports lightbulb is broken.
Tries to talk user through troubleshooting.
Problem resolved by turning on light.More like:
Use reports lightbulb is broken. Support spends an hour talking user through diagnostic tests. Determines that the lightbulb in question is a houseplant.
-
User can not find switch. Guided to switch, user said switch operation is too complicated and refused further troubleshooting. Escalated.
User is very upset. It was a broken bulb last time, so it must be a broken bulb this time. Why can't the help desk make bulbs that don't break? Bulb was fine, user was locking and unlocking the door instead of flipping the light switch.
-
found in my archives
Full stack developer:
The lightbulb is broken. Deploys a lightweight fix that involves 17 metric tons of chandeliers, stadium floodlights, sconces, and the necessary infrastructure to operate the street lights for a city of 500.000. His solution delivers a solid 100 lm of light using only 175 MW of power.
-
Full stack developer:
The lightbulb is broken. Deploys a lightweight fix that involves 17 metric tons of chandeliers, stadium floodlights, sconces, and the necessary infrastructure to operate the street lights for a city of 500.000. His solution delivers a solid 100 lm of light using only 175 MW of power.
why they are like that
