4 ms·
1. Increase the Bus Factor of our main application. 2. Develop mentoring skills. 3. Start to transition away from being a full-time developer to a staff engin
by nvahalik 5y ago
1. Increase the Bus Factor of our main application.
2. Develop mentoring skills.
3. Start to transition away from being a full-time developer to a staff engineer.
4. Create a culture that is highly tolerable of risk and failure.
2-4 are not just work focused but are also family focused. So much of what we do as a family embraces comfort rather than risk-taking. We should do more of that.
- ravenstine 5y ago> 4. Create a culture that is highly tolerable of risk and failure. I'm curious; in what context? Would this be at a personal level, a team level, or something bigger?
- nvahalik 5y agoWell... In my personal/family life allowing my kids the freedom to do big things with enough oversight to ensure basic safety but giving them the freedom to try things and figure stuff out. Give them goals but force them to think through ideas, try things and take chances. I've done this a little in the past and have always been amazed at the results. Team level: not enforcing a very strict "it must be coded in this way approach" (unless it is obviously wrong). Giving people the ability to try out new ideas and building some time in for learning how not to do things. Example: if a dev takes a couple of days to build a new feature but it turns out that feature sucks, it should be OK that he tried it. Trying to be more of an encouragement to designers and allow designs—even bad ones to get some play. We might learn something along the way.