Reply to thread

Message

<blockquote data-quote="kigmatzomat" data-source="post: 9534494" data-attributes="member: 9254">Yep.&nbsp; several times.&nbsp; A couple at a Fortune 100, the last one wrapped up last month.&nbsp; One particular process I shepherded from paper, to MSAccess (budget denied for 12+ months), to MSAccess + MS SQL (web developer budget denied, db budget approved) to IIS+MSQL (&quot;why is this risk-management process not in a proper application?!?&quot;) then from ugly IIS vb to c#.&nbsp; That one was for government audits. The last one was a migration from MSSQL to Snowflake.There were also a few that didn't happen that should have and were the triggers for me to look for other employment. (&quot;It's perfectly fine for multi-million dollar engineering contracts to be dependent on a set of XLS macros hacked together by a college intern to drive hydraulic simulations that could result in billions of dollars of damages, why should we spent $5k on a software license for a vetted application?&quot;)Again, that's what due diligence and retention bonuses are for.&nbsp; Been through acqui-hires from both sides. We don't know how hard it would be.&nbsp; I mean, if it was designed in accordance with &quot;D&amp;D One&quot; concepts of modular rules, it would be easy peasy. WotC decided to buy DDB while simultaneously putting 5e 2024 in development.&nbsp; That was the ideal time to do a code freeze and do the necessary refactoring.&nbsp; WotC's gets all the credit and all the blame for DDBs (in)ability to support 2014 and 2024.</blockquote>

[QUOTE="kigmatzomat, post: 9534494, member: 9254"] Yep. several times. A couple at a Fortune 100, the last one wrapped up last month. One particular process I shepherded from paper, to MSAccess (budget denied for 12+ months), to MSAccess + MS SQL (web developer budget denied, db budget approved) to IIS+MSQL ("why is this risk-management process not in a proper application?!?") then from ugly IIS vb to c#. That one was for government audits. The last one was a migration from MSSQL to Snowflake. There were also a few that didn't happen that should have and were the triggers for me to look for other employment. ("It's perfectly fine for multi-million dollar engineering contracts to be dependent on a set of XLS macros hacked together by a college intern to drive hydraulic simulations that could result in billions of dollars of damages, why should we spent $5k on a software license for a vetted application?") Again, that's what due diligence and retention bonuses are for. Been through acqui-hires from both sides. We don't know how hard it would be. I mean, if it was designed in accordance with "D&D One" concepts of modular rules, it would be easy peasy. WotC decided to buy DDB while simultaneously putting 5e 2024 in development. That was the ideal time to do a code freeze and do the necessary refactoring. WotC's gets all the credit and all the blame for DDBs (in)ability to support 2014 and 2024. [/QUOTE]

Verification