Status Update

Hi All! As many of you know, I have been pretty scarce around the QlikView community as of late. As crazy as it feels to say it, I am no longer working as a QlikView Developer. I have accepted a new role, in which I will be focusing my time on user experience design and product development. No more editing script for me, I suppose. This is an exciting change, but I will miss QlikView and, more importantly, I will miss the QliKView Community. For now, I will keep my blog around. Who knows, maybe I will post some UX Design insights down the road. Thank you for all your support over the years… until next time!

The 4 Qlik Community Types We All Love to Hate

This isn’t a design post, but I thought you could all relate! Add your favorites in the comments below.

1. The Vague But Desperate Poster

This poster usually includes a desperate plea for help in the title but then no information whatsoever in the body of the post.  We can tell you need help, but with what? Help us help you!


2. The Really Important Guy

This poster needs help right now.  Drop what you are working on and help him – his deadline is your deadline!


3. The TMI Poster

This poster includes his entire QVW script in his question. All thirty-four pages of it. The error is in there somewhere!


4. The Boss

This poster lists a set of requirements for the application he needs you to build. Oh, and he needs that by tomorrow afternoon. So if you could come in on Saturday…


QlikView Blogs

Arguably the best thing about QlikView is its active and helpful community of business and IT professionals.  With inspiration from Arturo Muñoz, and his blog post “The Qlikosphere, 18 Blogs You Should Follow”, here is my Top Ten list of the best QlikView resources on the web:

  1. – Rob Wunderlich
  2. – Stefan Walther
  3. – Jonathan Dienst
  4. – Stephen Redmond
  5. – Steve Dark
  6. – Barry Harmsen
  7. – Deepak Vadithala
  8. – Matthew Crowther
  9. – Tim Benoit
  10. – Vlad Gutkovsky

Check out Arturo’s post here:–part-i and let me know if you have any other QlikView resources you use.