|
That sounds very familiar to me... I know of a guy like that, who will rapidly jump on and propose and implement half-baked "tactical" solutions to any production incident. As you say, he is valued by management, because he is very responsive, at all hours, and always has some kind of snake oil "fix" to offer for any problem, and generally maintains a bit of a "mad scientist" vibe. The issue is that, most of his "fixes" are just rearranging deck chairs, increasing timeouts, decreasing timeouts, adding memory, upgrading random libraries, etc., and he's constantly operating in "emergency mode", trampling on other people's work and priorities to get his "urgent" stuff out the door. He also just sort of throws things at the wall - "what if we change / disable X to fix this, would that break any client use cases?"... well, I dunno buddy, you are the one proposing the change, you have access to the logs, you are the genius, why is it _my_ job to evaluate your stream of half-baked ideas to separate the wheat from the chaff? Ultimately, we co-exist, and I'd even say there are things to learn from him, i.e. being responsive is important and hugely valued. Over time, I've learnt not to get sucked into his urgent, half-baked proposals to save the world, I just say look, if you think that's a good idea, go for it, do it, but... you don't get to force it down everyone's throat and pretend there is consensus, I have my own, different priorities that I am not going to drop for you. |
I’ve been on teams where I needed to be the methodical engineer who carefully built critical infrastructure and agonized over every decision. I’m currently at a small startup that hasn’t yet reached breakeven, so I’m scrambling like crazy to build things our customers and investors will pay for. That’s what this team needs.
Thank goodness for both of you. Your team would be worse for it if they lacked either.