French software engineer with 15 year experience on 3D data visualisation and processing. Lots of C++, and switch to Unity recently.
I like when it run fast 😉
The "worst" developers I worked with were so concerned about making the perfect design they end up doing nothing. Clean code is important, but if your code is so clean it never end up to production because you always find something to improve before merging it, it is just useless.
Good point. There's a balance between getting shit done and writing clean code. Personally I struggle with this sometimes when I see some code in desperate need od refactoring.
French software engineer with 15 year experience on 3D data visualisation and processing. Lots of C++, and switch to Unity recently.
I like when it run fast 😉
Yes, me too. In this case, I generally timebox the refactoring effort. I start by making dirty working code and then iterate until the end of initial estimation. This avoid overdesigning a priori, at worst I can at least ship something to production, at best I'm happy with the code I've done before the end of the time I've allowed to myself.
Getting shit done.
The "worst" developers I worked with were so concerned about making the perfect design they end up doing nothing. Clean code is important, but if your code is so clean it never end up to production because you always find something to improve before merging it, it is just useless.
Good point. There's a balance between getting shit done and writing clean code. Personally I struggle with this sometimes when I see some code in desperate need od refactoring.
Yes, me too. In this case, I generally timebox the refactoring effort. I start by making dirty working code and then iterate until the end of initial estimation. This avoid overdesigning a priori, at worst I can at least ship something to production, at best I'm happy with the code I've done before the end of the time I've allowed to myself.
I like that strategy. We're getting paid to deliver value and your strategy priorities just that!