Creating problems that can only be solved by writing software! It's a subset of the 'expert user PEBCAK' category — a term any long-term IT help desk professional will recognize immediately, even if they've never encountered it before.

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.)