4 Replies Latest reply: Jun 29, 2018 12:36 AM by Rob Wunderlich RSS

    Bad envrionment: Company has a terrible perfoming app, complicated section access, demanding users, and the main developer of the app has left with no proper explanation, documentation, or handover. The new developer is under pressure - advice please?

    Michael Wallman

      Hi,

       

       

       

      I am writing this on behalf of a new Qlik colleague who is in a very difficult situation.

       

       

       

      Our company has a terrible perfoming app, complicated section access, demanding users, and the main developer of the app has left with no proper explanation, documentation, or handover. The new developer is under pressure - what to do?

       

       

       

      Terrible performing app

       

      - The Qlik Sense app loads and transforms data in the same app and the user interface is in the same app.

       

      - The expressions are extremely complicated, full of set analysis, IF statements, AGGR etc, many of them going into 5 pages if you paste them into Microsoft Word.

       

      - Because of these complicated expressions, some of the charts take over a minute to load.

       

       

       

      Complicated section access

       

      - Section access is used to "conceal" information to certain users, so there are two copies of fact data, one masked, and the other unmasked. Data reduction is done also to hide certain information. And also dummy data is loaded because in some cases all the data needs to be accessible from a table by all the users.

       

       

       

      Demanding users

       

      - The users are constantly asking for more and more complicated charts to be added to the app. By the sound of things the management is under pressure to deliver so they cannot say no to the users.

       

      - Unrealistic deadlines dropped from nowhere so the developer becomes under pressure.

       

      - Everything is "agile" where things need to change as per new requirements

       

       

       

      Main developer left

       

      This app took around 1 year to build and the main developer has left.

       

      - There is hardly any comments in the script to explain why certain procedures are done the way they are

       

      - No relationship diagrams for the new developer to use

       

      - No documentation on the UI or why the expressions were built the way they were

       

       

       

      The new developer feels extremely under-pressure as he is the only one who has to deal with all this on his own. He knows the best practises but with such complex data model, and ridiculously complex expressions he feels overwhelmed and feels like it is risky to make even small changes because it may impact some unknown part of the application.

       

       

       

      What advice do you have in these circumstances?