10 Comments

I'd also add:

> Become more familiar with the business context. For Senior+ engineers, I think that it's vital not only to solve coding problems but also to solve some critical business/domain-wise ones.

Expand full comment

Great addition Petar!

So true!

Thanks for sharing

Expand full comment

I like this quote: It’s Better to Ask For Forgiveness Than Permission

Another way to put it: Tell, don't ask!

Expand full comment

It's a rule that, because the way I am, took me something time to understand and absorb to be part of my behavior.

But since then, it's a game changer, and "prerequisite" for a people willing to grow to Tech Lead+ position

Expand full comment

How do we approach this in an organization where different teams build different tools in different languages? Also, what is the right approach if the tool your company is building is simply too complex to understand KPIs? Is it me who should understand them, or should engineers and managers share more direct KPIs with you?

Expand full comment

Great questions Akos, thanks for sharing them!

It is true that, even though companies try to apply some governance to reduce the complexity of their products, still many of them are built in multiple languages.

A person willing to grow to a Staff Engineer role might master 1 or even 2 programming languages, but this person is characterized by the capacity to implement/understand software in multiple languages. So, that would be a pre-step in this ride.

About the KPIs. I know by heart that a product can be REALLY complex and having the full picture could be really challenging. However, thanks to the creation of relationships I mention in the post, a person can ask and build an important knowledge base for having a big picture.

From my vision, everybody should be aware of the KPIs, bringing ownership and caring to the employees.

Expand full comment

Thanks Marcos! KPIs should be communicated top to bottom, right?

Expand full comment

Yes indeed !

The reality of the companies though is that, many times, the message stucks in the middle and does not arrive to everyone.

There is were I see the value of the connections among people; someone will have the KPI "X" and other one the KPI "Y".

It makes things harder than they should be, but that's real life 😅

Expand full comment

Thanks! This is my first year in corporate software development, and this stuff is new to me!

Expand full comment

Of course! Happy to help! If you have further questions about this post, let me know.

If everyone else have questions, drop me a message or reply one of emails I've sent, I like to help and give value folks!

Expand full comment