Lessons Learned from Software Rewrites

Re:Lessons Learned from Software Rewrites by emdeha on Monday September 05, 2016 @05:18AM (#12429082)

Great article! It's interesting though, how did you convince management to remove features no one was using?

[ Parent | on HN ]

Re:Lessons Learned from Software Rewrites by di4na on Monday September 05, 2016 @09:24AM (#12430118)

From my PoV : Pull the plug and wait to see if someone yell. If noone yell... then noone need to know.

If someone yell, be sure to put your own contact proeminently everywhere. So that your management do not know. And just roll it back

[ Parent | on HN ]

Re:Lessons Learned from Software Rewrites by OpenDrapery on Tuesday September 06, 2016 @09:41AM (#12435913)

Problem with this is the feature that is used by some external actor once every 18 months. You'll pull the plug, and when 6 months go by, you'll think you're safe. Then when shit blows up, you'll have no context and spend 3 days tracking it back to the "pulled plug"

[ Parent | on HN ]

Re:Lessons Learned from Software Rewrites by tonyedgecombe on Monday September 05, 2016 @06:28AM (#12429304)

If no one was using them why do you need to convince management?

[ Parent | on HN ]

Re:Lessons Learned from Software Rewrites by emdeha on Tuesday September 06, 2016 @04:19AM (#12434378)

Because management decisions ain't always driven by logic.

The simplest reason may be attachment to the feature--the feature is of no use but the person who's invented it is scared by the possibility of removing it.

[ Parent | on HN ]

Re:Lessons Learned from Software Rewrites by akerro on Monday September 05, 2016 @08:47AM (#12429888)

Because when trying to sell the application list of features is longer, which means we know what we're doing and are able to maintain it.

[ Parent | on HN ]