DEV Community

Discussion on: 6 Productivity Myths That You Should Not Believe

Collapse
 
ghost profile image
Ghost

I think the root of all this and other myths are the fact that self knowledge is harder than following some arbitrary rules and that blanket statements don't require any thought or reflection; maybe those "successful people" habits where useful for them, doesn't mean they we be useful for everyone, maybe they weren't the benefit but the result of knowing themselves enough to know that worked for them. Maybe blindly following this myths is not the problem, maybe is something deeper, is the "blind" part, that's why so many take opinions and recommendations as laws and turn people into "gurus"; so many times we see blank statements like "those who don't do TDD aren't prefessional", "OOP is the best and only alternative", "functional is better", "OOP is the devil", "waterfall is bad, agile is good", etc. Of course, if I just follow and believe them I don't have to think, just quote someone else, that's why some figures like Bob Martin got his god-like status; why TDD has become a religion. Religion is easy, just pick one and follow, the alternative is to observe, analyze, test and repeat each time. Maybe Agile is great for this project, maybe not for the next one.

I bet some of the readers of this article will take it as gospel even tho I think it was made for the opposite. Maybe even take this fools rant as one. And dear reader, please don't follow the example of Michelangelo :)