554 karma · joined January 21, 2011
[ my public key: https://keybase.io/djkianoosh; my proof: https://keybase.io/djkianoosh/sigs/DSOsnLW2_8ytGA3mDk9YJbIp5y3jCYnAzjRn1B5b9C0 ]
There's likely a threshold (a 10000 hours type thing) where you've researched enough code history to value great commit messages and descriptions and docs/readmes, issue descriptions and comments etc.
But how do we impart the importance of this to the other devs around us that will make it stick? Past "war" stories?
The photography was great.
Here's the reason: managers are so spread thin that they don't want to be in 5-10 standups all morning, so they combine around organizational structures rather than product(s)/deliverable(s). Another case of the software delivery matching org structure...
Will it be possible to run this internally, as in, inside a firewall? Might be useful for enterprise customers.