3 ms·
Oh lordy, this is waking up some bad memories of using Dynamics for a huge project. As a team of 50, we started having to extend the crap out of it with c#, whi
by jksmith 4y ago
Oh lordy, this is waking up some bad memories of using Dynamics for a huge project. As a team of 50, we started having to extend the crap out of it with c#, which made me question the use of the tool in the first place. So we called in an expert, who proceeded to tell up that if you didn't stay as close out of the box as you could with as little c# customization as possible, then we'd run into problems, which of course was the issue. That was in 2015, and the tool may have gotten better, but at the time, it was only capable of some basic crud applications, along with some pretty good interop with msft office. Point is, if it's a no/low code solution, the whole solution ultimately better be in the box. Otherwise you're screwed.
So how do you come up with a uniquely competitive product from no/low code if the whole solution must already essentially be in the box? Maybe the best use case is internal IT needs.
- pjmlp 4y agoThis is typical enterprise stuff, Sitecore, SharePoint, SAP, LifeRay, AEM, .... Out of the box they are always very generic and then it is expected that a team of consultants, certified from agencies with vendor partnership, drop in to perform the actual customization.
- jksmith 4y agoThe whole scene was funny because while the MSFT Dynamics sales guy was really trying to be helpful, the MSFT Azure sales guys couldn't give two shits about the tool and wanted to give it away as bait to get customers into Azure. That was my take at the time.
- pjmlp 4y agoYeah have seen it happen as well, with other products though.