Hi SDE, am wondering how you deal with the senior leadership ppls that solves or work during their free time to solve anything that a simple engineer like me trying to solve. To be more clear the current way am doing things am trying to mesure and analyze what’s going on with the legacy stack (Very painfully process) and a soon I found something that need to be fixed the smart very very smart architect will slap some code together and ask you to test if it solve the problem. I really don’t want offense them but I wanna avoid such issues in the future.
He is not smart very smart. He is unprofessional. What you need to do is 1:1 with your manager. Ask him he trust you do deliver the tasks assigned to you. If he does, tell him that you need to be allowed to do your job. You welcome code review by more senor people, but not some code injections. If the manager does not trust you, ask what training do you need to be ready to do the job.
Just say in reviews that "I worked as a team with x y z senior engineer to solve business problem a b c." Take credit for their work just like they take credit for yours! You were after all working on the same problem and ultimately it got solved for the business. I struggled with this before too; I called it the too many cooks in the kitchen problem. I learned that it is a good sign when seniors swoop in because it means you are working on high priority stuff. Take credit for your (plural) work and soon enough you'll get promoted.
The actual problem I am going through is that I love doing the last mile ‘write code’ thus I feel like they are taking the pleasure out of me.
I did that when I just started managing people. It was painful to review some juniors’ code and ask them to do it again while I can fix it easily. I later come to the realization that they will never learn and deliver something even worse because they thought I’ll fix it anyway. Talk to them if they don’t have ill intentions.
Talk to management so they can let you go for being redundant
As a pretty senior SWE, part of my responsibilities include saving overall Dev time by using my experience. If a junior engineer is faffing around for days or weeks when there's a simple solution, I'd be shirking my responsibility if I don't point them in the right direction. I get paid a lot because of my wisdom and experience. You should definitely talk to this person and your manager. You may be missing some important pieces of the puzzle. Or the guy you're talking could just be a dick. But try to assume good intent. Besides, pissing off senior people is a bad career move.
I liked your thought process. @OP, You need to understand the role of Seniors. They are there for directions and help in moving the team, resolving ambiguities, getting things done timely, maintaining quality. Learn from seniors, from their experiences. I do believe on my teammates' abilities but i ensure that i help my team in any way i can to move forward. Assuming the +ive intent will bring in a lot of change, how you perceive and take such things
I am all in for guidance and help from very smart people notice am saying smart because sometimes less experience team members can play that role to. But this isn’t the case. As I said currently the goal is to understand this piece of code we inherited and harness it with Performence analytics to enhance it. But the problem with those high level architect is that as soon you single an issue to be solved they go and solved it without any notice all you know is that you get a patch to apply and test FYI those patches it is something I am sure that I can get them done my self. I guess the problem is those very expensive architect they get to do whatever the feel like doing... now the question is how you know if this person is open to talk about it?
I'm guessing you are moving too slow and they are getting frustrated.
Probably true coming from amazon. This has happened to me in past work places and I didn’t appreciate it. I felt micromanaged by my own team members.
I don’t think so as I said we have inherited this legacy big chunky code that nobody knows what is going on with it. Am spending all my time dicing it and analyzing it to build list of things to be fixed, the only reason why am not fixing stuff yet is because I believe we need to go through this stuff all the way instead of patching it and feeding the beast. To be clear the code that this 25plus architect wrote is something that any junior Dev can manage to write. Thus I don’t think he is moving faster ...
Challenge for a penis fight and show who's the boss 🚬😎
yeah that is utter bs. senior my ass. he is not fulfilling his required duty of mentoring. talk to mgr in 1:1. note both aspects. depriving you of accomplishment and failing to mentor.
It sounds like your boss is doing it. If that's the case your best bet is to just accept it look for a new boss.
I sometimes do this to help the team meet tight deadlines and I would expect them to take credit for that work. It's nothing personal or unprofessional
Tech Industry
Yesterday
1346
In what plane of existence do kids make sense at all?
Tech Industry
Yesterday
632
Always Keep Applying
India
Yesterday
3037
Life as an Indian is absolute hell
Tech Industry
Yesterday
2458
Googlers entered Sundar’s office in protest and threatened to stay
Tech Industry
Yesterday
4197
Tesla Interviewer Who Rejected Me Got Laid Off 🎉🎉🎉
talk to your management that you are getting eclipsed, and while you appreciate their help, you yourself need the scope and time to grow. depending on the personality of the senior engineer, talk to them as well.