78 karma · joined July 29, 2009
[ my public key: https://keybase.io/lyal; my proof: https://keybase.io/lyal/sigs/VdHswE56pyWz1sqoGanCBtmEhEJwCyScIMQ3n4DAR_U ]
Could be fascinating to highlight config/code/approach changes on each pull request. Could actually help velocity across entire teams.
Incentives and gamification are definitely there as well. We want to bonus people for doing thoughtful code review.
Completely agree re: editorconfig. Very necessary to prevent bikeshedding. We're actually building a dedicated review IDE.
Part of our roadmap is to offer open source projects code review -- not just for exposure, but to work with reviewer standards on.
We're definitely interested in security review.
The part about training for business conduct feels a bit iffy in tone from the level of detail it goes into. I bought a company in Germany a few years back, and my Canadian sensibilities certainly offended folks until I learned the rules of the local culture. Any cross border business interactions are fraught with this.
A few of my friends are currently investing/managing a company out of Ghana. Extremely low investment has yielded a great growth curve, and they're changing how sub-Saharan Africans manage their finances. They're some of the happiest investor/entrepreneurs I know.