No. In fact, Hell, no. If you don't understand the electoral college and it's benefits, you don't understand America.
The electoral college is serving the exact purpose it was intended to serve. Without the Electoral College, those who live in cities slowly drive the rural areas toward poverty and slavery and resource deprivation.
See, there are two district groups of people. Those in a big city and those out of a big city. It is very difficult for either to understand the other. The Big City people already have the advantage on numbers. But they have no clue about life outside the big city. Our rural areas, especially our farmers, are critical to big city life in ways those who live in the big city don't understand. The rural people have an insight that most people who live in the city never can understand.
Even with the Electoral College, the large metropolitan cities in California and New York and other states have massive power, perhaps more than they should.
Before we remove the electoral college, we should stop having 100% of the state's electoral college go one candidate. Each Electoral college vote should represent an area. In California, there are areas that are 90% republican, but their voice gets stomped on by the rest of California. California has 55 electoral college votes.
The grouping of electoral college votes has helped further the terrible two party system. Without grouping the electoral college, it would be more likely that another party or an independent could win some electoral college votes, which would encourage more diversity in thinking.
I have a Surface Pro 3. When I first got it, I could watch a full video or stream ESPN for hours. I've watched a whole 4 hour NCAA Football game streaming, when it was at full power.
I can work on battery with no power for more than half the day, running Visual Studio. I can't quite work the whole day, starting at 9am around 3:30 to 4 PM, I am out of battery. If I plug it in while going to lunch, I then work the second half of the day on battery no issues.
It is now 2-1/2 years old.
So, while it is not as long lasting as my Kindle tablet, it is far more long lasting than any laptop I've ever owned.
It is also my favorite computer, ever. There is a reason that the Surface Pro is so popular. It lives up to its hype.
If we need less water in the ocean, that means we need more water on land. So why don't we move it there?
We have many deserts. Sahara, Gobi, Southwest US, etc.
We pipe oil all over the world, why not water. The Great Salt Lake in Utah (I am from Utah) is extremely low and depleted. Why not pipe salt water to it. It might not seem to make a dent at first, because filling the Great Salt Lake wouldn't change the Ocean levels. But remember, the Great Salt Lake only losses water to evaporation that fills the Rocky Mountains with snow. The glacier/snow packs in the Rocky Mountains are depleting, too, partially because of lack of precipitation, which is partially because of a decreasing Great Salt Lake. So the more water in the Great Salt Lake, the greater the snow packs. Over the next 20 years, the difference would be noticeable.
Now, why can't we make more Great Salt Lakes. Why not put an Ocean in Death Valley. Death Valley is 200+ feet below see level, just build a pipe. Now you can pipe from Death Valley to the Great Salt Lake as it is closer than the Ocean. Now their is more rainfall in the entire southwest.
Now do the same in the Sahara desert. Add an ocean lake on the west side of the Sahara. How much more rain will that provide to the Sahara? Instead of a desert that soaks up heat and does't contribute to our atmosphere, we would have more rainfall and more plants, which would lead to more transfer of green house gasses to oxygen. We could make the Sahara inhabital, even farmable.
Next the Gobi.
Obviously I am talking about major world projects that are expensive and could take twenty years to implement. But so, what? Should we not start just because it will take a long time?
They day you stopped learning is the day you become a legitimately "aged" developer.
In my experience, the bias against "aged" developers has been justified, not because of age, but because of complacency. The problem with some "aged" developers (I am turning 40) is that they stopped learning and rely only on existing knowledge for solutions.
In this industry, there are two types of knowledge: 1. The type that changes quickly: language, syntax, libraries, maven/nuget packages tools, IDEs, plugins, code generators 2. The type that never gets old: good coding practices, architecture, design patterns, decoupling, vast experience, etc.
Young developers usually stay up update to date on the first type, while slowly growing the second type. Usually, a young coder writes their code more quickly and delivers faster, but their code is sometimes less maintainable because of lack of the second type of knowledge. Aging developers have built up a good store of the second type of knowledge and have learned the first type of knowledge for so long they think they are done.
So some developers give up on the first type of knowledge, become complacent in their first type of knowledge. This is when I would say they have "aged".
Some times these "aged" developers get bitter when a young developer outshines them on the first type of knowledge. I used to do that to old developers all the time. Some of them would try to outshine the young developer with the second type of knowledge. When you do this, instead of bridging the knowledge gap together, you increase the rift. Accept that the young developers are better at the first type of knowledge. Embrace it, cheer it on, and let them go with it. But steer their exuberance with your second type of knowledge. Let them share with you their first type of knowledge, so you learn, then enhance what they taught you with your second type of knowledge, so they learn.
The best developers, the ones who become rockstar developers are usually the ones who are over 40, have a ton of the second type of knowledge, but also keep on the first type of knowledge.
See, no matter how long you have been developing, your current skill level shouldn't be what you use for each project. The world of dev changes every year. You don't need to know everything, but you need to know how to learn.
All developers of any age need to start every iteration/spring with learning time.
Learning Steps 1. Crowd Source.
- What is the current development world doing in regards to your solution?
- Of those, which have stuck and why? 2. Has anything new been released that can help you with your current solution. 3. Choose the technology: language, framework, architecture, design patterns, etc. 4. Are there any tools, IDE plugins, etc, that will automate boiler plate code for what I am doing? 5. Would it be faster to write a tool to generate the code or to write the code?
Only then should you implement the work in your iteration/sprint.
If you do this for every sprint/iteration, you will deliver much faster. It seems like learning will add time to your overall solution. It doesn't. It might not save time in every sprint, but in any given year it could save weeks to months of time. Your delivered solutions will feel up-to-date not because you used some new fangled thing shiny toy, but because you increased your toolbox with better tools before you started and used better tools.
Also, since you never stop learning, you never become an "aged" developer.
Yes, agism exists. But I think you will find that it is rare. More often than not that the interviewer noticed during the interview that the candidate has stopped putting effort into learning the first type of knowledge.
First, checking credentials in a border state should be standard practice for all border states, especially when illegal immigration has proven a problem, which for the southern border, it is, whereas for the northern border, Canada, not so much.
Second, the bordering country is Hispanic. So targeting Hispanics is not racist, it is properly targeting the demographic of the bordering country. Arizona doesn't border the Netherlands, it border Hispanic Mexico.
Third, I thinks "racist" and "statistically likely" are being confused. If you are in Arizona, look Hispanic, then the there is a 1 in 7 chance that you are illegal. The 1 in 7 comes from the fact that there is an estimated 2.1 million Hispanics and of those, and estimated 300k are illegal immigrants. Most legal immigrants can speak some English, so if the immigrant can only speak Spanish, the likelihood an individual is illegal is almost double, or 1 in 3 or 1 in 4. So a street check would be effective in finding an illegal alien 12 to 33% of the time. This makes that option viable. Note: Search the internet for Arizona population stats are there are various different ones but these stats demonstrate the point.
However, the number of illegal aliens who are white Caucasian is so small it isn't even estimated. So checking whether a Caucasian is illegal or not would be effective as the ratio is maybe 1 in 10,000 or even 1 in 50,000.
So if you have a method that is effective 1 in 8 times in a border state, use it.
The problem is that people don't think logically. They just listen to the biased media that is more interested in click-bait than actual facts. Do you see how statistics and common sense completely blow the "racist" fallacy out of the water?
The number of women in computing is a statistic, not necessarily a problem.
This article is suggesting that we solve a statistical different without first proving that the statistic indicates a problem in need of solving.
Personally, I want more women in computing, especially dev, because, well, women are awesome. So awesome, I married a woman.:-) Also, I personally feel that a feminine perspective can be beneficial to many dev projects, but I have not data to back up my personal feeling.
Well, 100% of planets we humans have set foot on have intelligent life.:-) Unfortunately 100% of the moons humans have set foot on did not have intelligent life.
Many Americans don't want either candidate. Actually the best solution is to vote for an independent this year.
If an independent can win enough of the electoral college votes so that neither Trump or Hilary have 270 electoral college votes, then the House gets to pick from the top 3.
If the US voters can create this scenario, then we can avoid either of these two terrible candidates.
I believe the Republican majority House of Reps won't pick Clinton because she is a democrat and, well, evil. They won't pick Trump even though he is democrat. So the independent is in.
Actually, no. That is not true. You obviously haven't been part of the review process much. There are many types. Reviews happen, first an foremost because: 1. Amazon (or the company) requests them. With every purchase about two later, I get an email asking me to review. A certain % of people, most who are not basement dwellers, will take time to respond. 2. The product caused an extreme emotion: This usually isn't a large percentage. The customer either really liked the product, or really hated the product. The reason so many reviews are high, is because it is actually an extremely small percentage of customers that are so angry they want to throw the product a 1 star. 3. Bloggers/Reviewers as a business. 4. A small percentage of people that just get pleasure from being a top reviewer and do it as a hobby. (Kind of like the same people who post here or on Stack Overflow, who get nothing out of it but virtual prestige).
I would say basement dwellers aren't even on the list of measurable percentages.
But your statistics are missing all kinds of relevant data. Let's assume all candidates are scored from 0 to 100. Then let's add some additional data points:
Data Point 1 - Referrals A referral is like a +5 bonus to the candidate's scoring. Divide the resumes into two groups: 1. referred, 2. not referred. Were any of the Asians referred? If an unreferred candidate gets a 90, that is pretty good. Another resume would have received an 86, but it included a +5 referral bonus. So it is a 91.
Data Point 2 (A big one) - Social/Soft/Communication Skills Add Social/Soft/Communication Skills aspects to candidates.
Asians often have communication issues. To start with, for many, English is a second language (ESL). ESL candidates must prove that they can: 1. Speak clearly enough to be understood. 2. Write clearly enough to be understood.
Many ESL candidates have accents. Having an accent is not necessarily a problem. Having an accent is not a justifiable reason to exclude someone. However, the candidate has an accent so thick that it makes it difficult for coworkers/customers to understand, then that is a problem. Being unable to communicate clearly IS a justifiable reason not to hire some. As it turns out, some Asians have difficult to understand accents.
Many ESL candidates are not fluent, even when they claim to be. They may say or write sentences that don't make sense. For example: "I have a doubt about your product." What does this mean? In English, it means there is doubt the product will do what it says it will do. However, if you talk to this ESL person, you will see that they meant, "There is something about your product that I don't understand." Those are two completely different statements. The ESL person who used the word "doubt" clearly was not fluent in English.
If you can't speak English well enough to be understood, you cannot consider yourself fluent. You may be able to read and write fluently, but in speaking fluently includes pronunciation and being understood. Not being fluent or being only partially fluent in English is a valid reason not to hire some one.
I recommend that any English as a Second Language person with an accent problem takes a class on phonetics and work with a speech therapists at least until their accent is good enough. Also, I recommend that they read books (both fiction and non-fiction) out loud in English. Working in a second language is tough.
So a difficult to understand accent, or not being truly fluent could be anywhere from a -1 to a -100 (so bad of an accent they are un-hireable) in the 0 to 100 candidate scoring system.
Data Point 3 - Citizenship Were all the Asian candidates citizens? Choosing a citizen over a non-citizen is not discrimination. How many of the Asian candidates are non-citizens?
There are probably a dozen or so more data points to add.
For rapid development in Business Apps environments, I recommend C#.
I first learned in Java because Java is the most taught language in schools. Newbies, like college students, do the most searching on the web. That sways the stats to make Java look way more popular than C#. However, multiple checks for available jobs have shown C# to have as many or more jobs that Java. Also, the # character just isn't handled by everything as well as it should be and makes C# stats inaccurate. The # character causes a lot of C# stats to be lost and/or not properly counted.
IDE: Visual Studio is so far beyond other IDEs, nothing else even half as good. Maybe not even 1/3 as good. The free version of Visual Studio takes away any issues that used to exist, such as it being too expensive. Language: C# has a lot of features and is fast to code in. Mobile: With C# (using the now free Xamarin library), one can write mobile Apps for iOS, Android, and Windows. C# provides the best native cross platform development experience for mobile apps out there. Web: Whether you do WCF or WebAPI or MVC, you have some great options for coding the backend and frontend in C#. Though you can't completely get away from JavaScript for front end. Verbosity: I write less code in C# to do the same things in Java and C#. Buzz:.NET Core and the open source of.NET Core is creating a lot of buzz.
Oracle is not pushing Java forward like it needs to be pushed. If Android hadn't based it's primary language on Java, Java would be following Open Office into its slow demise.
The language you write in most is the most popular language to you.
If you work in Java, C#, or C++, you will have plenty of jobs available. If you know two of them and have descent coding skills you will be head hunted constantly.
Knowing multiple languages makes you better.
English is my first language, but I learned Spanish as my second language. I didn't fully understand many of the grammar and other language concepts in English until I learned Spanish. Learning Spanish helped my English more than the study of English did.
Likewise, I didn't fully understand delegates and events in C# until I really started coding in JavaScript, a language that is extremely callback heavy, so much so that JavaScript can lead one to call back hell. Each language takes advantage of different features and logic and do so in different ways. Seeing how two different language implement the same feature actually helps you better understand the concept, not just use the code without fully understanding it.
So which language is popular doesn't matter. If you know two languages or more well, and can solve problems, you can probably be successful in any language.
Are you kidding. Most Americans are living the American dream and most American's are rich.
The problem is that many have changed the definition of rich. The idea of keeping up with the Jones is real, you just don't fully understand the extent of it and that most poeple are guilty of it even if we think we aren't.
In the middle ages, if a person owned land and had a livable building on it, and could self-sustain them and their family (at least two meals a day even if meager at time) from the land, that person was rich. They were probably a Lord, even if they couldn't afford servants.
Now, we have people who own land, a home, eat two or three meals every day, have their kids going to school, have electricity, one used car, refrigerators, hot water heaters, warm showers, soft beds, plenty of blankets, a couple TVs, a cable TV package. But they have four kids in only two bedrooms (can you believe they are sharing a room) and the household makes less than 50k a year. They can't get their kids phones. Some say that family is in poverty, or that family is incorrectly termed "lower middle class".
If you compare that family to the rest of the word, the way the other 7 billion people live, most in 3rd world countries, then that family isn't just rich; they are loaded. They have way more than they need. That family isn't just seeking the american dream, they have found it!
You see, over time "nice-to-haves" such as a car, a phone of any type, computers, tablets, game consoles, expensive diets, perfect grass in the yard, and many other things have slowly become so ubiquitous that you forgot that only the top 10% of the
With internet and IT tech we are improving many aspects of the world by: 1. Improving communication world wide. 2. Improving entertainment world wide. 3. Improving education world wide. 4. Make banks and credit card readers available online to everyone (so even poor person from a 3rd world small town can run a business) etc.
With DNA/Gene manipluation we are trying to end world hunger: 1. Creating GMO food that can grow where no plant has grown before. 2. Determining causes of diseases and how to stop them 3. Finding ways to kill weeds without pesticide etc.
The quote is intended to isolate everything inside it, and by definition, the punctuation is not part of what is quoted. Living in the US, I rebel and put the punctuation after the quote all the time.
Your solution, to bug the Unicode Consortium, is the best solution I've ever heard.
Great example of something that is a valid use case.
Issue: Don't hit kids
You are assuming a car has to solve the problem the way you are solving it. You don't see the kids, but you guess they might be there by the open garage. So you drive slower. Why would a computer do that?
A self-driving care could be equipped with an infrared sensor and doesn't have to wonder if kids are nearby. It doesn't have to guess that their might be kids by open garages. The 360 degree sensor detects all warm life in the vicinity, tracks those heat signals movement at submillisecond speed, and makes sure not to hit any of the heat signatures without even having to slow down. So not only is the problem solved better, it doesn't require slow driving so things have improved.
Slashdot Mirror
No. In fact, Hell, no. If you don't understand the electoral college and it's benefits, you don't understand America.
The electoral college is serving the exact purpose it was intended to serve. Without the Electoral College, those who live in cities slowly drive the rural areas toward poverty and slavery and resource deprivation.
See, there are two district groups of people. Those in a big city and those out of a big city. It is very difficult for either to understand the other. The Big City people already have the advantage on numbers. But they have no clue about life outside the big city. Our rural areas, especially our farmers, are critical to big city life in ways those who live in the big city don't understand. The rural people have an insight that most people who live in the city never can understand.
Even with the Electoral College, the large metropolitan cities in California and New York and other states have massive power, perhaps more than they should.
Before we remove the electoral college, we should stop having 100% of the state's electoral college go one candidate. Each Electoral college vote should represent an area. In California, there are areas that are 90% republican, but their voice gets stomped on by the rest of California. California has 55 electoral college votes.
The grouping of electoral college votes has helped further the terrible two party system. Without grouping the electoral college, it would be more likely that another party or an independent could win some electoral college votes, which would encourage more diversity in thinking.
Yes. Yes, we are worth it and we prove our worth time and time again.
Why is this news? This is a standard open source practice, to fork and change/improve.
Good work developer. Good use of Open Source.
Also, Meta-bills are a terrible design. All bills should fit on one side of one sheet of paper 8-1/2" by 11" paper, with 12 pt font.
If you want a 2000+ health care bill, then you would have 2000 separate bills.
This would prevent a lot of corruption.
I have a Surface Pro 3. When I first got it, I could watch a full video or stream ESPN for hours. I've watched a whole 4 hour NCAA Football game streaming, when it was at full power.
I can work on battery with no power for more than half the day, running Visual Studio. I can't quite work the whole day, starting at 9am around 3:30 to 4 PM, I am out of battery. If I plug it in while going to lunch, I then work the second half of the day on battery no issues.
It is now 2-1/2 years old.
So, while it is not as long lasting as my Kindle tablet, it is far more long lasting than any laptop I've ever owned.
It is also my favorite computer, ever. There is a reason that the Surface Pro is so popular. It lives up to its hype.
If we need less water in the ocean, that means we need more water on land. So why don't we move it there?
We have many deserts. Sahara, Gobi, Southwest US, etc.
We pipe oil all over the world, why not water. The Great Salt Lake in Utah (I am from Utah) is extremely low and depleted. Why not pipe salt water to it. It might not seem to make a dent at first, because filling the Great Salt Lake wouldn't change the Ocean levels. But remember, the Great Salt Lake only losses water to evaporation that fills the Rocky Mountains with snow. The glacier/snow packs in the Rocky Mountains are depleting, too, partially because of lack of precipitation, which is partially because of a decreasing Great Salt Lake. So the more water in the Great Salt Lake, the greater the snow packs. Over the next 20 years, the difference would be noticeable.
Now, why can't we make more Great Salt Lakes. Why not put an Ocean in Death Valley. Death Valley is 200+ feet below see level, just build a pipe. Now you can pipe from Death Valley to the Great Salt Lake as it is closer than the Ocean. Now their is more rainfall in the entire southwest.
Now do the same in the Sahara desert. Add an ocean lake on the west side of the Sahara. How much more rain will that provide to the Sahara? Instead of a desert that soaks up heat and does't contribute to our atmosphere, we would have more rainfall and more plants, which would lead to more transfer of green house gasses to oxygen. We could make the Sahara inhabital, even farmable.
Next the Gobi.
Obviously I am talking about major world projects that are expensive and could take twenty years to implement. But so, what? Should we not start just because it will take a long time?
They day you stopped learning is the day you become a legitimately "aged" developer.
In my experience, the bias against "aged" developers has been justified, not because of age, but because of complacency. The problem with some "aged" developers (I am turning 40) is that they stopped learning and rely only on existing knowledge for solutions.
In this industry, there are two types of knowledge:
1. The type that changes quickly: language, syntax, libraries, maven/nuget packages tools, IDEs, plugins, code generators
2. The type that never gets old: good coding practices, architecture, design patterns, decoupling, vast experience, etc.
Young developers usually stay up update to date on the first type, while slowly growing the second type. Usually, a young coder writes their code more quickly and delivers faster, but their code is sometimes less maintainable because of lack of the second type of knowledge.
Aging developers have built up a good store of the second type of knowledge and have learned the first type of knowledge for so long they think they are done.
So some developers give up on the first type of knowledge, become complacent in their first type of knowledge. This is when I would say they have "aged".
Some times these "aged" developers get bitter when a young developer outshines them on the first type of knowledge. I used to do that to old developers all the time. Some of them would try to outshine the young developer with the second type of knowledge. When you do this, instead of bridging the knowledge gap together, you increase the rift. Accept that the young developers are better at the first type of knowledge. Embrace it, cheer it on, and let them go with it. But steer their exuberance with your second type of knowledge. Let them share with you their first type of knowledge, so you learn, then enhance what they taught you with your second type of knowledge, so they learn.
The best developers, the ones who become rockstar developers are usually the ones who are over 40, have a ton of the second type of knowledge, but also keep on the first type of knowledge.
See, no matter how long you have been developing, your current skill level shouldn't be what you use for each project. The world of dev changes every year. You don't need to know everything, but you need to know how to learn.
All developers of any age need to start every iteration/spring with learning time.
Learning Steps
1. Crowd Source.
- What is the current development world doing in regards to your solution?
- Of those, which have stuck and why?
2. Has anything new been released that can help you with your current solution.
3. Choose the technology: language, framework, architecture, design patterns, etc.
4. Are there any tools, IDE plugins, etc, that will automate boiler plate code for what I am doing?
5. Would it be faster to write a tool to generate the code or to write the code?
Only then should you implement the work in your iteration/sprint.
If you do this for every sprint/iteration, you will deliver much faster. It seems like learning will add time to your overall solution. It doesn't. It might not save time in every sprint, but in any given year it could save weeks to months of time. Your delivered solutions will feel up-to-date not because you used some new fangled thing shiny toy, but because you increased your toolbox with better tools before you started and used better tools.
Also, since you never stop learning, you never become an "aged" developer.
Yes, agism exists. But I think you will find that it is rare. More often than not that the interviewer noticed during the interview that the candidate has stopped putting effort into learning the first type of knowledge.
First, checking credentials in a border state should be standard practice for all border states, especially when illegal immigration has proven a problem, which for the southern border, it is, whereas for the northern border, Canada, not so much.
Second, the bordering country is Hispanic. So targeting Hispanics is not racist, it is properly targeting the demographic of the bordering country. Arizona doesn't border the Netherlands, it border Hispanic Mexico.
Third, I thinks "racist" and "statistically likely" are being confused. If you are in Arizona, look Hispanic, then the there is a 1 in 7 chance that you are illegal. The 1 in 7 comes from the fact that there is an estimated 2.1 million Hispanics and of those, and estimated 300k are illegal immigrants. Most legal immigrants can speak some English, so if the immigrant can only speak Spanish, the likelihood an individual is illegal is almost double, or 1 in 3 or 1 in 4. So a street check would be effective in finding an illegal alien 12 to 33% of the time. This makes that option viable.
Note: Search the internet for Arizona population stats are there are various different ones but these stats demonstrate the point.
However, the number of illegal aliens who are white Caucasian is so small it isn't even estimated. So checking whether a Caucasian is illegal or not would be effective as the ratio is maybe 1 in 10,000 or even 1 in 50,000.
So if you have a method that is effective 1 in 8 times in a border state, use it.
The problem is that people don't think logically. They just listen to the biased media that is more interested in click-bait than actual facts. Do you see how statistics and common sense completely blow the "racist" fallacy out of the water?
My next phone will be the surface phone. I am just waiting for it to release.
The number of women in computing is a statistic, not necessarily a problem.
This article is suggesting that we solve a statistical different without first proving that the statistic indicates a problem in need of solving.
Personally, I want more women in computing, especially dev, because, well, women are awesome. So awesome, I married a woman. :-)
Also, I personally feel that a feminine perspective can be beneficial to many dev projects, but I have not data to back up my personal feeling.
Non-techies complaining about tech? Wow! Unprecedented.
Some have made this to be Surface vs iPad. It is not.
From what I have heard, the problems were with WIFI and not the tablets themselves. The device is almost always blamed for network issues.
From what I've read, the problem is "Tablet" vs "Paper" not type of tech.
Well, 100% of planets we humans have set foot on have intelligent life. :-)
Unfortunately 100% of the moons humans have set foot on did not have intelligent life.
What about a Square-card-reader-sized scanner that connects to your phone and can analyse blood, or a skin or hair sample.
Sorry, I meant "they won't pick Trump even though he is Republican."
Many Americans don't want either candidate. Actually the best solution is to vote for an independent this year.
If an independent can win enough of the electoral college votes so that neither Trump or Hilary have 270 electoral college votes, then the House gets to pick from the top 3.
If the US voters can create this scenario, then we can avoid either of these two terrible candidates.
I believe the Republican majority House of Reps won't pick Clinton because she is a democrat and, well, evil. They won't pick Trump even though he is democrat. So the independent is in.
Here are two independent options:
Evan McMullin - https://www.evanmcmullin.com/ https://www.johnsonweld.com/
I hope others like me make a statement this election and vote for neither Trump or Hilary.
Actually, no. That is not true. You obviously haven't been part of the review process much. There are many types. Reviews happen, first an foremost because:
1. Amazon (or the company) requests them. With every purchase about two later, I get an email asking me to review. A certain % of people, most who are not basement dwellers, will take time to respond.
2. The product caused an extreme emotion: This usually isn't a large percentage. The customer either really liked the product, or really hated the product. The reason so many reviews are high, is because it is actually an extremely small percentage of customers that are so angry they want to throw the product a 1 star.
3. Bloggers/Reviewers as a business.
4. A small percentage of people that just get pleasure from being a top reviewer and do it as a hobby. (Kind of like the same people who post here or on Stack Overflow, who get nothing out of it but virtual prestige).
I would say basement dwellers aren't even on the list of measurable percentages.
But your statistics are missing all kinds of relevant data. Let's assume all candidates are scored from 0 to 100. Then let's add some additional data points:
Data Point 1 - Referrals
A referral is like a +5 bonus to the candidate's scoring.
Divide the resumes into two groups: 1. referred, 2. not referred.
Were any of the Asians referred? If an unreferred candidate gets a 90, that is pretty good. Another resume would have received an 86, but it included a +5 referral bonus. So it is a 91.
Data Point 2 (A big one) - Social/Soft/Communication Skills
Add Social/Soft/Communication Skills aspects to candidates.
Asians often have communication issues. To start with, for many, English is a second language (ESL). ESL candidates must prove that they can:
1. Speak clearly enough to be understood.
2. Write clearly enough to be understood.
Many ESL candidates have accents. Having an accent is not necessarily a problem. Having an accent is not a justifiable reason to exclude someone. However, the candidate has an accent so thick that it makes it difficult for coworkers/customers to understand, then that is a problem. Being unable to communicate clearly IS a justifiable reason not to hire some. As it turns out, some Asians have difficult to understand accents.
Many ESL candidates are not fluent, even when they claim to be. They may say or write sentences that don't make sense. For example: "I have a doubt about your product." What does this mean? In English, it means there is doubt the product will do what it says it will do. However, if you talk to this ESL person, you will see that they meant, "There is something about your product that I don't understand." Those are two completely different statements. The ESL person who used the word "doubt" clearly was not fluent in English.
If you can't speak English well enough to be understood, you cannot consider yourself fluent. You may be able to read and write fluently, but in speaking fluently includes pronunciation and being understood. Not being fluent or being only partially fluent in English is a valid reason not to hire some one.
I recommend that any English as a Second Language person with an accent problem takes a class on phonetics and work with a speech therapists at least until their accent is good enough. Also, I recommend that they read books (both fiction and non-fiction) out loud in English. Working in a second language is tough.
So a difficult to understand accent, or not being truly fluent could be anywhere from a -1 to a -100 (so bad of an accent they are un-hireable) in the 0 to 100 candidate scoring system.
Data Point 3 - Citizenship
Were all the Asian candidates citizens? Choosing a citizen over a non-citizen is not discrimination. How many of the Asian candidates are non-citizens?
There are probably a dozen or so more data points to add.
For rapid development in Business Apps environments, I recommend C#.
I first learned in Java because Java is the most taught language in schools. Newbies, like college students, do the most searching on the web. That sways the stats to make Java look way more popular than C#. However, multiple checks for available jobs have shown C# to have as many or more jobs that Java. Also, the # character just isn't handled by everything as well as it should be and makes C# stats inaccurate. The # character causes a lot of C# stats to be lost and/or not properly counted.
IDE: Visual Studio is so far beyond other IDEs, nothing else even half as good. Maybe not even 1/3 as good. The free version of Visual Studio takes away any issues that used to exist, such as it being too expensive. .NET Core and the open source of .NET Core is creating a lot of buzz.
Language: C# has a lot of features and is fast to code in.
Mobile: With C# (using the now free Xamarin library), one can write mobile Apps for iOS, Android, and Windows. C# provides the best native cross platform development experience for mobile apps out there.
Web: Whether you do WCF or WebAPI or MVC, you have some great options for coding the backend and frontend in C#. Though you can't completely get away from JavaScript for front end.
Verbosity: I write less code in C# to do the same things in Java and C#.
Buzz:
Oracle is not pushing Java forward like it needs to be pushed. If Android hadn't based it's primary language on Java, Java would be following Open Office into its slow demise.
The language you write in most is the most popular language to you.
If you work in Java, C#, or C++, you will have plenty of jobs available. If you know two of them and have descent coding skills you will be head hunted constantly.
Knowing multiple languages makes you better.
English is my first language, but I learned Spanish as my second language. I didn't fully understand many of the grammar and other language concepts in English until I learned Spanish. Learning Spanish helped my English more than the study of English did.
Likewise, I didn't fully understand delegates and events in C# until I really started coding in JavaScript, a language that is extremely callback heavy, so much so that JavaScript can lead one to call back hell. Each language takes advantage of different features and logic and do so in different ways. Seeing how two different language implement the same feature actually helps you better understand the concept, not just use the code without fully understanding it.
So which language is popular doesn't matter. If you know two languages or more well, and can solve problems, you can probably be successful in any language.
You immediately went to religion? A religious bigotry is alive and thriving on slashdot!
From what I understand the motives to deny climate change are political not religious.
Are you kidding. Most Americans are living the American dream and most American's are rich.
The problem is that many have changed the definition of rich. The idea of keeping up with the Jones is real, you just don't fully understand the extent of it and that most poeple are guilty of it even if we think we aren't.
In the middle ages, if a person owned land and had a livable building on it, and could self-sustain them and their family (at least two meals a day even if meager at time) from the land, that person was rich. They were probably a Lord, even if they couldn't afford servants.
Now, we have people who own land, a home, eat two or three meals every day, have their kids going to school, have electricity, one used car, refrigerators, hot water heaters, warm showers, soft beds, plenty of blankets, a couple TVs, a cable TV package. But they have four kids in only two bedrooms (can you believe they are sharing a room) and the household makes less than 50k a year. They can't get their kids phones. Some say that family is in poverty, or that family is incorrectly termed "lower middle class".
If you compare that family to the rest of the word, the way the other 7 billion people live, most in 3rd world countries, then that family isn't just rich; they are loaded. They have way more than they need. That family isn't just seeking the american dream, they have found it!
You see, over time "nice-to-haves" such as a car, a phone of any type, computers, tablets, game consoles, expensive diets, perfect grass in the yard, and many other things have slowly become so ubiquitous that you forgot that only the top 10% of the
With internet and IT tech we are improving many aspects of the world by:
1. Improving communication world wide.
2. Improving entertainment world wide.
3. Improving education world wide.
4. Make banks and credit card readers available online to everyone (so even poor person from a 3rd world small town can run a business)
etc.
With DNA/Gene manipluation we are trying to end world hunger:
1. Creating GMO food that can grow where no plant has grown before.
2. Determining causes of diseases and how to stop them
3. Finding ways to kill weeds without pesticide
etc.
I could go on . . .
Wow! Is this over-hyped in the media.
Facebook, please remove all child nudity automatically. That is fine. If someone wants an exception, please let them submit that exception manually.
That is what happened.
This is not a problem at all.
The quote is intended to isolate everything inside it, and by definition, the punctuation is not part of what is quoted. Living in the US, I rebel and put the punctuation after the quote all the time.
Your solution, to bug the Unicode Consortium, is the best solution I've ever heard.
Great example of something that is a valid use case.
Issue:
Don't hit kids
You are assuming a car has to solve the problem the way you are solving it. You don't see the kids, but you guess they might be there by the open garage. So you drive slower. Why would a computer do that?
A self-driving care could be equipped with an infrared sensor and doesn't have to wonder if kids are nearby. It doesn't have to guess that their might be kids by open garages. The 360 degree sensor detects all warm life in the vicinity, tracks those heat signals movement at submillisecond speed, and makes sure not to hit any of the heat signatures without even having to slow down. So not only is the problem solved better, it doesn't require slow driving so things have improved.