At the same time, I feel like nowadays there's less forums or places people can ask help with, although today ChatGPT can be a good help with newbie questions.

Another option is to have enough people in the company interested in using that to justify it.

In my company (a large bank) Linux is now being rolled out to selected people as test because there was enough interest from a lot of the backend crowd.

That’s what I do, except I straight up create the python venv in a folder, activate it and then do pip install yt-dlp. No messing up with my system.

This kind of thing can be easily automated nowadays. It’s not really a problem.

That’s a good argument.

If I was gonna make a suggestion, it would be to use some formatting tool such as black to make sure your code is styled in a standard way.

What about accessibility?

Just as an example, I worked as a contractor with the biggest bank in Latin America before and basically all their server code is Java (with new code in Kotlin nowadays).

I have friends who work at the biggest bank in Latin America, where most backend stuff used to be Java. Nowadays all new code is written in Kotlin.

I’d go as far as saying you should know what every line of code does or you’re risking the whole thing to have unexpected side effects. When you understand what the code is doing, you know what parts you should test.

Another example is a large number of libraries using an external dependency to check if a number is odd.

As a programmer myself, collaborating on projects can often be more complex than simply "adding features." It's not uncommon to encounter challenges such as mismatched preferences in technologies, differing architectural choices, or even divergent design aesthetics that can dampen interest. Besides that, the original creator may not even appreciate the proposed changes and could reject them.