2 ms·
Interesting. So, taking a widget with CSS styling full of negative margins and redundant <div>'s and "!important"'s and font-sizes which overwrite each other fi
by crazygringo 15y ago
Interesting. So, taking a widget with CSS styling full of negative margins and redundant <div>'s and "!important"'s and font-sizes which overwrite each other five times... And cleaning it up so that each element and rule does exactly what it should be designed to do, in 1/5 of the number of CSS rules, and is now easily added to, but looks exactly the same in the end...
If that's not called refactoring, what is it supposed to be called? I would hate to use terms like "cleaning up code" or "improving code" because they're so horribly vague (they could be about merely changing tabs to spaces, or include adding whole new features).
Suggestions?
- gfodor 15y agoHonestly in that example I think you're probably safely within the classic definition, since its just a gap in tooling that makes it you can't make those types of transformations automatically in baby steps. Here's an example of someone using it wrong: "We are going to refactor the API call to have 5 parameters instead of 4." The word they are looking for here is "change" or "extend", and they're falling back on "refactor" since they think it makes them sound smarter.
- crazygringo 15y agoOK, now I get how people misuse it, I totally agree :)