This seems like a nice feature. Python has sets like this too, and it's super useful.

I used to work with a guy who was a tech lead on a project. He was getting constant pressure that he app he lead simply did not work. The problem all came down to a database connection that was being used in multiple threads.

I told him what the problem was. He said, great let's make a meeting to talk about it. I wasn't allowed to solve it just yet. I made the meeting. Everyone understood. The lead told me to then make a prototype, but still not allowed to just fix it. I made the prototype. The lead said we needed a meeting to talk about it. Still not allowed to just fix it.

Meanwhile we still get pressured to make the damn app work, the lead keeps saying that none ever bothered to read documentation and that we need to sit down and talk about how we are going to to solve.

This went on for several weeks. When I was finally allowed to solve the issue (not by him), I took only one day.

I've been promoted into management for over one year now, and I've barely programmed on the job. I find it hard to keep up with the details on the application, but I still make an effort to with news, and do some programming for fun on my on.

I think it's important for manager to still be able to make small contributions to the application. The manager isn't going to own a big new feature that takes several sprints to complete, but he can still debug or solve some bugs, or make smaller changes. He should also have an overview of the code's structure, and know about the technologies used to build the project.

Indeed. The name doesn't follow the conventions of other commands in Windows/Powershell at all. And it is inconsistente too. "sudo" stands for "super user do", but in Windows the notion of super user is called administrator. This will likely also cause confusion with people googling for "sudo" and getting to *nix related pages instead.