xahteiwi,
@xahteiwi@mastodon.social avatar

Hot take: major rewrites of large parts of a a complex codebase are almost always a mistake.

icing,
@icing@chaos.social avatar

@xahteiwi Let me add: "if you do not have enough test cases nailing down the expected behaviour."

And: "if your rewrite will not allow existing tests to run, it is not a rewrite."

xahteiwi,
@xahteiwi@mastodon.social avatar
mdione,
@mdione@en.osm.town avatar

@xahteiwi even with tests? but yeah, big gulps means you choke.

xahteiwi,
@xahteiwi@mastodon.social avatar

@mdione I've not come across a test suite that fully covers functionality, performance, and UX, and a project team that considers a regression in any of those a bug that needs fixing.

hikhvar,
@hikhvar@norden.social avatar

@mdione @xahteiwi Most code bases have thorough unit tests and very few integration tests. Guest what kind of tests you throw out the window with a major rewrite...

xahteiwi,
@xahteiwi@mastodon.social avatar

@hikhvar This, and also: even if all your unit and integrations keep passing throughout the rewrite, all that effort is for naught if the rewrite just does not make sense.

“There is surely nothing quite so useless as doing with great efficiency what should not be done at all.” — Peter Drucker, 1963

@mdione

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • mdbf
  • DreamBathrooms
  • thenastyranch
  • ngwrru68w68
  • tacticalgear
  • magazineikmin
  • Youngstown
  • khanakhh
  • rosin
  • slotface
  • InstantRegret
  • everett
  • kavyap
  • cubers
  • megavids
  • GTA5RPClips
  • cisconetworking
  • modclub
  • ethstaker
  • osvaldo12
  • Durango
  • normalnudes
  • tester
  • provamag3
  • Leos
  • anitta
  • JUstTest
  • lostlight
  • All magazines