Friendgineers: Are you letting low priority work hold higher priority work hostage? If you are, are you doing it on purpose, or by mistake?
Friendgineers: Are you letting low priority work hold higher priority work hostage? If you are, are you doing it on purpose, or by mistake?
"Parallel Change" is one of my main go-to moves when refactoring, as it allows *me* to choose which tests (and code) to "break", instead of breaking a whole bunch all at once.
Basically, allows me to apply MMMS(S)S (h/t GeePawHill) by letting me take small (safe) steps to the new world.
One of the worst well-sounded advice in #SWE I totally abore is "Don't upgrade third parties unless it's absolutely necessary." When it will become necessary, that upgrade will likely be very painful. You just don't want to be in this position.
Like everything in software, frequent regular small steps are better than large sporadic jump.