4 ms·
This post, like the one that preceded it, has its flaws. But I was impressed with the post that inspired the "folklore" suggestion: http://blog.institut-agile.
by raganwald 16y ago
This post, like the one that preceded it, has its flaws. But I was impressed with the post that inspired the "folklore" suggestion:
http://blog.institut-agile.fr/2010/11/folklore-ou-fait-scientifique-comment.html http://blog.institut-agile.fr/2010/11/folklore-ou-fait-scien...
(Note that folklore isn't necessarily wrong).
- billswift 16y agoI like Peopleware, and Larry Constantine's essays Constantine on Peopleware, especially for managers of programmers. But I think Robert Glass's Facts and Fallacies of Software Engineering might be a better recommendation for a developer.
- deleted 16y ago[deleted]
- andreyf 16y agoFrom the slashdot review [1], it seems that at least some of the "facts" Robert Class mentions fall quite solidly into the "folklore" category, e.g.: First, each Fact is stated succinctly. (For instance, Fact 1: The most important factor in software work is not the tools or techniques used by the programmers, but rather the quality of the programmers themselves.) Then the point is fleshed out more fully -- in this case, that even with all the periodic hype for some hot new methodology that promises orders of magnitude greater productivity, the quality of your programmers matters far more than anything else (and even the best new methods only offer 5-35% increases). 1. http://slashdot.org/article.pl?sid=04/08/27/1616256 http://slashdot.org/article.pl?sid=04/08/27/1616256
- Morendil 16y agoNow translated here: http://morendil.github.com/folklore.html http://morendil.github.com/folklore.html