At least with Engineering/Math/Hard Science you have to demonstrate via projects and tests that you have actually learned something.
That "something" is the ability to solve problems.
There is a simple formula: To be employable (in a free society) you need to solve more problems than you create.
Every employee creates problems - most notably they expected to be paid. Some individuals create additional problems by being high-drama, which makes them less employable, but that is another story.
If "getting an education" means the same as "learning to solve more and harder problems", then it is easy to see why getting an education leads to better employment prospects.
Much disappointment, bitterness, and argument ensues, methinks, when people confuse "earning a diploma" with "learning to solve problems". These are distinct things. Though there is a correlation between having a diploma and being able to solve a problem, the correlation is less than 1.0 and is quite a bit less, I believe, than most university administrators are willing to admit. This comes down to marketing: Universities do not sell problem solving skills, they sell diplomas, and so naturally they will emphasis the "earning a diploma" aspect over "learning to solve problems".
STEM courses are all the rage with employers now, I believe, because a STEM diploma has a much better correlation with problem solving skills than do other degrees. I do not think that is an inherent property of the STEM curriculum. My experience is that someone with a liberal arts degree can be just as good of a problem solver as someone with a STEM degree. I think instead that this is an indictment of the current horrid state of liberal arts education.
Note to students: If you desire is to be employable, focus on developing problem solving skills, not on getting a diploma. I don't mean to blow the diploma off completely - it might still be a technical requirement at the (unenlightened) HR departments of the companies for which you want to work. I mean instead that you should be constantly asking yourself "will this course improve my problem solving ability" rather than "will this course help me to graduate". I also mean that you should actively take it upon yourself to practice solving problems. And not just technical problems: business problems, interpersonal problems, societal problems, environmental problems, logistical problems - all kinds of problems. Do you see a piece of litter on the ground - pick it up and put it in the trash bin, and you've just solved a problem. Instead of being arrogant, bitter, angry, or hostile towards people you interact with, trying being kind and understanding, and you're on your way toward solving interpersonal problems. Make up your bed. Wash the dishes. Wash and fold your laundry. Make it your habit to solve common everyday kinds of problems like this and you are well on your way toward solving the bigger problems that employer are willing to hire you for.
Go install some SQL database on your desktop machine and play with it. MySQL, MariaDB, and Postgres are all free and will work on Linux or Windows desktops.
Or, experiment with SQLite. You can download a self-contained standalone precompiled binary that you run as an ordinary command-line program. (ex: "sqlite3 mynewdatabase.db") In fact, sqlite3 is already installed by default on your Mac and probably also on your Linux desktop, so you might not need to install anything at all. There are no servers to set up and maintain and no access permissions and user accounts and passwords to configure. And the database you create is just an ordinary disk file that can delete once you finish experimenting.
All of the databases on your Android and iPhone are SQLite databases, so if you want to look at some real-world data, just upload them and look at them using the sqlite3 command-line tool. You might find other SQLite databases to look at already on your workstation from programs like Firefox, Skype, iTunes, Dropbox, etc.
MySQL, MariaDB, and PosgreSQL are all fine products. But if all you want to do is experiment with the SQL language, they are way, way more complication than you need.
The importance of something like this (assuming the report is true) is for use as an energy storage mechanism, not as a means of "producing" energy.
Imagine a PVC power plant out in the desert someplace. Electricity from the plant is used to generate liquid hydrocarbons that can be stored and burned for fuel for use when the sun isn't shining, or that can be used in circumstances that are necessarily off-grid such as to power an airplane. The "gasoline" thus produced can be thought of more as a battery than as an energy "source". It is merely storing the energy of the sun for later use. And it is completely carbon neutral since the CO2 released when the fuel is burned was taken out of the atmosphere in the first place so there is no net change in atmospheric CO2.
The Achilles's heel of many renewable energy schemes has always been that they are inconsistent and do not generate energy when and where it is needed, and that there is no efficient way of storing the energy for later use. If the reports in this article are true (and that is a BIG IF) then this could be a huge win for renewable energy.
So the idea is sound. The question becomes whether or not the report is real (I have serious doubts) and if it is real, is the efficiency sufficient to make it worthwhile.
Showing the use of a search term in context (i.e. showing a "snippet") is a feature of a concordance - a kind of document that has been produced manually for hundreds of years. So there seems to be lots of prior art.
I've actually *sold* a few of licenses to the public domain SQLite library. Companies call me up and say they want to license the product. I carefully explain that no license is necessary and that they can use it forever for free for anything they want. But they still want a license. So I sell them one. So far, I've sold them cheap. Maybe I should charge more....
This appears to be more of an issue in Europe where, apparently, the concept of "public domain" is less well defined than in the US.
panic: kernel trap (ignored)