

I have it on good authority that you currently have a project idea which you can use to pick one (or more) of those paths and start learning. ;-)
For example user management in studio3T
Not sure how I missed this on my first read of your post. But, this looks like a fancy front end to making MongoDB calls. That makes life easier, MongoDB has a well documented API and a driver for C#. As an aside, if you want to get really good at PowerShell, getting a basic working knowledge of C# and .Net in general is really helpful. For the lazy (and I always like lazy), there’s even a pre-built MongoDB module on the PowerShell Galley called Mdbc. There is also the Project’s GitHub Page which has a lot of useful info.
Granted, this path likely means learning enough about MongoDB to create/delete/modify users. But you came here expecting a load of homework, right? Also, this is a good excuse to spin up a docker container running MongoDB and go hog wild breaking the fuck out of it (just call it “research” if management asks). And who doesn’t love breaking stuff?
I’d also note that you may be able to get some help along the way by capturing the network traffic to the server caused by the Studio3T GUI. WireShark can capture the traffic to/from the DB server and you can read that to reverse engineer some of the calls you care about. Just, make sure you talk to your security folks before you download/install WireShark. If they are worth their salt, they’ll understand an engineer installing/running wireshark, it just makes their day easier if they know the alert is coming first. Assuming the GUI isn’t complete shit, it may encrypt traffic. This can be dealt with by using the SSLKEYLOGFILE environmental variable. In most cases, this results in the TLS keys being saved to a file and that can be imported into WireShark.
Good luck, and have fun!
I happen to be a prime example of how bad US Rail is this week. I’m taking my son from near Fredericksburg (the real one), up to Ballston for a summer camp. We have a couple options:
So, for the low, low cost of about 1.68 times the cost of driving, we can take slightly longer to get to our destination and have zero control over our schedule, which makes the actual time devoted to travel considerably longer. We tried the public transit route last year, and it meant leaving earlier in the morning (about 30 minutes) to catch a train to get us there on time, and getting us home around 45 minutes later. And this is right around the US Capitol, which has some of the better transit options. Needless to say, we’re driving this year.
I really want to be able to take transit, but it’s basically dead in the US. Earlier this year, I needed to go to Boston for work. Catching a train from Washington, DC to Boston meant an 7 hour train ride (using the “high speed” Acela line) at ~$500 round trip. Flying was 1.5 hours and cost ~$300 round trip. Wanna guess which option I used?
Basically, all of the incentives are stacked against transit options in the US. Except within certain metro areas, driving or flying is always cheaper and faster. Yes, inside those metro areas, public transit can be great. I used to work in Washington, DC and used the VRE I mentioned earlier to get there and then WMATA or the Capital BikeShare to get to my office. That was great, since I didn’t have to drive into DC every day, which sucks big donkey balls. But it probably wasn’t cost effective and wasn’t really time efficient either.