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

In my region ( USA), ordinary people simply don’t have the resources for individual lawsuits like this.

It would have to be a well connected or monied individual to have any chance. Or the situation is so egregious and documented enough, that a law firm thinks it can make money, by taking most of the winnings from the victims

Uphill, in the snow, both ways

Maybe lemmy will grow over time to include more types of people.

Social unrest may evolve this network faster than expected, in particular ways that are not foreseen. So, in my mind there are two paths for lemmy. A stable growth or chaotic .

Edit : unrest in any country that has a lot of lemmy users if alternative social networks clamp down or are unsafe to use

For a supposedly gun infested and ultra violent country, there is an eerie calm lasting for decades.

Most probably this was a one time thing?

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.

A lot of the initial popularity of Isis in Iraq was due to very similar factors. This was an uprising of a complex mix of people and goals. Most involved at first were established leaders who were patriotic and tribes who were oppressed by the new and invalid government.

This of course was airbrushed in the west and countless thousands were killed by Americans during the uprising.

Syria was destabilized due to the mass death.

The main takeaway here is that force often seems like an answer but that can go badly

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.

All posts are filtered, organized and sometimes made by AI, or non AI programs, which will decide which users get shown which posts?

Interesting