All points here are really accurate. I have been a Software Engineer (Middle) about 1 year and from my experience you should try to take more challenging task even if you don't see how to solve it right now. You may feel stuck sometime and do not know how to proceed forward, and, it's time where you start to ask questions to your team lead or architect what they think about task on current stage and how you can move next. There you should start accumulate different point of view on task, as developer, as business person, like customer. It will help you to build more wide picture of project or development in whole. Now I have been promoted to Senior Software Engineer. Also, if talking about design and implementation, spent some time to research of existing solutions or methods to solve the problem, don't just apply it, but analyze what and how people come to this solutions. Keep learning! =)
Thanks for sharing! All these points are valid and I think you could summarize them as taking ownership. You are responsible for the project and that the cost of change stays low in the future (high quality code). You are responsible for making your team perform at the highest level (tooling, mentoring, communication). You are responsible for delivering high user value (planning, consulting, prioritizing, etc.). You are responsible for yourself (get up to speed fast after vacations or onboarding, get unstuck, etc.). Sure others do mistakes and it’s not your fault. But you own the project and you need to take responsibility. That will make you really standout. Good luck everyone! 👍
I'm on my 4th assignment with offshore teams as a TPM and UI architect. What's the best way to oversee but not overreach. I tend to suggest changes and updates as a way to communicate without sounding authoritarian. Any suggestions? Tia.
I think it's helpful if a team can agree on a set of standards - that way, you can point to the agreed rules rather than feeling like you're simply enforcing your opinion. I might also suggest daily commits/WIP pull requests to monitor progress. Also, saying things like "I might suggest..." or "Have you considered..." rather than "You need to fix this" can go a long way. As far as XP - no real thoughts. But I think remote pairing can be helpful. Hope this helps!
All points here are really accurate.
I have been a Software Engineer (Middle) about 1 year and from my experience you should try to take more challenging task even if you don't see how to solve it right now. You may feel stuck sometime and do not know how to proceed forward, and, it's time where you start to ask questions to your team lead or architect what they think about task on current stage and how you can move next. There you should start accumulate different point of view on task, as developer, as business person, like customer. It will help you to build more wide picture of project or development in whole.
Now I have been promoted to Senior Software Engineer.
Also, if talking about design and implementation, spent some time to research of existing solutions or methods to solve the problem, don't just apply it, but analyze what and how people come to this solutions.
Keep learning! =)
Nice!
Thanks for sharing! All these points are valid and I think you could summarize them as taking ownership.
You are responsible for the project and that the cost of change stays low in the future (high quality code).
You are responsible for making your team perform at the highest level (tooling, mentoring, communication).
You are responsible for delivering high user value (planning, consulting, prioritizing, etc.).
You are responsible for yourself (get up to speed fast after vacations or onboarding, get unstuck, etc.).
Sure others do mistakes and it’s not your fault. But you own the project and you need to take responsibility. That will make you really standout.
Good luck everyone! 👍
First step to becoming a senior developer: wear a Patagonia vest.
👀
Underrated knowledge. This should have 100k likes at least.
Great content Peter! Thanks for sharing your experience!!!
I will achieve this ✨manifesting✨ I will become a legendary senior developer soonest ✨
LoA
great sharing , thank you!
Good points, thanks for sharing 😊
Thanks for watching! :)
I'm on my 4th assignment with offshore teams as a TPM and UI architect. What's the best way to oversee but not overreach. I tend to suggest changes and updates as a way to communicate without sounding authoritarian. Any suggestions? Tia.
Ps please add your thoughts on Remote pairing as I'm a fan of XP since 2001 but run into push back and reluctance to adoption.
I think it's helpful if a team can agree on a set of standards - that way, you can point to the agreed rules rather than feeling like you're simply enforcing your opinion. I might also suggest daily commits/WIP pull requests to monitor progress. Also, saying things like "I might suggest..." or "Have you considered..." rather than "You need to fix this" can go a long way.
As far as XP - no real thoughts. But I think remote pairing can be helpful.
Hope this helps!
@@PeterElbaum thanks, it's hard to feel the pulse from across the world so these language barriers have to be handled carefully.
When you lose a software engineer who didn't document their work you also feel their absence.
gracias señor
🙏
I think….I might be a senior. 😂
👏there it is!