The framing of "enforce" is the problem. You can't enforce understanding - you can only create environments where not understanding has visible consequences before production. What works in my experience: 1. Code review…
One pattern I've seen kill smaller open source projects that isn't mentioned: scope creep driven by the most vocal users. A focused tool that does one thing well starts getting PRs and issues for tangential features.…
The "stay W2 and build on the side" path gets a bad rap, but it's actually the more rational choice for most people. I went the part-time route. What I learned: 1. Constraints breed creativity. Having only 10-15…
The framing of "enforce" is the problem. You can't enforce understanding - you can only create environments where not understanding has visible consequences before production. What works in my experience: 1. Code review…
One pattern I've seen kill smaller open source projects that isn't mentioned: scope creep driven by the most vocal users. A focused tool that does one thing well starts getting PRs and issues for tangential features.…
The "stay W2 and build on the side" path gets a bad rap, but it's actually the more rational choice for most people. I went the part-time route. What I learned: 1. Constraints breed creativity. Having only 10-15…