103 karma · joined August 14, 2014
The unfilled job number of 6 million is an interesting data point. I'll give them that. But a job does not equal having a good life.
In short, the only data point to take away from this is waste of time. Am I being harsh? Not as harsh as un-empathic, presumptive declarative what people in America need (by the way you need to provide evidence and support to make claims like this at least).
Now I want to know the number of other configs to reduce the number of system calls. This all adds up to being significant the greater the number of hosts in your environment.
The LINQ interpreter on the client would have to retrieve the statistics from the server's tables and indexes of interest and perform the same operation as the optimizer (costing more network and some db cpu). Next it would have to send back the plan to the db executor in some way. This plan "marshalling" would cause more network traffic, requiring the executor to "unmarshall" the plan costing more CPU. This is less efficient than the current scheme.
Alternatively the LINQ language could be implemented on the database but with its own inherent difficulties, but in reverse.
Once a plan is cached and is reused, this inefficiency goes away to some degree. So there could be a possible mechanism for the server to send back to LINQ client a hash identifying the plan if it is cached and then have LINQ only send the hash with parameters to the DB on next execution. (You would have to see if this isn't covered by some patent of course!)
The constraint is the network connection. If the network connection between client and server were faster and bigger than the data bus on the computers, then it would change the equation significantly. But longer distances means slower communication all things being equal (lightspeed and all). So a network connection being better than the data bus would be inefficient and quickly remedied in a competitive marketplace.
On the topic of concept-rightness you quickly veer into a language game. gcc transforms c code into machine code (and may also output error messages, warnings and such). For some, this is not important, and may not be conceptually right. But if you are interested in say the ABI for instance, you do care.
On the point of "fundamentalness of abstraction", I interpret it as a measure of how many layers of abstraction (Ab) can be decomposed into the concrete thing of interest. LINQ generates another layer, that of SQL. If it generated an execution plan and sent that to the database optimizer, then I would say it does not generate another layer and would be equal in level of Ab to SQL.
But if LINQ can generate SQL that runs on the database, then it is also possible for the database to support LINQ natively. And maybe that was the original intent.
However, as it stands today LINQ to SQL costs CPU resources. So in adopting LINQ one of the tradeoffs you are adopting is CPU resources for developer use/benefit of LINQ.
The message here is, well if you don't get a Ph.D., make a lot of money. If you don't make a lot of money, get a patent. If you don't get a patent, at least get published. There are other things that we also want to be able to cultivate other than those I bet.
When a group of geniuses could build a nuclear weapon to take out a whole country, I believe the interest in genius started to spark. Before then, what was the icon of a a genius (I'm thinking before Einstein became iconic)?
The article is interesting, what were the lessons though?
There are other measures of value to society other than STEM publications, income, patents, and Ph.D.s It's often the outliers that don't even fit the Gaussian that are more interesting to me. (Feynman said he scored 120 something on an IQ test.)
As a business I can fully, completely operate without any of the their software, profitably, peaceably, and with at least the same amount of friction or less. And more securely.
If you think otherwise, you are ignorant of the tools available for free and of some intelligently thought-out engineering.
Quality of a language is such a trite, over-used discussion that the results/goals of software are completely forgotten. This too is arrogant ignorance.
How many software engineers are there in the world? It's more than taxi-cab drivers. More than Dr.'s More than teachers. Cooks, farmers, and builders (not combined of course). This is evidence of software for software's sake. There is no quality. Just a moving shell-game of "you need this".
I love writing algorithms--that PowerShell and .NET are some kind of something that will solve people's problems any better than something else is simply marketing. I have a pet rock to sell you.
Knowing an experiment or observation is not repeatable _is_ knowledge that _can be_ useful. What are the causes of non-repeatability? That's even more useful to know.
The observation and experimentation processes of science may be reflexive and would be worth investigating.
The money spent on "science" has created ecosystems where the novel, accidental discovery might be more likely.
The claim that "science" is self-correcting must be supported by evidence.
Finally, the media reporting of science does injustice to scientists by making claims not put forth in publications so frequently, that you are wise to disregard any media reporting of the science, and must go to the paper itself.
For a scientist working incrementally, accumulating data, sieving it for information, fighting for grants, doing administration while making sure family gets three squares, articles like this may cause a wince. But they probably influence support for more funding. Pro scientists I know do not have time to read these articles and will never see them unless it's from someone else, but budding scientists, career-changers, influencers, all get misinformed.
In short, news on science causes long-term damage for short-term gains.
We already have a population that does not work. As of Mar 2016 there are 16.6 million men age 16 to 65 not disabled not in labor force, and 28.2 million women. (44.8 m total) (from: http://www.bls.gov/webapps/legacy/cpsatab6.htm) A lot of those are probably those who gave up though.
Many though are retired or in school. In 2014 ages 55 to 64, 13.8% were retired. (http://www.bls.gov/opub/btn/volume-4/people-who-are-not-in-t...) (Note I consider home responsibilities as working as you would probably have to hire someone to do those if you didn't do them yourself). In 2014, both genders age 25 to 54, 1,479,000 were retired!
As I always say, if we don't split hairs now, we'll be splitting heads later.
But probably more apropos, the laws for H1-B and other hiring processes make it such that you don't want to have any hint of impropriety that would convince a judge the plaintiff would even have a case. Once the judge rules there's a case, you pretty much open up your bank account and settle.
Then there's the counter, if you're so awesome why aren't you my competitor?
To make mice depressed they will do a forced swimming test (poor mice). So this is another way to induce depression: physical+psychological stress.
If there were good science with good funding it's feasible to come up with a lab test for depression--and anxiety--that's very, very accurate.
No, the article is incorrect. It does not have citations either. Explore pubmed for plenty of information. (Keep in mind the sad reality is that even good science is wrong lots of the time--I'm hedging, okay most of the time.)
The risks of not properly treating depression and anxiety is very, very high. So the article is very irresponsible in my opinion.
1) The example rows use first name and last initial for Client primary key attribute (e.g James H.). No one uses this in the real world for a name-based primary key. In fact, in a sufficiently large enough system, you would _never_ use a name for a primary key since names are not guaranteed to be unique.
2) Functional dependencies are interesting ideas. The discussion says that studID (student id) determines address. It would be beneficial to further discuss how we know that. For instance, more than one student could live at the same address. And a student could live at more than one address. So does studID truly determine address? Does the dependent attribute have to be unique? Does the determinant set?
3) The discussion moves from Data(studID, studName, ...) to breaking it out to three entities and says "The following structure is considerably better." But what criteria make it better?
4) It states that "Each student has his own address", but in the real-world that's not _always_ true. There will be cases when a student does not have an address, or the address is still unknown. Also, mailing address and physical addresses can be two different attributes. I'm being picky, right? But these things come up all of the time (so much so it gives me heartburn). So using good examples will help prevent future bad designs I believe.
5) courseID is supposedly functionally dependent on courseName. Again, courseNames can be non-unique in a real school. And courseID domain and range would be important to know whether courseID is unique. For instance there are many 101 courses out there. So is this a sequentially generated ID, a GUID? Only then can we know if it's truly unique.
6) Now to the really good stuff. Functional dependencies are abstractions that exist outside of the database logical and physical design and implementation correct? What if we identified all of the functional dependencies in our entities? Could we generate a good table design automatically from that? How do we prevent from modeling the entire universe and how do we prove that we've over-modeled? (I think one of the stated benefits of relation models is that once, you get to 3NF you can expand the model as needed. So how do we use FDs to determine whether we are 3NF)?
Interesting reduction of FDs to mathematical concepts, but to make it useful to a practitioner, more to go.
2. You ask if it's normal I suspect to see if you would encounter this "style" elsewhere. It's probably more common than not depending on the organizational culture and budget. Older, bigger, companies that bring you in as a "junior" level usually have mentor programs and some even formal.
3. I don't know the answer to that. The word "all" usually is a signal that the answer is no. But to achieve a very high level of expertise probably requires foregoing lots of other learning (i.e. social skills) that other people encounter as they mature. But rotten attitudes can be found everywhere.
3% of what? I would not characterize that as plummeting, but after looking at the graph you linked to, it very much looks like a "plummet".
It doesn't sound like they have a definitive answer of the cause. The data is done by survey, and missed surveys are "imputed". (ftp://ftp2.census.gov/programs-surveys/cps/techdocs/cpsmar14.pdf) So I strongly suspect (but cannot support) there's probably some kind of assumption of a gaussian somewhere, and of course human behavior can assume many different "forms". In other words, I think they should be providing an error rate with these numbers. The other aspect is they probably have faith in the Gaussian I suspect.
The cause of war is not usually taught. It's the events that led up to war that is. http://en.wikipedia.org/wiki/Events_leading_to_the_attack_on...
Is this a fair analogous question?