4 ms·
I had this team of consultants which sole purpose was to introduce an ES system, it was my predecessor that had decided this. The consultants were “experts” on
by he0001 5y ago
I had this team of consultants which sole purpose was to introduce an ES system, it was my predecessor that had decided this. The consultants were “experts” on building this kind of system. Very long story short, it failed miserably with a completely broke system which was hard to test, failed pretty much all use cases and completely blew budget.
According to the team there were many reasons why the project failed, one was they the requirements were complex. This also manifested in that implementing some of these requirements had “close to infinite” amount of combinations. Never understood that but that was one of the explanations. We shut down the project and made a “traditional” solution instead.
- jordanbeiber 5y agoI know you’re not me, but here I am, pretty much in the same boat. The word ”traditional” have also been thrown around.
- throwbabyaway 5y agoMy wife was diagnosed with PCOS (poly-cystic ovary syndrome) and we learned that it reduced her chances to get pregnant. Few weeks later we were sitting against this famous reproductive endocrinologist who were explaining us our options: - Yeah, going to a fertility clinic is of course an option. However, you should at first perhaps consider a more traditional approach instead. - What is the traditional approach, some medication? - People seem to have forgotten how to have sex these days. However embarrassed we were at that time (BTW he then laughed and saved us from the awkwardness), trying the obvious, easy solution and taking care of problems as they come became a conscious thing afterwards. I love over-engineering, but asking myself and the other stakeholders "what are we actually trying to accomplish here" is the most engineer-like thing I do nowadays. I'm not suggesting just winging it all the time, but looking for the easiest solution first, not last. That's all.