In my view, there are five types of QlikView Developers.
1. Hacker: The Hacker starts off learning anything with great enthusiasm and ready to overcome the challenges. He or she is willing to stay on the plateau for long time as long as they get to hack something once in a while. They are generally happy to take up a challenge to solve a specific problem(s). The Hackers love to show off their skills and they love building app for SIB(s) (Seeing is Believing). He or she specializes their skills in searching on QlikCommunity and happy to hack the logic/implementation or methodology. The Hacker loves reverse engineering process to solve any problem. He or she may not know or understand the full theory behind the problem they are about to solve. In honesty, they don't care to get into the depth of the problem. They are generally result oriented and not process oriented. The QlikView Hackers are interested in building SIB apps, extension objects & integration of google maps by reading a blog post or cookbook and by exploring new tools. The QlikView Hackers are great at building demo applications but they will lose interest in long term end-to-end implementation. Their main source of energy for their spurts is from Red Bull and/or caffine.
2. Sellotaper:The Sellotaper approaches every new task or career opportunity with great enthusiasm. They are overjoyed when they make the initial progress and they love to show off their progress even before it's half complete. However, their enthusiasm quickly fades away when they were asked to do similar thing(s) in long term. The Sellotaper will search for shortcuts and will try to cut the corners. He or she will work on reactive basis, i.e. they will solve the problems as a reactive response. They don't like to take the responsibility to clean up the underlying code or logic and prefer to sellotape when the problem arises. He or she hardly comments their code, their object/variable naming convention is inconsistent, they like the absolute paths in the QlikView script, they most likely use the transparent text boxes to overlay on existing QlikView object(s), they will fix the QlikView data modelling problems by selecting and locking the fields instead of restructuring the data model. The Sellotaper is not interested in code refactoring and they hate code reviews with peer group.
3. The Ambassador: Every large team will have at least one Ambassador. The Ambassador knows all the theory behind the Software Development Life Cycle principles, Project Management and Quality Assurance. He or she might be unofficial Business Analyst for the project(s). Although, The Ambassador sits within developer team but he is more interested in overall delivery of the project instead of actual fitting of nuts & bolts. The Ambassador is very good at taking new initiatives and represents the developer team in meetings. He or she spends little time doing the actual development and generally rely on other developers to solve complex problems. Their motivation is the ambition to lead and manage the project.
4. Excel Superhero: As the name says, Excel Superhero come from strong Excel background. In their previous role, business folks treated them as demigods for their Excel skills. The Excel Superhero love the lookup functions, string functions and pivot tables. The Excel Superhero have intermediate thought process to solve any problem or complete a task in QlikView. This intermediate thought process is Excel way of solving a problem. He or she thinks about rows instead of sets and they tend to rely on building the logic within QlikView expressions instead of simplifying data model in QlikView script. The Excel Superhero are advocates of Macros/VB Script COM API and wanted to work their VBA magic using the COM API in QlikView. He or she generally appreciates the code or expressions by volumes and not by elegance of the solution.
5. The Master: As the name suggests, The Master is product evangelist and enjoys the plateau. The Master guides other developers with best practices and has strong foundation of broad spectrum of things in IT. He/she sets high standards for himself, and his/her work sometimes takes longer time to complete. It's not because, he/she is not incompetent. On the contrary, he/she is highly capable; but he/she makes work for himself/herself by creating new coding practices and development tools, all to meet his/her own standards. He/she is happy to share their knowledge to others. You will find him/her speaking in the conferences and other technical events.
Obviously, we all fall under one or more categories based on our background.