Skip to main content

Senior vs Junior devs

 It is important to achieve a balance between Junior and Senior people in your team.

Recently I had to explain to someone why making class abstract is not the way to go when you need to implement a utility class.

And today I did an assessment on an implementation we need to extend to another customer. I know the business flow and use cases very well, even if I was working on a UN project for the last few months. But thrilled with the architecture I had created and how easy it is to implement and integrate another customer to the system.

The moral is to give the freedom to senior devs to design a solid system that can be extended and give them time to mentor junior people on how to get better.
Labels:

Comments

Post a Comment

Popular posts from this blog

The messy meeting

When you know there will be a messy meeting and there is nothing you can do about it, the best thing to do is to avoid it. Messy people produce messy meetings, and they take the time and the energy of everyone who is part of it. That is why instead of being part of this drama, find a better team and better meetings to invest your precious energy.
Post a Comment
Read more

New year preparations

 I stopped preparing for things since August this year. I decided to go with the flow. With no plans for the New Year, today I received an invitation to a party. Seems like not having any plan was the best plan in the end.
Post a Comment
Read more

The recovery day

 What to do once all the presents are opened? Should we just move forward with our goals? As I wrote about recovery day after flying long distance. It is important to plan a recovery day after the holidays. This is your guilty free time.
Post a Comment
Read more