My personal preference is to avoid the "all in one" solutions as they often have limited features and updates have a higher chance of introducing bugs in features I use. I like using the right tool for the job rather than trying to use a hammer as a screwdriver. Sometimes the right tool for the job is the hammer, but if a hammer is the only tool you use, you are likely missing out on a bunch of cool features in the dedicated tools!
So my free weapons of choice for database related things are SSMS for TSQL, Profiler (I know others will say use extended events, but I got used to profiler and it works for 99% of the use cases I need to use it for and it is quick and easy to use) for analyzing running queries, visual studio for SSRS and SSIS and I like SentryOne's Plan Explorer for doing stuff with execution plans. Still use SSMS to generate the execution plan, but then save it to disk and load it up in Plan Explorer to work with it. I also like XEvents Profiler, although it is a bit limited at the moment. My hope is one day it will be a replacement for Profiler but that may be a pipe dream.
I use paid tools as well, but was wanting to just stick with free ones so this didn't feel to spammy.
In the article you mention PoSH as well, and my tool of choice (despite the bugs I've found and live with) is Powershell Plus Professional Edition (which is free). The best feature of it - one click code signing. Bugs though are when working in the console I've had it reset on me many times. The code editor window is decent and the command history is nice and it integrates to source control (which I am not using for powershell at the moment as I don't do THAT much in it). One thing it lacks that I really like in the Powershell IDE version that comes with Windows 10 is the command lookup window.
My preference for any tool is still to have a lot of single-purpose applications that look, feel, and work the way I expect. Last thing I want is an all in one tool that gets an update to fix a bug in a feature I don't use and creates a bug in a feature I do use or worse - removes a feature I rely on.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.