frizzle112

4 ms·

1. 1.▲
   by frizzle112 5y ago

   I think it depends on the complexity of what you're building. If it's something very novel or something that requires a lot of domain or technical expertise, then you might need a principal engineer to be the point person to figur
2. 2.▲
   by frizzle112 5y ago

   Author describes a classic tragedy of the commons situation - many reap the benefits but there's little incentive to invest in OSS. Analysis from there is weak. The incentives I think fairly clearly lead to major underinvestment in ope
3. 3.▲
   by frizzle112 5y ago

   Basing the argument on single company stock reliably going up is a big mistake, but I do think the longer-dated stock awards are advantageous to many employees because they're effectively an employee option - every month/quarter&#
4. 4.▲
   by frizzle112 5y ago

   I think it all comes down to judgement and there are definitely ways people can write code in their individual style without hurting maintainability. That said, maintaining a codebase where there is a lot of variation in idioms, style and f