barcist

4 ms·

1. 1.▲
   by barcist 3y ago

   Objective measures are a good thing. Otherwise you just end up with some subjective opinions nitting bro culture even closer together.
2. 2.▲
   by barcist 3y ago

   > As a maintainer of a security-oriented open source library, the paranoia of "is this person trying to help or to exploit?" That's an excellent mind set when reviewing code, no matter security or not. But especially for s
3. 3.▲
   by barcist 3y ago

   In a corporate proprietary code base this is REALLY easy. Just commit a bug. Happens every day, everywhere. Just that normally these are mistakes. You can easily mask a deliberately inserted exploitable bug as a mistake. Make the code a bit
4. 4.▲
   by barcist 3y ago

   > potentially all your users might go with the fork That's the issue right there. Why would you care? Clearly, the maintainer is invested in having a "community". Why? They must expect something positive coming out of it,
5. 5.▲
   by barcist 3y ago

   The trick is to align the metrics with company goals. It's not easy, but not impossible either. For example, if quality is your goal, then the metric you give your devs is "number and severity of bug reports coming in from custome