I beg to differ. It is paramount to create code which is as clean as possible when developing, but once it's merged it should be changed only via tests and small steps. Or you could just accept chaos and live with it.
Hi Alain! You are totally right... But my point of this post is to tell people to keep learning. You can try above points only on a small project or your side project. Obviously big projects require testing.
Code refactoring might generate some bugs but that's exactly the point of learning. I hope you understand my point now.
Have a good day :)
I understand and embrace it actually. But I felt like the post encouraged people to break things in general, instead of breaking their own things which is actually learning for me
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I beg to differ. It is paramount to create code which is as clean as possible when developing, but once it's merged it should be changed only via tests and small steps. Or you could just accept chaos and live with it.
Hi Alain! You are totally right... But my point of this post is to tell people to keep learning. You can try above points only on a small project or your side project. Obviously big projects require testing.
Code refactoring might generate some bugs but that's exactly the point of learning. I hope you understand my point now.
Have a good day :)
I understand and embrace it actually. But I felt like the post encouraged people to break things in general, instead of breaking their own things which is actually learning for me