| I've felt companies would want what the post lays out: - A safe software stack - Make code understandable (industry best practices) - Focus on employee ramp up time I was confused when some companies stressed different things, and I didn't quite realize until reading this post that it might be coming from a place of fear of losing engineers. What I've seen: 1) Committees for coding standards 2) Teamwork over code ownership 3) Peer code reviews to enforce quality Sounds like these things would help increase code quality and reduce the bus factor. But I think there are some dangers. 1) Committees can mean that no individual is responsible for bad decisions 2,3) Teamwork is great if people have separate roles. Too many cooks can become a real problem otherwise. I suspect people afraid of responsibility are more likely to embrace committees and teamwork. Dickheads incapable of working with others are more likely to take ownership (or else they'd be completely unemployable). I also suspect many startups cargo cult practices that work well for giants, but are net negatives that encourage your employees to leave if you're small. Lacking ownership but getting paid super well is a better tradeoff than lacking ownership AND lacking amazing pay. |