479 karma · joined May 13, 2016
10 million who are not involved in the slightest and would not even know about this without seeing it in the news.
So your argument is, since x billion (not just million) people don't know something we can already conclude it doesn't exist.
I'm attacking your numbers argument, nothing else.
And your "someone will always disagree" is completely out of place - it's true about about something not present in this story at all. So by throwing in some random true fact you made your 2nd argument.
Last, the comparison with "climate deniers" (others in this thread) is bogus too: The difference is that topic was WAS discussed at great length - and the "deniers" did get heard. So yes, after hearing all sides there is no need to give everyone equal time. In this story however we hear about it for the very first time, and while I certainly don't expect to give them equal time for their views, and personally would not bother one iota, it makes me wonder:
What happens when we hear such stories and always automatically assume they are wrong? For me it's not about this one single story, but how we handle such stories in general. Always throwing the "majority opinion" view around seems misguided. I'm not much concerned about this particular case, but about the generalities thrown around here like the the "10 million people" argument above. Just because those people are sick doesn't make your justification/reasoning correct - somebody else being wrong doesn't make you right automatically!
What do you mean? This is like saying "The only reason you use a towel is to get dry", implying "you are a cheater". Yes, towels are to get you dry, and yes, it is "This is nothing more than a negotiating ploy". I don't get why one would use the word "ploy" here as if something cunning that few people notice or understand is happening.
But it certainly makes it more accessible!
Myself for example, as a CS degree holder and IT consultant, over the last few years I received quite an education in anatomy, physiology, statistics (focus on medicine, biology and public health), chemistry, org. chemistry, medicinal chemistry (drug development), neuroscience, etc. Several hundreds of hours of lectures. Plus lots of others like history of architecture, "first nights" from Harvard (classical music, several courses), equine care, equine nutrition, Apacher Spark (Berkeley courses), and a lot more.
There is no way on earth I could have learned much esp. about the medical subjects any other way. You have to be really, really dedicated to try to put the pieces together just from random sites Google gives you - that's more for when you already are deep(er) into a subject and need something specific. You can of course, but since I have a life effort/benefit analysis would prevent one from doing so.
cd /D/Videos/Courses/
./coursera-dl/coursera-dl -u <<email>> -p <<password>> compilers-004Sure it weeds out "non-programmers" - any programming task (more than "Hello World") does. But how many people who are good programmers and just suck a) under pressure, b) especially when surprised are falsely out-selected?
I once failed to answer what a right join is. I got the (freelancer) job anyway - and of course I knew all along what that is, but when I got that question I had not used any joins in years (doing infrastructure work instead), and under interview pressure I can't think except along narrow lines. I ended up doing most of the complicated SQL queries in the department, with people coming to me because to me that was easy. After failing a very simple interview question on joins.
b) ignore everything else until you are done
c) repeat
Don't worry that at your pace it will take ages - very soon you will develop an idea how to rank what you should look at next. If you don't, go back to a).
Obviously it's useless to think about it too much when your knowledge about a subject consists mostly of holes and gaps, so first gather data (a).
I can't quite see how concrete your question is, but try Khan Academy. Follow the suggested order if you have no preferences.
And no, debt does NOT have to be paid back. It can be rolled over indefinitely, or, if demands on "payments" really are an issue just go bankrupt. NOT A JOKE. It happened A LOT. I myself - and I'm not that old - have seen three currencies in my country in my life (Germany), my grandparents more. Germany is a horrible 3rd world place... no?
What are people going to do when all they get is "sorry, no more payments on the old debt. Are they going to emigrate to Alpha Centauri? Are they going to refuse to live from now on? No, they will grumble and get back to doing what they've been doing all the time. As long as the government is strong etc. Plenty of examples - see Germany. No that doesn't lead to Argentina - only Argentina leads to Argentina. A countries industry, culture, people, government don't suddenly stop working just because the currency is changed and old debts forgiven. Money does not exist, it's a made-up concept.
> we can't claim that we have an abundance of money - quite the opposite.
Uhmm... what should I tell someone like you? Except to repeat:
Money does not exist, it's a made-up concept.
Guess what happened after the financial crisis - we invented a trillion dollars. Out of nowhere. Suddenly it was there.
Example: Describing the laws of physics doesn't give any description of whether you stand in a wasteland or in a paradise. Either one is built upon the same rules. The rules the article mentions don't rule out the worst much-less-than-cooperation outcomes.
Think about it: Do we really, in the US of A or anywhere in the 1st world countries, have a lack of resources? In the 21st century? With hardly anyone actually working on the basics the population needs, like food, because our productivity is through the roof?
And "money" only is an issue when humans decide it is - it is an entirely made-up concept represented only in bits in computers (never mind that little bit of printed money, which can be produced at will too).
We do pay a huge amount of people in both private and public sector to do useless work. See dilbert.com cartoons and their popularity, and the results of research into the mood of working people, a huge amount of them thinking their work is useless to society or even just their own company.
The feeling (and reality) that we all have to work hard to get by is mostly an artificially created system outcome. With the productivity levels we have achieved, and the tools and knowledge at our disposal, we should have plenty of room for experiments.
(That's the comment when you answer the quiz correctly.)
What a simplification. I'm all for the chickens, but the quiz and this quiz-answer-comment make it seem a little too easy.
If you want to sell 250 chickens a year you a) need quite a few more than that, b) you need SPACE - and it should provide plenty of free food for hundreds of chickens (so, LOTS of space), and c) the more chickens the higher the risk of disease, and several hundred chickens is <i>a lot</i> of chickens for a poor guy, d) if you don't have LOTS of space you will need to get food from somewhere (and pay for it?).
For people without an argument. Because then you would have to know what those firms actually do.
Read this: http://flyingfrogblog.blogspot.de/2010/05/why-is-haskell-use...
It's from 2010 so things may be different - but it illustrates that you can't just drop names, you have to do your research.
I have no intention of defending MongoDB because what do I know, never worked with it in real life - but just out of curiosity I took the free courses they offer (https://university.mongodb.com/) and I find that a sizable share of the complaints about MongoDB come from people who don't seem to have learned much about the product they are using. It's like people complaining their new truck behaves badly in water.
A lot of critics seem to have chosen MongoDB when they needed a SQL DB from day one. If you need full flexibility to (re)combine data you need SQL, for example. A document store isn't "schema-less" at all - much of the schema is built-in and very inflexible after that.
That is an unanswerable question since it's about everything. "NoSQL" is a huge variety of techniques - many of them yet to be invented, that only have one thing in common: "not SQL". From document storage over key/value storage to graph databases. Anyone who tells you what they think "about NoSQL" either has to redirect the question to become a useful one, or if they actually attempt to answer it take your popcorn and expect entertainment at best.
"Types and examples of NoSQL databases" - https://en.wikipedia.org/wiki/NoSQL#Types_and_examples_of_No...