The software problems concern me because the fact that things don't work properly at this stage suggests that their development process is not a good one and even perhaps that the design is not that great. A "good" process doesn't release features until they "add value" - i.e. they may not be everything you wanted them to be but they have to be good enough to be useful before you impose them upon your users.
With the wrong design some tasks become Sisyphean - possible enough in theory to keep your masters cracking the whip (no we can't change direction now - just work smarter!) but so hard as to slow your work down to a crawl. One does make bad designs - I certainly have. It's not so common to recognise that and even less common to be allowed to fix it.
Last edited by t43562; 12th Sep 2016 at 12:41.