One of the reasons I started doing this blog was to have a place to store my random Qlik info. But even before this, over the years I have collected a number of code snippets that I can refer to whenever a similar problem comes up. So you don’t need a blog, you just need a folder.
To be honest, there are a lot of repetitive problems within the Qlik ecosphere. I think that is true for programming languages in general, however with Qlik scripting being a relatively niche area, it is even more apparent.
So with that said, save your work! Create a folder and start adding .qvs files and give them some comments. Future you will thank you.
I recommend downloading VS Code. There is a Qlik extension made by Xaver Han, which will give you syntax highlighting among other things. Both great and free. Also, I cannot recommend using the Chrome extension Add-Sense enough! Credit to Erik Wetterberg, it makes pulling load scripts from Qlik Sense apps a breeze.
If you want to up your game and potentially learn a new skill, create a Git repo. Many offer at least one free private repo, I personally use GitHub, but there are tons of options out there. This is a skill I think every developer should have, even if it’s just the basics.
*Disclaimer: If you are doing work for a client, make sure what you are saving is okay to have a copy of.