4 ms·
I don't mean contributing patches to Rails, I mean writing Rails. Or contributing features to projects that are viewed as bit more hard-core, eg. Apache or Pyt
by nostrademons 16y ago
I don't mean contributing patches to Rails, I mean writing Rails. Or contributing features to projects that are viewed as bit more hard-core, eg. Apache or Python, though even there you're often better-off starting a new project than contributing to an existing one.
There seems to be a general cognitive bias in the programming world against maintenance work, which strikes me as a bit dumb because it's both harder and more important than starting new projects. But as long as it exists, I'm going to exploit it, and do high-visibility but useless projects like port Arc to JavaScript or rewrite Tetris in 3 hours instead of contributing patches to JQuery.
- barry-cotter 16y ago>> There seems to be a general cognitive bias in the programming world against maintenance work, which strikes me as a bit dumb because it's both harder and more important than starting new projects. This is not unique to the programming world. Starting something and finishing it looks a lot more impressive almost evrywhere than making something that exis´ts better. Just think how much more impressive founding yet another non-profit looks on ones cv compared to doubling the projects of an existing one.