>informed about boreout (the relatively unknown cousin of burnout).
Thank you for giving a word to this vague thing that I thought was unique to my situation. I worked as the solo IT guy for a small firm of about 50 people, half in house, and when I started in 1998 I was busy 40 hours per week... at the end in 2012 I'd show up and wait for things to break.
That job broke me
Ever since I'm afraid to start projects, or try things with only a few exceptions when I've been sufficiently nerd-sniped.
Wow, that sounds a lot like my job... small business, solo IT, heavy emphasis on "other tasks as needed." Some weeks it's felt like I slacked off most of the week waiting for calls to come in (though I've been keeping busy learning, documenting, and updating) while other weeks I'm so busy I barely sit down.
Over time it's been teaching me to say no to projects when they're out of scope or beyond my ability. I used to say "I'll try" to everything which led to some great learning experiences but also a lot of stress and disappointment. Still trying to find some kind of balance there.
Years ago I imagined such a thing as "Programmer in the corner syndrome". This is where you are the only person interacting with considerable complexity and fragility, and no one else in the office ever looks, or could look.
Thank you for giving a word to this vague thing that I thought was unique to my situation. I worked as the solo IT guy for a small firm of about 50 people, half in house, and when I started in 1998 I was busy 40 hours per week... at the end in 2012 I'd show up and wait for things to break.
That job broke me
Ever since I'm afraid to start projects, or try things with only a few exceptions when I've been sufficiently nerd-sniped.