The Indoor Cyclist's support thread
- Thread starter Jeremy
- Start date
Juggernaut
Master of the Metaphor
The amount of cross product backend code reuse is going to be staggering. Nothing I enjoy more than vanilla packaged with 50 different names.
Having been part of quite a few mergers over the years, I would say that these 2 products will never ever merge the codebase. In fact, in a few years when they say it's a single product, there is a 99% chance they still exist as totally separate codebases. Many products these days are multiple products disguised under a single trench coat.
Honestly getting them to use the same login across both platforms will probably take a year to finish.
Juggernaut
Master of the Metaphor
Having had been a backend developer for nearly 30 years who “survived” 3 acquisitions and two mergers myself I “know” you are correct for the preponderance of the individual product’s code base. I also “know” that a “tactical” solution will be instituted to bootstrap what will appear to be a cohesive framework masquerading as a canonical cross platform format.
The code reuse will be on the new “presentation layer” so no one see how the sausage is made. 😉
I’ve been gone from that life for 3+ years now and those AssHats are still running systems and processes daily that I wrote decades ago. They have no idea how (or why) they work, what the dependencies actually are and refuse to comprehend (despite countless pleas to re-write them) that utilizing exe’s via a wrapper built with an IDE that has been out of support since the early 2000’s is a bad idea.
SmooveP
Well-Known Member
Financing the cost of the merger may lead to higher prices.