2 ms·

Sometimes it seems that we're over focused on efficiency as opposed to effectiveness. And I get it, because it's very hard to "be both". You can either spend yo

Sometimes it seems that we're over focused on efficiency as opposed to effectiveness. And I get it, because it's very hard to "be both". You can either spend your day coding away solving problems or you can spend your day discussing with people figuring out what the problem is. Both pursuits have clear failure modes; you can spend a lot of time trying to understand the problem better without really getting anywhere and you can spend a lot of time solving the wrong problem. How do you know when you have the right balance? 50/50?

cj 2y ago
> How do you know when you have the right balance? Find the right balance by understanding the needs of the whole business, the needs of your department, and the needs of your specific team, and your manager’s expectations of you. Then balance all that with the work assigned to you, deadlines, etc. And then align your day to day work with what the business is telling you is most important. (This is also how average engineers can put themselves in positions to be promoted ahead of “rockstar engineers”. Companies promote and elevate employees who have the most positive impact on the business, not people who have the most impact on the codebase)