Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
ddephor48843yI agree that you have to get shit done sometimes.
But so many "Clean Code"-rules do not generate any effort at all, but are ignored as well.
Like indenting, variable/function naming, avoiding spaghetti code, make modules do one thing, and so on.
You do not have to create a great design on every small part of the software, but make it readable und comprehensible. Remember that source code is written once but read a thousand times.
I see it every day, someone does some tiny shitty hack, because there's no time to do it right. And then this hack spreads with CTRL-c/CTRL-v virus up to the point where you cannot get rid of it without days of work. Five minues here and there can save lots of time on the long run.
CWins51423yPartly agree. My code in reusable components is cleaner and better than in code that is for one customer only.
Requirenents change every few days? What kind of software is that?? Sound more like working on prototypes instead of some production ready stuff.
Huuugo26063yIt's called Scrum
Even scrum is about 2 or 3 weeks. Requirements changing so much is another way of saying there are no requirements and doing things as they come.