1,299 karma · joined May 17, 2016
* less desk real estate needed
* many of us aren't doing much number entry at all
It is not too hard these days to buy a complete and immediately usable keyboard on line. But it does help to know what you are looking for because there are choices to be made around format, switches, keycaps, etc.
That "certain point" is so far away, it might as well not exist.
Plenty of US and western companies operate to make a buck in far more restrictive markets around the world.
Hell yeah, the government should have a say in how publicly funded schools run their admissions. Why should a school running on public funds get to favour students differently based on who they are related to? Do they have a greater right to that public money?
You do realise that the EU gave the industry (i.e. the "experts") the task of defining and agreeing on a standard for charging cables? The manufacturers worked on this and agreed on USB-C, all except one US based fruit company.
To me it looks like the discussion in the US has been poisoned such that there are only two options: Stalinism vs the-poor-can-starve-in-the-streets Capitalism. It's a framing from the cold war which the right in the US has kept alive. It exists to hide the possibility of a middle path, a popular middle path which Europe took after the war.
"As I said before, the insights are not particularly original, I’m just raising awareness of issues."
If you are familiar in the subject matter, then that may have been your cue to stop reading.
Satire is dead.
The value of learning database systems is learning how to model and represent data. All entirely relevant to NoSQL and key value stores.
> Because many languages use lightweight threads (fibers, coroutines, etc.) now that don't involve context switching
Concurrent programming is everywhere. It is not just something that has to do with threads. Even a simple CRUD app with a React front-end and DB back-end is a concurrent system. If your ever used a Promise or async/await in JS, you're dealing with concurrency.
> barely any company does anything beyond web requests
You still need the basics and at least an understand of what DNS is, what a firewall is, etc.
No one here is saying that graduates need to have mastered all of these different areas. But they should at least be able to recognise them when they hit problem later on in their careers. I've worked with junior web developers in the past who had no idea that they're working with a concurrent system.
"Management treats us like faceless cogs in a machine! They only care about grinding productivity out of us."
Also tech workers:
"How dare management require us to go to the office! I can do my work perfectly fine from home over Slack. I don't need that office socializing BS. It's a waste of time."
At work we have a bunch of Python services which do REST API and CRUD for the most part. There we have a simple plain python dependency injection set up which puts together the different components/classes of service and makes sure that each is provided with the references its dependencies. This is defined in one python file. I experimented with parsing this file and graphing the relations between the components, and the result was pretty good (given my low effort). It did a good job of exposing the relations between most of the important classes and where things had gotten messy.
Speculating, like gambling is a zero sum game (at best). Any gains come directly from other players. They are inherently risky.
There is a qualitative difference here.
I've noticed this too.
My leading hypothesis is that projects start with simple data storage requirements which don't require much more than "flat file database + JSON", i.e. NoSQL, document database like Mongo etc. The fast and loose nature of these systems is nice to have at the start of a project too, compared to the work needed do SQL.
As the project evolves requirements start to appear which require combining data from 1 or more of these "flat files" or document collections. Then you discover that that your data is relational after all and these new "simple" queries you want are hard to do with your chosen (NoSQL) database.
In short: As an application evolves and its data grows, it tends to become more relational.
Conclusion: Demand more from your terminal emulator, including direct support for more of the Unicode drawing characters.
Maybe that is how you experienced it as a computer nerd like myself, but that was not the pitch.
For business it was computers for all just like the big boys. For families it was prepare your kids for this new computer oriented world. For us kids it was play computer games at home without having to stick coins into a machine at the mall. But us kids had to play the education angle on our parents who had credit cards. :-)