canada is very protective of its regulated fields. if you didn't graduate in the US or Canada, it's very hard for an immigrant to become a vet/dentist/doctor/lawyer/engineer/accountant/etc. So these people end up in a rut where they are either delivering food, or stuck in an entry level job forever
From my experience those intelligent people who for whatever reasons can not get back to their original occupation still doing rather well in other fields. I am in Canada since the beginning of 90s. have many immigrant friends, most of them are well off.
indeed you should avoid postgres if all you need is saving files on a disk. that's exactly the point. people reach for complex client side frameworks when all they need is to render some markup.
not trying to be facetious or anything, but I doubt their product team is worried about customers that are mad they have to click a few extra buttons to save 1 or 2 dollars per month
For every person who comments there are thousands and thousands who are reading. This is their target customer base -- highly sophisticated technical professionals who have the potential to influence many more non-technical people who take their expertise and opinions as a given. If they aren't worried about it then maybe they should think about it a bit more.
On the other hand, a competent team would care about a negative message being listed first on a popular internet forum frequented by their target demographic.
The corporate leviathan has to first detect that event and analyze it for sentiment. Before any loss mitigating response can be possible in the first place.
half finished projects that you developed on your own don't hold that much value. They may pad those green stats, but those can be faked quite easily. It's contributions to projects with other contributors that really matter.
Why work on half-finished personal projects when you can contribute to a high(ish)-profile public projects, especially such that your prospective employers might be using?
it's at least one server (_any_ computer that never turns off) hosting things you would use (and probably pay) on a day-to-day basis.
The most important point is to be available all the time in multiple devices that you own, that's why some folks don't want to do these things on their main machines. A laptop you could take it away, and your family at home would/could lose access to the things you're hosting. A beefy desktop might be a bit too power hungry to be on all the time.
this kind of harms the appeal of a homelab. If you search youtube, you will find many creators sharing their labs. But when you look at the services they host, 80% of it is just stuff to maintain their infra (hypervisors, monitoring tools, high availability stuff, etc).
All of this is very interesting, but not very useful. I'm personally most intrigued by how people are maxing out their old hardware for years, like many examples in this thread
Seconding the sentiment on this thread, I used this book to learn JS 5 years ago, and it's awesome. I've never seen another resource as good. YDKJS is more of an advanced treatment. If you're a beginner it feels academic, while Eloquent JS is very practical and approachable.
40% of Federal MPs are landlords. Haven't got figures for Provincial MPs or Municipal representatives but I'll wager a substantial amount are landlords too.
