4 ms·
Pretty low-quality flaming post. Basically "battle of the word definitions". Refactoring is observably the best way to get to know someone's code. Refactoring
by pdimitar 6y ago
Pretty low-quality flaming post. Basically "battle of the word definitions".
Refactoring is observably the best way to get to know someone's code. Refactoring doesn't have to actually change behaviour; in fact, the word itself means "improving the code without changing its behaviour".
Not seeing any value in this post outside of "I disagree with some words, let's use others".
- Cthulhu_ 6y agoThis is what I've caught myself doing; instead of reading and trying to understand the code, I scan it and start "fixing" it to make it my own. Writing and changing code is a lot less boring than just reading it. Focusing on details (formatting, function naming, ordering, files) seems to be a lot more "gratifying" than trying to grasp the bigger picture. I guess this is why I'll never become a senior developer / architect. Mind you, atm I don't have anyone else working on the same codebase either so it's all me.
- pdimitar 6y agoWhat's a senior developer? I had zero problems grasping a lot of bigger pictures but since I didn't care much about political and office drama I never was dubbed "senior" while working in offices. At one point I decided for myself that I am senior by the virtue of being able to quickly understand what's happening in a codebase and where the real value-add lies, plus the ability to integrate it into the bigger ecosystem of deployments that the company practices. And having a good general culture. So don't you care about "senior". :) As for the topic -- harmless refactoring is indeed the way to get to know code. This has been said by people like Martin Fowler and Kent Beck so it's not exactly baseless and isn't easily refutable by a flaming post like the OP.