Loved the post and the art. This is genuinely going to be helpful for me to share this with my colleagues and management. > From an engineer point of view, th

Loved the post and the art. This is genuinely going to be helpful for me to share this with my colleagues and management. > From an engineer point of view, this may sound trivial, but the truth is that your career depends heavily on how your manager, and their peers, perceive your impact and your work. > I have to admit my track record of convincing management about the importance of my work based on this particular idiom has been… spotty at best. I still believe in the concept, though. The above are from “diagonal contributions” but to me also apply to rake collecting. But I have to wonder, why is this the case in software engineering? We go through K-12 school being told to make the world a better place and have a positive impact. Most religious teachings impart the idea of helping others. In nearly every profession or job role from waiting tables to building houses, a common complaint is when someone doesn’t “help out” when needed. So why in software engineering is the expectation warped such that “collecting rakes” to make sure others have a better chance at successful contributions often seen as rabbit-holing, or procrastinating, or just flat out wasteful? And especially so when done diagonally across teams? Why am I expected to only own my own pieces and not improve others? And most importantly, why does it feel like my reputation and career still hinges on the quality of my work and how it interacts with others’ work, if I then feel I need to ask for forgiveness every time I collect rakes or work diagonally? Something feels culturally wrong about this.