11 ms·
The problem with these tools is that they invariably have solutions to their own design problems that conflict with the system you need to build. One of my old
by Smeevy 5y ago
The problem with these tools is that they invariably have solutions to their own design problems that conflict with the system you need to build.
One of my old customers went with Tibco as a replacement for an internally developed system and have had no end of troubles with it. They were over 2 years late in their roll-out and the unforeseen limitations/lack of understanding of their tool have basically made them re-create their old C# application in Tibco in its entirety, thereby reducing Tibco to a second-rate cluster manager. I'm sure they did a number of things wrong in that effort, but that's an expensive lesson that they relearn every year when their gigantic Tibco invoice arrives.
I'm also in the process in migrating a system from the Versata business rules engine/ORM application that is hands-down the worst system I've ever seen in over 30 years of writing software. This is another client with their own set of problems, but I have literally been able to replace thousands of lines of bizarro-world copypasta a single SQL query running on top of a normalized database.
That's not to say that Tibco or these new cloud-centric tools aren't impressive and useful, but I haven't seen any of these tools that I would ever recommend for anything other than the absolute simplest glue code service. Additionally, I probably replace that service with something boring as soon as it gives me any backtalk at all.