> All the 'teaching how to think' was replaced with 'how to get a well paying job'.
Yeah. Companies didn't want to train new employees any more as that costs money (both for paying the trainees and the teachers) so they shifted to requiring academic degrees. That in turn shifted the cost to students (via student loans) and governments.
People call it a red flag for scams if you are supposed to pay your employer for training or whatever as a condition of getting employed... but the degree mill system is conveniently ignored.
The thing is, Nobel Prizes and other awards don't pay the bills.
Patents do, but in most cases it's trivial patents or patents for a "mutually assured destruction" portfolio (aka, you keep them in hand should someone ever decide to sue you).
That's a fundamental problem with how the Western sphere prioritizes and funds R&D. Either it has direct and massive ROI promises (that's how most pharma R&D works), some sort of government backing (that's how we got mRNA - pharma corps weren't interested, or how we got the Internet, lasers, radar and microwaves) or some uber wealthy billionaire (that's how we got Tesla and SpaceX, although government aids certainly helped).
All while we are cutting back government R&D funding in the pursuit of "austerity", China just floods the system with money. And they are winning the war.
At least in parts of Eastern Europe (especially the former GDR) district heating systems were introduced as a response to the oil crises of the 70s, resulting price shocks and the transport of coal to households being very labor and resource incentive [1].
> Obviously AI will massively increase the output of the economy, and people will figure out what to do with that, as people will want a shitload of things done. Which means the problem you're identifying will be trivial to solve, and we'll figure something out.
Historically, that "we'll figure something out" has usually meant the economical wipeout of large parts of the population, sooner or later followed either by some epidemic event or other "act of god" (like fires) that was a consequence of squalor and poverty, or by some sort of war to thin out the herd.
I'd prefer if history would not repeat itself for once.
> Historically, that "we'll figure something out" has usually meant the economical wipeout of ...
Uh, historically everything has usually meant the economical wipeout of large parts of the population. It still means that in most third world countries. Economic power is not the huge differentiator here.
Ymmv. I've got a mix of cheap premade patch cables and some I crimped from solid core, all cat5e, all holding 10gbe totally happily. I suspect that only works because they're a meter or two long but that reaches across the rack.
> My experience working at Big tech companies is that people with roles like “agile coaches", "technical project managers", UX testers add questionable value.
"Agile" can go and die in a hellfire for all I care.
But good technical project managers aka "bridges between the higher-up beancounters and the workers" are worth their weight in gold.
Pretty easy. Get them to talk about a project they've managed and start poking holes. Who was on the team? How did they organize meetings? What were the bottlenecks? How well did everyone get along? What did they do to help grease the gears? Did they have to change the process? How did they like the software? Which software did they use? Did they have to administer it themselves? How did they deal with management changes / team changes / tons of support requests / issues in production? Where did they draw the line between PM work and engineering work?
People have a very difficult time keeping their story together, especially when they're asked a couple of questions that interview prep didn't cover.
Beyond that though, there's the probation period. If they can't do the job, they're supposed to be let go before they become permanent.
Trouble I see from most interviewers is a tendency of asking questions with a "right" answer. Those tend to be a lot easier to game. They then fallback on sorting applicants by pedigree - the old, "no one ever got fired for choosing IBM" method.
Then, they come back and rant about how PM's are trash, and Agile is trash, etc. etc.
Well, quite frankly, you work in a shitty place then that doesn't know how to competently interview for these positions.
There are real differences in the knowledge and work behavior of great PMs and the bullshitters, and it's usually not that hard to tease out the bullshit in an interview if you know what you're doing.
>Well, quite frankly, you work in a shitty place then that doesn't know how to competently interview for these positions.
I was talking about a country, not a workplace, and franky, so what? I can't change that. What I can do, is tell you how it is, and how the system gets exploited.
If you live in some magic utopia where things are different(the US maybe?), good for you, but this information doesn't change anything for me where I live.
Best I can do is adapt and exploit the system in my favor as well if I can the same the rest do, otherwise I get left behind by the unscrupulous clueless scammers who do.
> It's ridiculous to me that they're concerned about the trustworthiness of AI-generated code when their code quality is so low.
Agreed, but at least it's somewhat sensibly structured. AI? Good lord you'll end up with a slopaghetti mess.
> They don't even have automated tests and ignore attempts to add them.[0, 1, 2, 3]
Two people, 540 issues and 270 PRs open at the moment. Not wanting to be that guy... but do the math. The reviewer team is small as hell and after this drama (which probably kept both of them busy with BS) they'll likely be even less willing to trust others.
If you want to stand a better chance at getting your code into other people's hands, go and contact the person behind the Evo fork. IIRC he's part of Hansemesh, Germany's biggest regional MC.
I have heard indirectly multiple times now that the only two ways to get a PR of interest merged is to either gather enough people to Like the issue on Github or to join the Discord and ask.
> What is it with mesh projects and having these super draconian trademark enforcers?
Simple. Follow the money. Meshcore has more than 100k of users, repeaters are cropping up like weeds across the world. And that means there is a serious incentive to "cash out".
Notably, the person "cashing out" here wasn't involved in Meshcore firmware or app development, but in marketing.
Yeah. Companies didn't want to train new employees any more as that costs money (both for paying the trainees and the teachers) so they shifted to requiring academic degrees. That in turn shifted the cost to students (via student loans) and governments.
People call it a red flag for scams if you are supposed to pay your employer for training or whatever as a condition of getting employed... but the degree mill system is conveniently ignored.
reply