Wrong question. Most don’t like to self-promote in dev. If you did like it, you’d be in sales. Right question is ‘how do I get my contributions to be well un

Wrong question. Most don’t like to self-promote in dev. If you did like it, you’d be in sales. Right question is ‘how do I get my contributions to be well understood.’ For that, you need to emphasize numbers. Every project, every task, every epic you ship has, at its heart, the goal to improve some metric in your business. Do you understand what those metrics are? Do you understand why they are important to the business? If the answer is “no”, then you’re doing things out of order. You can’t possibly hope to get others to understand your work if you yourself don’t understand it. When you can say “I helped reduced latency by 237 ms”, that’s a good metric. Even better if you are curious enough to then connect it to the outcome - “which led to 17% longer sessions by users.” When you master the numbers, then self-promotion becomes a by product of your work. E.g., at the team meeting “I understand our goal is to increase flip flops by 10%, is that right? Well, I think we can do it because when I was on that project with Team B last year we increased flib flabs by 12%.” Summary: don’t self-promote, instead understand and communicate your impact on metrics.