Also AWK is made to be fast, right? I suppose doing something in CPython in a non efficient way might not be noticeable with a bit of text, but would show up with a large enough data stream.

If they actually wanted quality documents for people to use, they would be advocating for Standard Ebooks or something.

Or… you know… have PDFs that aren’t pictures of handwritten text?

This is why technically software is a liability. The less code you need, the better, since every line of code is a potential vulnerability and something to maintain, update, etc.

But is it that different than the podcasts voices Google already generate with NotebookLM since a while ago?

Only chatGPT has these kinds of comments as if you’re seeing code for the first time. 😆

I’m not against adding comments where is needed: in the company I work for (a big bank) my team takes care of a few modules and we added comments on one class that is responsible to make some very custom UI component with lots of calculations and low level manipulations. It’s basically a team of seniors and no one was against that monster having comments to explain what it was doing in case we had to go back and change something.

For 99% of the code you just need to have good names though.

Also Windows has a button similar to “don’t update this week” or similar.

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.

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.

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.