3 ms·
That's the great dilemma. Either you write the actual fkin' code, or you do roundabouts all around "project management" tasks, which in itself can be seen both
by j1elo 8y ago
That's the great dilemma. Either you write the actual fkin' code, or you do roundabouts all around "project management" tasks, which in itself can be seen both as a needed means for a project's success, and as the perfect procrastination tool.
If you have 100 hours to write something and do ALL that is noted here you'll end up not shipping anything at all. I'm currently the main developer and maintainer of the Kurento project [1], and I've been working hard on all these accessory but important details because my vision coincides with that of the article's author, but at the same time they feel like a time sink which distracts from doing actual work on issues and bugs.
[1]: https://www.kurento.org https://www.kurento.org
- AstralStorm 8y agoThe main thing all these guys do is to ship the most trivial thing that will work (is better than competitors) but leave it open for improvements. Tests are written sometimes second, not first. Specifically regression only testing is pretty good and less intensive than full testing everything. But to know about regressions and problems you need reports and to do that, the software has to be shipped, in use and the report channels have to work well.