DEV Community

loading...

Discussion on: Good habits, good code quality

Collapse
deozza profile image
Edenn Touitou

Heck. All the excuses you gave about quickly writing functionnal code and not bothering with code quality and sturdyness, I already heard them from my boss every 2 or 3 days.

I learnt the hard way at a precedent job with TDD, code coverage, law of Demeter, ... and here, it's all about delivering features, 500 lines of code for a function, copy paste everywhere. And everytime I want to apply and justify the need for good practices, the answer is "do a functionnal code that works, we will see later for adding sparkles to it. Don't do quality code for the sake of doing it, the feature is the priority".

Collapse
dvddpl profile image
Davide de Paolis Author

Don't do quality code for the sake of doing it, the feature is the priority
It kinda make sense, to some extent. I saw many devs literally waste weeks for refactoring useless parts of code just because they learnt a new code design pattern.. (and probably I made that mistake too in the past) but overall quality pays off over time, in productivity, and mood.