3 ms·
>Hindsight is 20-20. The iterative bloat during development can happen for so many reasons. Indeed, I once had the pleasure of replacing a BizTalk server with
by mrweasel 11y ago
>Hindsight is 20-20. The iterative bloat during development can happen for so many reasons.
Indeed, I once had the pleasure of replacing a BizTalk server with 50 lines of C#. It wasn't that the BizTalk server wasn't a bad idea. The project was for a big harbour, which have documents, cargo manifests, import papers and a ton of other stuff flying back and forth. The idea of having a central hub for data exchange and data conversion wasn't actually that fare fetched. It's just that the only part that was ever implemented was a the upload of a small 5-10 line xml file to the maritime administration, regarding the departure of ships.
After three years of running a BizTalk server, for that one purpose, and with no-one fully understanding Biztalk, we just replaced it with a custom Windows service.
If anything the takeaway is that you projects should be revisited once in a while for clean up.
- gnarbarian 11y agoThis is a perfect example of what I'm talking about. People can get caught up in the process including all sorts of possible use cases and lose sight of what really matters. After the dust settles you can see what it's actually used for. And sure, its not like the other use cases were bad or wrong, its just not how it ended up. It's possible that the other use cases never got traction because of some longest yard effort required on the client's end to implement a workflow. But even that low of a bar ended up being too high.