We're a few days in 2019, and from a time perspective, I can say I had a busy 2018. I must say I've never expected that but in 2018 I've created or worked on 24 PowerShell modules. Some were simpler ones, some were a bit more advanced, and some will be retired in 2019 because their features will be moved to other modules. In PowerShellGallery alone those were downloaded over 15000 times (I must admit that some of those are surely automated tests – “Hello Pester” that I've learned in 2018. It's a nice number thou, and something I'm kind of proud of myself. After all, before 2018 I've not created a single PowerShell module before. Sure, I've created a bunch of scripts, hardcoded, that did the task that I had to solve. But I've never before built something, that could be installed by one little command Install-Module (something I've learned in 2018 as well) and executed by anyone, anywhere. I know the title says Sixteen PowerShell Modules but some modules are just too simple to give them anything else than a small mention.
If you follow my little company or me on Twitter or Facebook or GitHub you already know some of them, but not all of them get the same treatment. Not all of them are announced or even prime time ready, and some are in constant development which may be bad for some people because I like to change my mind on how things are supposed to look or work and that means breaking changes most of the time. What works today, tomorrow may not suit my needs that much so I change it. I try to be careful, I try to support old configuration, but it's not always possible or even feasible in the long run. But the main reason for the change is that I'm continually learning new things so what seemed like a good idea in January, in June looks like I should have spent more time on design.
Since this is a summary of my year, I've decided to share a bit of stats with you. I was pleased to see that year to year my blog was able to get 69% more visits. Something I'm proud of it. It's funny thou because it seems like on Saturdays and Sundays there is very rarely any traffic. Like if people stop searching for technical solutions, PowerShell modules and all that. Contrary to myself, where I spend weekends doing just that.
Finally, I would like to say BIG THANK YOU to people that helped me with some PowerShell problems in my journey thru 2018. I've learned a lot from you. Last but not least I would like to thank everyone involved in building VSCode and VSCode PowerShell Extension (and it's additional supporting modules). Working in VSCode has really impacted my PowerShell skills and allowed me to improve my skill set overall.