tag:blogger.com,1999:blog-15136575.post426855837964499199..comments2023-10-17T12:00:16.772+01:00Comments on Code rant: Fractured Product SyndromeMike Hadlowhttp://www.blogger.com/profile/16441901713967254504noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-15136575.post-85676558449403443632013-04-23T14:33:25.233+01:002013-04-23T14:33:25.233+01:00Interesting article, based on your very real exper...Interesting article, based on your very real experience.<br /><br />I guess the advantages to customers of the fractured model is <br /><br />1) non reliance on vendor (if you go bust, and they have source code they can find someone else to maintain the system).<br />2) absolute control over their own custom mods (rather than relying on the one-size-fits-all approach of SAAS).<br /><br />But food for thought all the same.Anonymoushttps://www.blogger.com/profile/07075781694582175355noreply@blogger.comtag:blogger.com,1999:blog-15136575.post-86885898879157115432013-02-28T17:18:33.086+00:002013-02-28T17:18:33.086+00:00This. We made the investment to build multi-tenan...This. We made the investment to build multi-tenant right off the bat and it has paid off in spades. If only we had "brand name" examples to show to decision makers to make crystal clear why clone and port is the wrong answer.Unknownhttps://www.blogger.com/profile/11662026976953853700noreply@blogger.comtag:blogger.com,1999:blog-15136575.post-77069483737660581812013-02-27T17:23:30.168+00:002013-02-27T17:23:30.168+00:00Great post. Having a project-oriented outlook qui...Great post. Having a project-oriented outlook quickly degenerates into a mess (given the scenario, I find it hard to believe they'd make it 5 years before imploding). It may conflict with some of the YAGNI crowd, but a product-oriented outlook should provide a much better outcome.Anonymoushttps://www.blogger.com/profile/01524527472698523956noreply@blogger.com