Not a bad list for only six years on the job.

Most everything is subject to endless debate, but two things I find true after over thirty years doing this:

1. If your software doesn’t solve a real problem that real people have, no matter how well-written it may be, it isn’t interesting. Real problems include exercises that help you learn how to build software, and many games, but not 90% of the stuff launched on ProductHunt (looking at you, “Squat-O-Meter”).

2. Don’t just reflect on what went wrong in retrospectives: Celebrate what went right, too. That’s not a waste of time. Ignoring a team’s successes is just as damaging long-term as ignoring a team’s dysfunctions.