Lessons from 27 Years in Tech
I took my first job writing code about 27 years ago. That’s enough time to have led many failed projects. I’ve learned through painful experience not to commit to an ambiguous scope on someone else’s timeline but rather to engage in the tough conversations that acknowledge risk, challenge assumptions, protect the integrity of the team, and trade scope for time. I acknowledge it’s a privilege to challenge bosses. But no one thanks you for failing on their terms. And when it works, you earn trust, foster a healthier space for coworkers, and stand a chance at delivering a meaningful outcome.