3 ms·
This post doesn't provide any evidence or even any arguments. There are lots of different types of rewrites, and rarely does anyone find themselves in the posi
by crazygringo 3y ago
This post doesn't provide any evidence or even any arguments.
There are lots of different types of rewrites, and rarely does anyone find themselves in the position to rewrite an existing system in a way that perfectly reproduces behavior 1:1, because rewrites are often motivated by a ton of ugly features/flows that were forced as kludges, where the whole point is to improve them, along with making it vastly easier/cheaper to write new features.
And no, waterfall works just as badly for rewrites as everything else, because when it comes time to program it, you run into bugs and unexpected behavior with libraries and the realization that your new architecture has problems and all of the problems that come with regular non-rewrite programming.
That idea that "First you need to determine the requirements. All of them. In excruciating detail." is the problem waterfall always encounters -- to write the perfect list of all requirements, that's ultimately writing all the code. Such supposedly perfect waterfall specifications are an illusion.
So no. Approach rewrites with the modern common sense of any software project, which involves defining and building out working components incrementally with testing, according to defined high-level priorities, and flexibly dealing with issues along the way as you run into the same unpredictable problems you always do.
And finally:
> Leaders who have delivered successful rewrites often describe the process as one of the greatest accomplishments in their career, but they never describe it as fun.
This sounds made-up. What leaders? Why would a leader ever describe a rewrite as one of the greatest accomplishments of their career? I've never heard of such a thing. And why shouldn't it be fun? Rewriting something to wipe away all the old horrible tech debt and start over from scratch can be super-fun!
- saghm 3y ago> > Leaders who have delivered successful rewrites often describe the process as one of the greatest accomplishments in their career, but they never describe it as fun. > This sounds made-up. What leaders? Why would a leader ever describe a rewrite as one of the greatest accomplishments of their career? I've never heard of such a thing. And why shouldn't it be fun? Rewriting something to wipe away all the old horrible tech debt and start over from scratch can be super-fun! It's also pretty hard to argue against a statement like that; if you point out someone who says otherwise, they can just say "they're not a leader". If anything, it's somewhat circular, since basically they're defining "leaders" as people who agree with them.
- ahhfgsado6698 3y agoYou guys are asking for permission and leadership supervision and scheduled time to do your rewrites? I was planning on just banging it out over a weekend and then sliding it in all stealth like on a slow Monday morning. I ain't no fancy nuclear weapons silo programmer like the author here.
- mmcgaha 3y agoI think I understand where the author is coming from. I have not done a lot of rewrites but the largest one I did was an application for maintaining and generating our product catalog. The original design had split North America and international catalogs into different files that were 95% the same and these had to stay in sync. Other oddities of the old system had page numbers manually adjusted when new pages were inserted and a hand maintained table of contents. All together there were 12 different catalogs generated and each one had a manual process of importing new pricing before being generated. What kicked off the project was a desire to correct the amount of manual labor required for generating new books but as soon as the project was proposed we had a VP that wanted to justify the project by doing something more. Now more was a little hand wavy but the concrete things were color pictures and automatically generating and laying out the entire catalog automatically. The problem was there was no data for either of these task; we had no color pictures and there was no repository of product attributes to automatically lay out the catalog. The break in the project that made it become possible for success was that the VP with hand wavy dreams left the company and I was able to start work on a rewrite that solved the important pain points without adding the overhead of multiple departments coordinating taking new pictures and and building a PIM with the required attributes. It has been been five years since we went live with the new catalog and the color pictures are around 50% of the book now, and the PIM has is getting rolled into and entirely different project. If we had waited then we would still be waiting on the benefits that kicked off the project in the first place.
- Too 3y agoThere seems to be an underlying tone of waterfall=bad. That’s missing the nuance of why it’s often considered bad. Usually because you never know the requirements up front, leading you to build the wrong thing. Except, when doing a rewrite you do know the requirements up front. Based on the experience of your current system.
- crazygringo 3y agoNo, that's only half of why waterfall is often considered bad. The other half is because of the unpredictabilities in building software period -- internal rather than external. You can build out one component fully and another component fully and then finally test them together at the end and discover there's a horrific race condition that requires rebuilding both from scratch to fix. That's why a more iterative process is considered best practice today, to find showstopper bugs earlier rather than later, particularly to catch and address architectural issues sooner rather than later. (But also, like I said, rewrites are rarely trying to produce a 1:1 copy in the real world. The whole point is usually to fix a bunch of problems with the previous system along the way, not to continue to reproduce the unwanted behavior. I'm not saying there are never perfect 1:1 rewrites that intend to reproduce all the bugs and warts and all, but it's rare.)
- j45 3y agoHaving an idea of what is known and not known in a solution can shed a light on approaches. It’s more possible for known (existing) solutions to go through the phases of waterfall for a rewrite. Where unknown solutions exist, using agile to get the vectors correct and signed can help a great deal. I have learned from experienced PMs how even agile waterfall loop where each step of waterfall itself is an agile undertaking can be beneficial in some cases. A rewrite can represent getting something much better than it is in a different way. A rewrite can represent getting something much better than it is in a different way than developers who may want to start from scratch to relearn the lessons of the past and develop technical debt in a new way. Of course to be optimistic how you both experienced and new developers will be open minded to listen to approaches they might not be used to, and not assume that if they haven’t seen or understood a way forward it doesn’t mean there isn’t understanding in why things were done in a certain way. Needing to feel significant from a coding project maybe worth some introspection - empowering users to benefit from software is most important. Tech should work for users and not the other way around to validate developers for finding a novel way to solve a problem that doesn’t move the needle for them