> Yes, but it's not really a satisfying work experience!
I dunno, I like it when people come to me with problems they need solved. You get to work with a stimulating variety of issues, get to meet more of your coworkers and earn their gratitude, and there's a real satisfaction in knowing that people see you as a capable problem-solver. I'd actually really enjoy having a job as "the guy who makes the tools work better for everyone else."
> Yes, but it's not really a satisfying work experience!
I think that comes down to your disposition. I find meetings and scope negotiation very energy draining but one in one problem solving doesn’t tax me that much. As long as I’m not spinning plates when you come up to me I can usually stop what I’m doing and get back to it later.
Hard to solve problems often conceal architectural problems or irreversible decisions and I’d rather be involved long before it becomes intractable.
Indeed, solving problems is my favorite part of my job; the issue is more along the lines of not being able to spend more time improving things, and wasting time fixing other people's git mistakes, carrying boxes of server components up 5 flights of stairs because all the elevators are broken, sitting through meetings re-explaining the same things as 6 months ago, because no one takes notes.
I dunno, I like it when people come to me with problems they need solved. You get to work with a stimulating variety of issues, get to meet more of your coworkers and earn their gratitude, and there's a real satisfaction in knowing that people see you as a capable problem-solver. I'd actually really enjoy having a job as "the guy who makes the tools work better for everyone else."