4 ms·

Unrelated to PowerShell, that sounds like information wasn't making it to the right people if the limit - 2 administrative connections were being used like that

Unrelated to PowerShell, that sounds like information wasn't making it to the right people if the limit - 2 administrative connections were being used like that for regular terminal services access, or like it would have made sense to split services across more systems if you had multiple people routinely doing simultaneous system changes on single servers. RDS CALs aren't cheap, but they're a one time cost and insignificant compared to the cost of staff sitting around waiting for RDP sessions to free up.

YeGoblynQueenne 10y ago
Aye right, there was no reason for all that. But, this was far from the only case where the company could have optimised its processes. For instance, as a junior dev, my work primarily consisted of copying some stuff off a spreadsheet (as in, with Ctrl+C), pasting it into a text file and creating some xml structure around it by hand. That was an extremely time-consuming and error-prone process and it caused all sorts of delays and frustrations, to myself as well as everyone that depended on my work. I spoke up about those inefficiencies very early on, but I was very inexperienced at the time and, to be honest, I had no idea how to properly communicate this sort of thing, so I never got anywhere. I only managed to come across as snotty and get a reputation as a trouble maker. After that I just kept to myself and focused on getting some experience with C# and learning psh and so on, generally learning as much as possible until I felt confident enough to look for a better job- which I took as soon as I found it. Generally, I was really unhappy in that company, but at the same time, exactly because I had to jump through hoops and learn how to automate my work, I taught myself a whole bunch of stuff that were very useful in my next job (where, btw, I had a great mentoring relation with my boss). So it all turned out alright.

YeGoblynQueenne 10y ago

Aye right, there was no reason for all that. But, this was far from the only case where the company could have optimised its processes. For instance, as a junior dev, my work primarily consisted of copying some stuff off a spreadsheet (as in, with Ctrl+C), pasting it into a text file and creating some xml structure around it by hand. That was an extremely time-consuming and error-prone process and it caused all sorts of delays and frustrations, to myself as well as everyone that depended on my work. I spoke up about those inefficiencies very early on, but I was very inexperienced at the time and, to be honest, I had no idea how to properly communicate this sort of thing, so I never got anywhere. I only managed to come across as snotty and get a reputation as a trouble maker. After that I just kept to myself and focused on getting some experience with C# and learning psh and so on, generally learning as much as possible until I felt confident enough to look for a better job- which I took as soon as I found it. Generally, I was really unhappy in that company, but at the same time, exactly because I had to jump through hoops and learn how to automate my work, I taught myself a whole bunch of stuff that were very useful in my next job (where, btw, I had a great mentoring relation with my boss). So it all turned out alright.