3 ms·
You may be right. The developer does, objectively, write good code. Was it so much better than the old code that it was a worthwhile endeavor? That is debata
by LordGrey 4y ago
You may be right. The developer does, objectively, write good code. Was it so much better than the old code that it was a worthwhile endeavor? That is debatable. Some of it was style change, some of it was idiomatic changes. There was, as far as I know, no performance change or refactoring that eased code maintenance or anything like that.
Rather than being a "bad dev" he may be simply a "bad value" -- good, but not worth the pain.
- clintonwoo 4y agoStructural change for performance improvement or making the code less error prone are the 2 big reasons I can see for rewriting code. 3rd being if the codebase is just legacy and needs to be updated. There's nothing wrong with an experienced dev improving code structure (at the expense of working on more tickets) but it needs at least an engineering or business justification generally.