6 ms·
To your point about getting software out the door. I've run into a type of developer on more than one occasion that I call "refactoring kings". Invariably, th
by mikerichards 11y ago
To your point about getting software out the door. I've run into a type of developer on more than one occasion that I call "refactoring kings". Invariably, they're on the hunt for commits and how they can make it "better". Of course any 20 lines of code has the possibility of being refactored infinitely to a better state.
That said, the post was pretty spot-on, if a little tongue-n-cheek. The trick is to know what battles to fight. I've recently come aboard a small team where the main developer is more of a DBA than "coder", so there's lots of best practices missing. But we're in a startup mode, and I don't have the time to refactor the whole damn thing. If I see something egregious, I'll fix it, but there's code battles that I'll defer for another day.
- rubyfan 11y agoI come across these types of "refactor kings" in most areas, not just on the dev front but in architecture, business process improvement, etc. "Better" seems to be like beauty (in the eye of the beholder). I have tried to change the culture I work in to be more focused on quantifying "better". This is difficult for software people especially, who cannot (or will not) make the connection between their contribution and the overall business.