3 ms·
> I mean honestly you sound like a pretty difficult person to work with. I wonder if this, rather than job hopping, is what’s limiting your upward mobility. It’
by to11mtm 4y ago
> I mean honestly you sound like a pretty difficult person to work with. I wonder if this, rather than job hopping, is what’s limiting your upward mobility. It’s important to be able to learn how to work with things that aren’t perfect, and how to go about making them better or more tolerable.
It could go either way for GP. I've seen people that bounced from place to place before finding a 'happy spot'...
In smaller shops it is easy to either be non-insulated from general corporate culture (which can be far better/worse than IT, often worse in smaller orgs) or just have to work with 'that guy' too much.
Large orgs with a good strategy will often try to fit a candidate to a team. Sometimes that means interviews with multiple teams. Sometimes that might mean a group interview with leaders (Yes, this leans on the leader more, so risk might go up.)
Devil's advocate; I have -some- empathy when it comes to terraform infrastructures that are so rigid you are -forced- to deploy thing 1 to an environment, then update thing 2 with some token/IAM you got back from deploying thing 1... A worst of both worlds situation I have encountered (or an analogue of) more than once.
> It’s impossible for everything to be 100% perfect even if you run everything, because you’ll have to deal with your own mistakes from when you lacked context or experience. “Dealing with bullshit” is part of the job, no matter how you slice it.
One more DA: There's bullshit on the level of (1) 'fill out a Capex/Opex Timesheet', (2)'do this task that you know you could do differently now and not have to refactor 1-6 months later, but I want it -this- way', and (3) 'hey we just finished standup and we have a meeting in 10 minutes, I said you were the SME of %ThingYouhaveSecondLeastExperienceOnComparedToTeam% and would help answer questions' or 'hey you didn't invite a BA to an engineer-only meeting. I'm going to invite them anyway and talk to you about it in a passive aggressive tone while you are outside'.
I've done all of the above. I don't mind 2 overall, my answer to 1 is a teeth-grit 'Is there a column to track the time I'm doing the timesheet', 3 is an obvious power-play or sign of toxic corporate culture.
I regret the time I didn't leave over #3. I don't regret the time I did.
- mplanchard 4y agoOh yeah no question! Things can always be bad enough or the bullshit high enough to be worth leaving, and maybe that’s what GP was talking about. I also hopped around a bit between longer term jobs to find something that fit, and I don’t think there’s anything wrong with that. But I think the perspectives of “I won’t put up with anything I don’t like,” and “I refuse to learn anything I don’t enjoy” are pretty toxic ones for a healthy workplace. I’m currently at my favorite job I’ve ever had in my career: I have autonomy, ownership, smart coworkers, great leadership, and a product I largely built and enjoy working on. But there’s still plenty of bullshit! There’s some that predates me, there’s some that is too far outside my sphere of control for me to bother with, and there’s some that I’ve created accidentally. Living with it and trying to keep the level of bullshit tolerable is an important skill in and of itself I think. Tricky to know when it’s too much and it’s time to leave, but you’ll never know if you never try to stick it out for a bit at least once.