Back when I was managing at Uber, I latched onto a thinking tool that I drilled into the teams I worked with: reach the right outcomes by prioritizing the company first, your team second, and yourself third. This company/team/self framework proved itself a helpful decision-making tool, and almost always led to the “correct” outcome. It also helped me articulate why I disagreed with some of my peers’ decisions, which violated this hierarchy by placing individual or team preferences over ...| lethain.com
Multipliers make or mar engineering organizations – teams that invest in boosting the right capabilities at the right time will get more done with less. Teams that neglect these capabilities …| CodeKraft
Last time, I explained that, although estimating software project timelines is hard, you should do it anyway. With that background, I want to go into some detail and share the technique I use when I need to develop a project timeline. I don’t believe there’s a single “correct” technique; this is one system that works well for me. However, my system does have one critical characteristic that I believe any effective estimation technique should have: it captures both time and uncertainty.| jacobian.org