College computer programming programs normally do not train people to immediately work, unless the students spend thousands of hours coding on their own. Most comp sci students avoid this.

So, when a new dev graduates and they did not do that extra work, then the first year of paid work is them putting in those hours while being paid rather than doing it for free

That is very frustrating !

New devs generally suck, I sucked a lot.

The problem I fear today is that there are more crutches new devs can rely on, until they can’t.

And it’s not a sharp boundary between getting by and not being able to work it

I’ve installed from steam after downloading it the deb from the website , and steam self updates. I never had issues on mint, Ubuntu or popos for years.

I really don’t know much, and anyone should take this with a grain of salt: but in my opinion any other way of installing steam on this branch of Linux is asking for trouble

I spent a lot of time using msdn Microsoft docs for windows and activex c++ back in the day. Faintly envious there are videos in the c# docs.

I changed tech stacks, but comments and examples are awesome to use inside docs. Usually in the php, it’s the comments in the docs that are the best help, and example code and work around can be found there.

But most php depends on the tens of thousands of projects and libraries made others: so the docs one needs is scattered in the dependencies. Some who have good docs (laravel) and some that have no docs , in which case a debugger is best way to learn.

When I was learning to program in the 1990s, at university, it was easy to get good advice and learning from the printed word: both in books and on websites. I think if I had to start learning all over again, and not be in a good school, it would be very hard for me to do as well.

Today there is too much advice, too many influencers who recently learned whatever they are peddling, too much AI, too many fields of tech.

I think the best way to learn now is how many of us learned decades earlier; use a list of books that are vetted by many ( can find lists here and there, saw one in GitHub last year). And while reading the books read the documentation even if they are gaps in one’s knowledge and the docs are badly written.

I don’t think one needs recent books for many concepts and basics. The wheel has been reinvented many times in the hundreds of tech stacks in use today. And the same concepts will be easy enough to learn in newer docs once a technology and programming set of tools is invested into by the learner.

As for new software engineering ideas and architecture concepts: usually these are reiterated from earlier ideas and often marketed for profit. So older architecture books, refined by several editions, are still best.