Noticeable that everyone that has stepped in to help out here are each battle-weary veteran victims of NinjaAbuse
To recap this Release:
Relocate installation directory and don’t tidy up the loose ends. This is SW Dev 101. At the very least, if this is impossible to do programmatically step-by-step instructions per hedge in Release Notes. But no, hours cleaning up their mess
Change to SQLite - problems writing to db file: recreate all your customs trading hours templates & re-attach to instruments. Hours. Again, like #Lancer - no forewarning, you’re out of commission meantime
CME change to Equity Rollover Dates - Ninja only did ES on their servers. More carnage, frustrated customers, no response from Support - they only fessed-up to it when I made it blazingly obvious that is what they had done
Customer asked if could Roll Positions automatically - Support: No. I’d noticed it’s a new Feature in 27
But what does that tell you about Ninja management/leadership? When they do a major update with ‘fundamental’ architecture changes, and introduction of new Features, there is no leadership in bringing together Development and Support to manage that rollout. And Support staff aren’t sufficiently interested to familiarise themselves with new Features (of which there are pitifully few) for a twice yearly event.
And don’t get me started on the Livestream fiasco
Michael Mouse beyond belief

Comment