What are your programming hot takes?
What are your programming hot takes?
You're viewing a single thread.
896 comments
-
Refactoring is something that should be constantly done in a code base, for every story. As soon as people get scared about changing things the codebase is on the road to being legacy.
-
Been with a lot of codebases that had no unit tests at all and everyone was afraid to change anything because the QA process could take weeks to months.
The result is you have a codebase that ages like milk.
-
Only if the code base is well tested.
Edit: always add tests when you change code that doesn’t have tests.
-
And also try to make tests that don't have to change if you refactor in future (although there are some exceptions)
-
-
Doesn't everybody agree with this? I really never thought of it as a hot take.
-
Our company motto is: "leave it cleaner than you found it"
-
Who is in the wrong? Your manager, for not giving you time to refactor? Or you for giving him the option?
-
Why do you need time to refactor? It is just part of the work you need to do and should be accounted for when doing any other work. IMO a big mistake people make is thinking refactoring is some separate thing they need permission to do. You don't, if you need to make a change in some area refactor it first to make it easier to accept your change, then add your change then refactor to clean up. This is not three separate tasks, just three steps in one task. You should be given enough time to do the whole task, not just part of it.
-
I guess I need to refactor for readability. What you just explained is the entire point of the comment I posted. Refactoring is part of the job. Don't give your manager a choice on whether or not it needs done.
-
-
-
Yes please. Many times when I add a feature I end up refactoring some of the code first to better accommodate it.
-
thank_you_michael_scott.gif
-
We used to call this ‘Code is Cheap’ at my last job - you’re spot on about the value of it
-
896 comments