Arsonists drawn to firefighting field. People with mental health issues becoming therapists. People with eating disorders becoming dietitians.
I'm trying to figure out what pathology I'm hiding as a software engineer.
I'm trying to figure out what pathology I'm hiding as a software engineer.
Experts create the worst problems and when experts bring the help desk those worst problems, sometimes the reply must be "You caused it, you fix it; or, we can restore your device to an IT-supported state after you backup whatever data you don't want to lose". So, what problems have you created that require you to engineer solutions for them? Did you create those problems intentionally? A lot of us do so in our 'home lab environments', and that's what they're for. But doing so intentionally at work — not accidentally — is called 'making work for yourself so you get paid by someone to fix problems you created', and that is a perfect match for 'firefighter arsonist'.
(None of this is accusation, this is just analogy-building; both 'software' and 'you' are swappably generics for any profession and any engineer, respectively.)
The software engineering job skips dealing directly emotional regulation, experiencing emotions and directly confronting others in vulnerable way or a negative way like boundaries.
Instead you are given a problem, and you can fix the problem, control the variables and see if your solution works logically and tangibly.
You cannot do this with people interactions. Emotional orbits, feelings, insecurities, needs, wants are messy overlap .. are not easily definable , and flux … software engineers may not thrive here I would guess.