The acronym STEM breaks down into Science, Technology, Engineering, and Mathematics; and this is a good way of categorizing the different kinds of learning that lie behind really knowing computer science and other STEM disciplines.
A "computer science" degree at an accredited 4-year college should cover topics related to computer science in all four of these areas:
Science: The science behind the technology, including chemistry and physics necessary to implement the technology that is used to build computational devices
Technology: Hardware and software technologies, including: logic gates, CPUs, memory (primary and secondary), communications interfaces, operating systems, compilers, databases, programming languages, etc.
Engineering: techniques for analyzing problems and engineering solutions to those problems (using software, typically)
Mathematics: binary math, formal logic, formal language theory, etc.
All of these together provide the grounding to enable the student, after matriculation, to go forth and do good things. As with all disciplines, the better prepared the student, the more deliberate the graduate's approach to solving problems and being productive.
I have an aquaintance who was (by her own admission and grades) fairly poor at her CS studies, but who was exposed to lots of core computer science STEM material in college. She is now an excellent practitioner/manager in a software development position. She is often frustrated by the plethora of "programmers" (both young and old) who didn't get exposed to the full range of computer science material. They don't know how to think about different ways to solve problems, or what the machine is doing, or how their code is translated into lower level instructions, and this limits their ability. Using tools at a higher level of abstraction is absolutely essential for achieving modern rates of productivity in programming (i.e., Java instead of assembler) but doing so without an understanding and appreciation of what your tools are doing for you is like running a race with blinders on.
I'm sympathetic to some of the ideals of the Tea Party. I believe that the 2nd amendment describes a pre-existing individual right to keep and bear arms for private defense as well as to maintain the security of a free state. I tend to vote conservative. I was aghast at some of the provisions of the Patriot Act and other similar legislation when they were proposed and stunned that they were voted into law.
I am certainly a person, although you may claim that I'm not a "true Tea Party person" because I'm not rabidly foaming at the mouth in support of the entire platform. I was opposed to those programs well before 2009.
I think actual people's beliefs are more nuanced than the overly broad "left wing", "right wing" labels would suggest, and that there are a number of "right wing" folks who are very concerned about privacy and freedom, not willing to trade it away for an illusive security benefit.
I had responsibility for a corporate data network a number of years ago, when cross-country link speeds were substantially lower than they are now. About 80 sites distributed across the US. We charged a flat rate based on number of "subscribers" (network users) at each location to put a location on the network as part of our cost-recovery strategy. The CIO asked me to develop a traffic-based charge instead/in addition to the subscriber charge. We analyzed the situation as follows:
If the source of traffic is charged for providing data to the network, it will limit the services that the source chooses to provide, even if those services are very beneficial to the rest of the network.
If the sink for the traffic is charged for the data it receives from the network, it can cause the sink to be charged for data it didn't request or cause that site to stop using services that create a better overall result for the corporation as a whole.
Locations subscribe to the network because they want access to services and because they want to be able to provide services. Charging by traffic would force providers and consumers into a level of analysis and complexity that would ultimately limit the usefulness of the network, and stifle creativity and growth. On top of that, adding cost-accounting to the network based on traffic would add about 30% to the cost of operating the network.
All kinds of "unfairness" exist in the network world. Our more distant locations thought it very unfair that they had to pay big bucks for a lower speed connection than our customers located at a corporate hub site, even though our actual cost to connect those customers was several times what we charged them, for example. Because we were a corporation, we could decide that the cost of the network was a pooled cost that benefited everyone, and that the best cost-model for the corporation's benefit was the flat-rate subscriber cost regardless of distance.
The commercial world is a little bit different than the corporate world, because the sources/sinks are more polarized (I'm suspect NetFlix puts more traffic onto the network than they pull off of the network). But the arguments seem similar in nature. Consumers on the network are there specifically because they expect to get traffic from providers. Verizon would have a much harder time selling Verizon's services (especially higher download rates) if the rest of the Internet didn't have other firms providing data that Verizon's consumer customers wanted to download. The value of the network is in both the sourcing and sinking of the traffic flows combined. Focusing the accounting on just one direction of flow ignores that value.
Executable content from an uncontrolled source. Sheesh! Why do the folks who design/build entertainment electronics have such a limited understanding of the digital world? Going back to the invention of the Compact Disc as a music medium, the industry consistently demonstrates an inability to think broadly about the opportunities and consequences of the digital world.
People with home networks (i.e., lots of folks) and a TV that permits executable content that was received from an uncontrolled RF source to run on a CPU that has access to the TV's in-home Local Area Network connection will be so screwed it isn't funny.
If all TV's end up with this capability, we'll have to firewall off our TVs from the rest of our home networks. The last thing I need when I get home from work worrying about the unholy intersection of jackass hackers and jackass software vendors is my TV going rogue and hacking into the rest of my carefully secured digital castle through the television.
Is the US government asleep at the switch? Here is the opportunity to nip in the bud a huge threat to national security (ever see how many TVs there are all over all federal buildings these days?). If they can't understand basic Information Systems security enough to understand that executable content MUST be either be from a controlled/trusted source OR MUST be securely isolated from trusted network connections, then we need a new set of policy folks.
One way to stop this idiocy would be to convince the masses that this threat is too great to ignore. If no one buys the TV sets (which are essentially Trojan Horse wormholes), the manufacturers will certainly take notice. If we get the entertainment electronics journalists on board ringing the danger bell, that might put enough of a dent in sales to get their attention.
If I were a student living in one of the rental units, I would want to a) disconnect from restricted access network, b) have the cost credited to me in the form of lower rent, and c) get my own unfiltered Internet access. I think I would even be willing to go to court over it, and maybe even make it a class-action lawsuit.
I would feel the same way if the rental units provided cable TV service, but chose to limit access to certain freely available channels (i.e., local terrestrial broadcast stations), or of the rental units provided a shared FM antenna system but chose to restrict or control access to certain FM radio frequencies.
Whether the FCC has gotten around to making it legally so or not, access to the Internet should be provided as a common carrier service. The intermediaries (such as the rental company in this case) should not be able to try to get a cut of the action above and beyond simply recovering the cost of the service in the rent.
That's my opinion, however. I'm sure others have their own. What the people who control the rental units should bear in mind is that others may share my opinion, and if enough of them do it could get very sticky for them. Restraining people's access to freely available media doesn't go over well.
My original comment wasn't based on subletting, it was based on the transient nature of a hotel/motel/B&B guest as opposed to a neighbor (regardless of whether the neighbor owns/rents/sublets).
There is a wide range of what is acceptable to various people in this context. For some, not knowing who their neighbors are from day to day may not be a big deal. Maybe they like forming new associations constantly, or maybe they avoid forming any associations. Either way, they don't care if the people around them are the same as yesterday or will be the same tomorrow. Others like more constancy in their associations, especially those who are around them when they are most vulnerable (i.e. at home where a lot of relaxing, bathing, and sleeping takes place). It is a tribute to society that many of us feel safe in a variety of circumstances that leave us vulnerable to those around us. We don't feel like we have to live with armed guards, nor constantly watch our backs to make sure someone isn't putting a knife into it. But how comfortable you are in the presence of strangers when you are vulnerable depends a lot on your level of trust in others and/or your ignorance of what can go wrong.
I think people usually expect and operate with the default assumption that the people around them are mostly like themselves, and they govern their actions accordingly. Short-term transient rentals will almost certainly play havoc with those assumptions on both parts. The "inconsiderate assholes" who show up late at night for their AirBnB accommodation probably aren't assholes at all. Their travel was delayed, they are tired and worn out, and they just want to get to a touchdown/relaxation spot. But their assumptions about what constitutes "good behavior" under those circumstances are very different than those of the long-term residents around them think, because they have very different expectations and motivations.
I'm familiar with a circumstance in which the equivalent business to a short-term rental opened in a very small neighborhood (private road off of a county road, six houses). This business has 24 hour a day operations, 7 days per week, with at least 3 employees per shift. Obviously way above/beyond AirBnB of course. The culture clash is enormous. For example, the employees speed down the road when they are late for work (and its not uncommon for people to be running late in the morning). Because its a private road, its only 18 feet wide, not the minimum 22 feet of a county road. The residents know each other, and always slow down to pass each other. The employees don't slow down a bit; I suspect they don't realize the road is as narrow as it is. I'm sure the employees don't understand why the neighbors dislike them so much - they are just working for a living, like everyone else, right? But unlike the residents, there is no tie of the employees to the neighborhood. Its just their job, not where they live.
Those who can, do; those who can't, write. Those who can't write work for the Bell Labs Record.