564 karma · joined April 4, 2016
(i) Try to estimate more realistically (usually higher). Consider making the feature stable when estimating, drop the "done" and "done done" concepts. A feature is done when it's stable, reviewed and tests green.
(ii) Don't accept pull requests that lower the test coverage of our application (at least in modules that we already have coverage).
(iii) Pull a few technical debt items to the Sprint Backlog
We figured that it was easier to avoid creating more technical debt in rather than trying to retroactively fix all. I've had long discussion with people saying that we should stop for one full week and do a mass cleanup and redesign. Not sure if I fully agree.
I do care if your code is a mess if other engineers have to maintain it.
You can monetize from distributed systems; and I think this will happen more often with Blockchain, render farms and things like that.
> who on earth is going to buy, run and maintain this infrastructure?
This. As much as I love the idea of decentralization, I can't see it getting much traction because of this.
`[0-9] - Matches any digit between 0 and -`
Mistype the `9` for a `-`. :-)
Another point that I think is valuable is: "Output one line per record data"
This is useful if your CLI that has to output data to the user. Makes it easier to interface with programs like `grep`
jashkenas/coffeescript
could go easily be mislead by: jashkneas/coffescript