4 ms·
People step up at moments like this. As a Lead: When my wife had heart problems, I instantly told my team to go on auto-pilot, who would run their ceremonies,
by ilc 4y ago
People step up at moments like this.
As a Lead:
When my wife had heart problems, I instantly told my team to go on auto-pilot, who would run their ceremonies, and went to support my wife. When I got called by someone with a question that was answerable by my team, I chewed them out. This is all with 100% support from my director.
As a developer:
I'm working on a product where the product has been developed by one dev largely for many years. I'm at the 6 month mark now, and honestly, if I had to step up to support everything myself, it'd suck, but the company would keep going. Would I have to change how a few things work? Probably. But would we get our releases out: Absolutely. Usually at 6 months, I could take over most products but this one is very specialized. (Which is why I joined up. I knew the ramp was longer, and I had more growth. :) )
And that is the real story: If you want to get that "truck number" up. Get someone else into your codebase, and working. If not expect some lag while they come on-line, but that the world will keep spinning.
... Also look for people who can learn, over just raw skills in a replacement scenario. Clearly they need to know enough, but it may take you longer to find someone who can check every box, than get someone and have them ramp up to "good enough" quickly, missing a piece or two. Heck you might want 2-3 developers.. something about learning your lesson.
- aliqot 4y ago> When I got called by someone with a question that was answerable by my team, I chewed them out. Yikes. A trivial work issue is something someone might use an excuse to check on you and make sure your wife is okay and that you're alright.
- ilc 4y agohttps://www.latimes.com/opinion/op-ed/la-xpm-2013-apr-07-la-oe-0407-silk-ring-theory-20130407-story.html https://www.latimes.com/opinion/op-ed/la-xpm-2013-apr-07-la-... Understanding the above article is very important. Instinctively, we want to help. But figuring out how to, without "dumping in" is critical. If you are worried about a person in the situation like the one I was in, figure out the right way to help them. If they say don't call. Honor that. As for "chewing out" my wording was strong there for what I did. Though I'd support someone chewing out someone there. I pointed out that my team could make choice X without me, and that I'd left clear directions on who could do what. I referred them back to that person, and reaffirmed my teams choices, which either good enough or the exact choices I would have made. Yes, the person was doing what you suggested. But that's not a good thing to do. If they want to help me, not interrupting me is important, I'd also left my personal e-mail... so an e-mail was much more appropriate, and would have been received better. Also it gives me time and space to think. Which are precious in moments like that. I may not know how you can help me today.... but I may tomorrow.
- badcppdev 4y agoYou should never try and hide that fact that you care. My approach would be a text message saying something along the lines of: Hi X. Hope things are going ok. Tell us if we can do anything. Alter for cultural differences, closeness of relationship, situations where things are not going to be ok.