[dantiberian]

I've previously worked with enterprise financial systems, and most of what was described here was standard functionality, or would be customisable to do so without too much effort. I would have loved to have heard more about whether they evaluated traditional ERP systems and why they chose to build their own event sourcing system instead.

[a_liang]

One thing to consider was that we had to build this in about 5-6 months from the ground up, and match it to our existing financial system. Most of the work was to derive the financial meaning from a system not designed to provide it. The traditional ways you would extract data into an ERP would be with raw data import, or with some slightly processed data. If we did that, we still have the problem of tightly coupling data models and accounting logic, which makes for very slow engineering progress on the product front. Not a tradeoff we want to make.

If you were talking about exporting the data from the event based system, then that's still possible, and I think it's something that our finance team may still be evaluating, but I can't speak for them.

[ernestbro]

Same story with Superset, their homegrown BI system. Why re-invent the wheel?

[sheeshkebab]

If it was not for "reinventing the wheel" we'd all be coding in cobol or Fortean against IBM supplied mainframes.

In other words - because they can and should (and can afford to and not be hooked up to some third party vendor milking them for the rest of their companies existence).

[Tarq0n]

Why sell your soul to Tableau when you can leverage your large pool of engineering talent to create something that only requires investing once, rather than large recurring license fees forever?

In my opinion Superset actually fills a niche that was open for far too long.

[hobofan]

Because it is not rocket science and you need people inside the company that know the insides of it when you want to adapt it?

[amenghra]

NIH syndrome?