Hmm, there is still a point in it. When you tax consumption, you can very easily target segments. Like, if you don't tax unprocessed food and clothes (something that is already common), you help the poors a lot. If you tax the shit out of high end cellphones and luxury cars, you then specifically target rich people, without hurting those who buy a phone just to talk and cars just to get to work.
The primary issue with it obviously is that if people change their spending habits because of taxes, they then hurt businesses, who hire less people, and you go full circle.
The harm is very similar to why you want everyone having access to health care.
Basically, if everyone was rational and calculating, it wouldn't be an issue. Its just offer and demand, the market, the result of your situation, and some luck.
The problem is that humans being humans, and by their very nature, will not always want to take responsibility for getting in a situation (and sometimes they really are not at fault...where you're born for example factors heavily).
You could say "Well, either work harder or just accept it". But they won't (well, some won't). They'll take shortcuts. Some will start selling drugs and weapons, some will become pimps, some will take a gun and go hit a bank. Then the person worth $1,000,000 come back home to learn his 12 years old daughter got raped.
When people aren't jealous, they're much much MUCH less likely to do something stupid, and that's better for everyone.
Again, like I said, its like why you need everyone to have health insurance. In a perfect world, some people would get it if they want, some wouldn't...the ones that didn't would sometime get sick, not be able to afford it, and die. That would be their choice to make. But its not how it happens. They take a risk, then when their 3 years old son gets sick and they can't afford the hospital, they take a gun and get the money, or they start manifesting and saying they're owed health care anyway. Its just easier for everyone to make sure no one ends up in that situation.
Basically, humans are emotional, irrational being by their very nature, including you and me, no matter how much we'd like to pretend otherwise, and a society built assuming everyone is logical and will accept the consequence of their decisions will simply fall apart, have crazy crime rate, etc.
You took that out of context and read too much into it. My statement wasn't only about targeting newer browsers, but when you have some form of control over a small, focused user base.
If your target audience is data scientists in big companies (that was the scenario i had in mind, based on a real product we shipped), 99.9 (I almost want to say 100%) of our target audience (a few hundreds users across a couple companies) was running less than 2 years old Macbook Pros. That worked quite nicely.
Sure, once you start growing and widening your target audience you'd start needing some kind of fallback...but the way we saw it, it was like if you were making 3d Studio Max or Maya or whatever... you can assume a certain level of hardware from your users.
Yeah, especially older ("more mature") systems tend to have those restrictions, because ERP developers usually prioritize "crossing the checkboxes" (ie: feature bloat) over good engineering. There's a few that have more forward thinking approaches...
Even many very large e-commerce sites dropped IE7 now, as it accounts for a very small amount of sessions, and an even smaller amount of conversion. Software engineers are expensive, and you need a lot to maintain a moderately complex website/app that supports IE7.
IE8 is a little more awkward. If your target audience is the general public (again, ecommerce site selling stuff to a general audience), you'll have to support it. If, however, you have a more sophisticated product (let say you target a more professional user base), you generally can get away with only supporting IE9 and up (ie: thats what Amazon EC2 does i beleive).
And if you develop an actual specialized web "app" that you license to a small group, something that will only be used internally by a few users, let say an HR management software or an ERP, you can have pretty constrained supported browser lists. This is where you can start wiping out the "Firefox/Chrome edge or IE10+". Developing with only green browsers as targets is pretty nuts. Lots of features you've never thought about become available. You can have offline mode because of local storage, webGL can be assumed, performance is rarely an issue, you pretty much don't need librairies like underscore anymore to do functional stuff because Array.prototype has most of it...
As you said, Google supports these. Which means the "SLA" is minimum 18 months from release, so you reasonably will have the "latest and greatest" for about 2 years, considering at what pace updates come out. Generally they keep doing minor releases a bit after that too, its just you're not guaranteed the next major Android version, though Cyanogen and whatsnot tend to support nexus devices pretty well afterward.
Its not as long as I'd like it to be, but at least there's no surprise with Nexus.
On the other hand, its not damn hard for the person who wants to cheat to get the divorce FIRST. If my wife's no longer interested in me, I'd hope she'd just tell me. I'd be heart broken, but at least we could clean the slate in a civilized manner. From the moment she tells me (even before the divorce goes through), she'd have no moral obligation whatsoever and can go and sleep with whoever the hell she wants.
Sure, she technically can even without telling me anything...but that's one hell of an assholish thing to do. Tell the partner that its over FIRST, sleep around later. Its not that complicated.
Yup. It supposingly got better, but back when i was on FiOS (I moved and don't have it anymore), getting 360p on FiOS to stream ok was miracles. Even back then Netflix worked just fine, so did all the anime services (Crunchyroll, Funimation) in HD. I could download stuff pretty quickly. Youtube however? Even the "music only" videos with static images that should compress fairly well would barely run at all. Some MMO games (ie: FF14) were unplayable unless using a VPN service (1+ second lag spikes, constantly)
If i go eat at a restaurant, I don't get to examine their entire cooking process, and i only have their word on what ingredient goes in. Sometimes shit happens, and sometimes there's lye in the iced tea http://kitchenette.jezebel.com... .
Now, if I get sick because a restaurant employee that's paid minimum wadge (if I'm lucky...it could just be an illegal who's getting screwed and thus doesn't care too much), well, there was a risk and I knew there was a risk. Nobody should expect to go to restaurants their entire life, especially small foodcourt places, and never get sick.
Now, if I DO get sick, and can pinpoint where it came from, I'm STILL GOING TO SUE THE FUCKING RESTAURANT TO OBLIVION (or at least, to the extent the law allows).
This is the same thing, except that the laws didn't evolve yet (because until recently, this wasn't a situation that deserved special cases).
Now even if you change the laws, you very well may never find the hacker. In the same way, a whole lot of rapists are never caught. But if you DO find the damn hacker, you sure as hell should have a case to toss the motherfucker in jail. And if you don't, you should be able to get the photos taken down, assuming you are in the jurisdiction of the hosting company (ie: don't sue Google, please...) In a lot of places, that last thing is NOT true. Even if you find the hacker, or can reach the hosts, its very possible no law applies to them. (at least no sex related ones).
One day society will evolve and sex won't be something that can make it harder to be employed, that won't get people embarrassed, etc, but right now, in many societies, it is the case. Until that change, the laws should be able to appropriately deal with it (ie: the recent issues in Mass where it was legal to take upskirt shots).
You can have something like Keypass on a dropbox account (or on your own server, ownCloud or whatever), then sync it on your mobile device and access it from there. If you lose the phone or dropbox gets hacked, someone can get your file...then they can start having fun brute forcing your ONE strong password you actually remember for the next 15 years, at which point you probably reset all the passwords anyway.
The main issue there is the input method. If you have it on your phone, you need to look the password and enter it. Entering a randomly generated 20 character password with your TV remote is something directly from hell. Even doing it with a keyboard is NOT fun.
correct horse battery staple may not be all that memorable... but let say: "I've been married since 1995!!!" or "Man, I fucking love lamb curry~" are pretty easy to remember, and assuming everyone cares about different things, will be pretty darn hard to snatch. Go ahead and dictionary attack it all you want.
The problem with the hundreds of site is the big one. No matter what, even if my password is just 1 dictionary word, I'll never be able to remember it for each site. The closest thing you can do is have an algorithm that defers the password from the site's name or url or something, but thats not practical for the average Joe, and the variety of password rules for each site means it won't really work for all of them, then you have to remember the exceptions...
The password manager only needs 1 password, and the file could be anywhere (ie: different people will keep them in different places), making mass harvesting tricky. And you have to get to the file in the first place (ok, if everyone puts in on iCloud we're back to square 1...)
Getting people to create 1 strong password, and use the manager for the others is one thing.
Getting people to do it 50-100(!!!) times and remember all of them, for all the accounts and services people have to manage in 2014, is insane and won't happen.
I agree its definately an half solution, but its better than the alternative. The password could be biometric too, solving part of the issue.
IMO the biggest problem left is input of long, complex password. Typing out an extremely long password on systems where I can't copy paste (ie: my TV or on home appliances) is crazy.
I use keypass for my passwords. The thing is, as is well known, a huge attack vector is to compromise a service provider (let say Sony or Adobe), get a password database, then go and find all users who used the same password everywhere. I can have the strongest password EVAR!~, if I use it more than once, and someone who stored it improperly gets hacked, its over (thus why the moment a new MMO comes out, a bazillion people get hacked, because their account infos are in every password database available as torrents).
So that means, obviously, you need 1 password per service. Now, looking at my keypass file right now, and including "family" passwords (ie: accounts both myself and my wife need access to), I have _123_ distinct accounts. Some of them include stuff like my router's password, so let say I have 100~ passwords for 3rd party services.
100. A hundred fucking different passwords. These are just the ones I have needed in the last 1-2 months, from services like Hulu and Slashdot, to my town's website to pay taxes, going by banks for every one of my credit cards, and everything in between. It adds up.
No normal human being will be able to efficiently manage this amount of accounts and keep them all secure, keep up with which one recently got hacked to replace passwords, etc. The password managers are too complex for the average joe.
Want to make it worse? When I want to enter a password on my Nest thermostat, it takes fucking forever. Include a mistake or two and i just spent 15 minutes entering a semi-secure password. The Funimation channel makes me do the same thing on my TV. Its just insane.
So what does the average Joe without patience do? Of course, their password is now ABCD123. DONE.
Passwords are a flawed security mechanism, its just easy to implement. We need a new one.
It really depends in what industry or subset of an industry you're in... I had to work on implementing something like that once for legal at an extremely large (and famous, or rather, infamous) company. Lawyers needed to run full searches against all our documents very very quickly to go through the bazillion lawsuit threats we were getting on a daily basis to figure out if they had some weight or not. That very much required full text search.
There's a lot of popular things I've never heard about. The indexing/search space is actually pretty big, because its one of those things everyone thinks is trivial, until you need to actually do it in meaningful ways or scale. Almost everyone hits a big fat roadblock, and start looking for tools to do it (since its more or less a solved problem). For the longest time, Lucene was a defacto standard, but its fairly low level as far as indexing and searching goes, and everyone reinvented the wheel over it.
So then you got stuff like Solr and other commercial product. For a while, the only meaningful ones were Solr, Fast, Autonomy, Endeca, etc... Still, the field is large enough to have a big mix of both open source AND commercial solutions (the last 2 I mentioned above were often part of multi-million dollar contracts, and not because the VP of IT was a moron...), and even more recently it exploded with more solutions than one would expect.
Its pretty much a field on its own, so if you've never had that kind of problem or worked for a company who did (and was close enough to see it), you wouldn't have heard of it. Everyone else did though. Its a bit like content management systems (there's more than Wordpress...), ERPs, etc.
Yup. If this had to be done (I disagree, but let say it has to...), then you need a judge or something to make the call, not some random underpaid bozo making the call. The time it would take would also ensure a lot less requests go through...
People talked about how spam would make email useless and that we'd need a replacement. But spam filters have become pretty good, and my Gmail account is treating me quite well.
My phone however? I use a service to flag known spam callers and have them never reach my phone, but that only use numbers, not the content of the message. So I pretty much just whitelist, and everyone else has to leave a message, and I'll call them back. Since I get a lot of crap spam calls, it takes a while before I go through messages, and can take several days before I call someone back.
So I just tell my friends and families: if you're going to call me without valid caller id, just poke me on Skype or shoot me an email. Its faster.
Phone communication is worthless now unless its plan in advance.
You're in a world where people are so manipulated (by the media, peers, etc), that its very easy to have 3 million people all be wrong. Especially when that 3 million is 1% of the population, and its only the vocal majority (people who like to voice their opinion a lot), you can end up with a non-representative sample pretty easily.
Now in this case, those 3 million people are most likely right (or at least, their idea match my own...so I'd like for them to be right), but it definitely doesn't always happen that way.
You have a standardize application process for college where you'll take standard tests to prepare you for a job industry where you'll be judged on standard interviews.
We could change things from the bottom up (change how you get into college, and then maybe change the tests..and then people that come out of there may interview differently), but the transition period would be awkward at best.
Alternatively you could change things the other way around. Start being smarter about how job interviews are done, then college could change, then their application could change.
Though "creative" people generally go in "creative" fields where things like portfolios and whatsnot are the norm... not just standardized tests, so while there's problems, its not nearly as bad as its made out to be.
Thats done all the time. You just need to give enough incentives (ie: equity with long term conditions) for people to stay.
I don't know how many people work on CyanogenMod, but hiring a douzen or so top notch engineers with knowledge of android's internal could take years. Thats a lot of lost opportunities, projects that have to be canned from lack of resources.
Congratulation, you've just described any kind of software development where you actually make stuff happen (as opposed to just making a stupid command line app that does nothing).
Doing anything meaningful in Java on *nix? Expect to hit quite a few annoying JVM bugs no one ever saw before, because they didnt do quite what you were doing.
Doing anything meaningful on Linux? Make sure to only target a very stable version of a specific distro...otherwise you'll find that libA that depends on libB that depends on libC has a bug that is non-deterministic because of libD.
Doing any kind of browser development? You heard as long as you didnt have to deal with IE you were ok? HAHAHA, jokes on you. Prepare to fight with non-standard mozilla behavior and subtle edge cases between different versions of Webkit/Blink.
Its the same thing as with the whole Document and settings vs C:\users. There's always been a good way to get it, but most developers suck balls and won't spend the 20 seconds it takes to figure it out.
Yeah, poor software developer and computer scientist in the US...Out of college if they're decent they're ONLY in the top 6%* of income in the country (all experience put together). And after a few years they're "only" in the top 3%* without having to sell their soul to a major bank (and they can go much higher if they decide to sell their soul anyway, but they can keep that as an option instead of it being mandatory).
Poor poor things.
*references not posted because the precise numbers vary depending on where you look...but the general idea stays the same.
Slashdot Mirror
Hmm, there is still a point in it. When you tax consumption, you can very easily target segments. Like, if you don't tax unprocessed food and clothes (something that is already common), you help the poors a lot. If you tax the shit out of high end cellphones and luxury cars, you then specifically target rich people, without hurting those who buy a phone just to talk and cars just to get to work.
The primary issue with it obviously is that if people change their spending habits because of taxes, they then hurt businesses, who hire less people, and you go full circle.
The harm is very similar to why you want everyone having access to health care.
Basically, if everyone was rational and calculating, it wouldn't be an issue. Its just offer and demand, the market, the result of your situation, and some luck.
The problem is that humans being humans, and by their very nature, will not always want to take responsibility for getting in a situation (and sometimes they really are not at fault...where you're born for example factors heavily).
You could say "Well, either work harder or just accept it". But they won't (well, some won't). They'll take shortcuts. Some will start selling drugs and weapons, some will become pimps, some will take a gun and go hit a bank. Then the person worth $1,000,000 come back home to learn his 12 years old daughter got raped.
When people aren't jealous, they're much much MUCH less likely to do something stupid, and that's better for everyone.
Again, like I said, its like why you need everyone to have health insurance. In a perfect world, some people would get it if they want, some wouldn't...the ones that didn't would sometime get sick, not be able to afford it, and die. That would be their choice to make. But its not how it happens. They take a risk, then when their 3 years old son gets sick and they can't afford the hospital, they take a gun and get the money, or they start manifesting and saying they're owed health care anyway. Its just easier for everyone to make sure no one ends up in that situation.
Basically, humans are emotional, irrational being by their very nature, including you and me, no matter how much we'd like to pretend otherwise, and a society built assuming everyone is logical and will accept the consequence of their decisions will simply fall apart, have crazy crime rate, etc.
You took that out of context and read too much into it. My statement wasn't only about targeting newer browsers, but when you have some form of control over a small, focused user base.
If your target audience is data scientists in big companies (that was the scenario i had in mind, based on a real product we shipped), 99.9 (I almost want to say 100%) of our target audience (a few hundreds users across a couple companies) was running less than 2 years old Macbook Pros. That worked quite nicely.
Sure, once you start growing and widening your target audience you'd start needing some kind of fallback...but the way we saw it, it was like if you were making 3d Studio Max or Maya or whatever... you can assume a certain level of hardware from your users.
Yeah, especially older ("more mature") systems tend to have those restrictions, because ERP developers usually prioritize "crossing the checkboxes" (ie: feature bloat) over good engineering. There's a few that have more forward thinking approaches...
Even many very large e-commerce sites dropped IE7 now, as it accounts for a very small amount of sessions, and an even smaller amount of conversion. Software engineers are expensive, and you need a lot to maintain a moderately complex website/app that supports IE7.
IE8 is a little more awkward. If your target audience is the general public (again, ecommerce site selling stuff to a general audience), you'll have to support it. If, however, you have a more sophisticated product (let say you target a more professional user base), you generally can get away with only supporting IE9 and up (ie: thats what Amazon EC2 does i beleive).
And if you develop an actual specialized web "app" that you license to a small group, something that will only be used internally by a few users, let say an HR management software or an ERP, you can have pretty constrained supported browser lists. This is where you can start wiping out the "Firefox/Chrome edge or IE10+". Developing with only green browsers as targets is pretty nuts. Lots of features you've never thought about become available. You can have offline mode because of local storage, webGL can be assumed, performance is rarely an issue, you pretty much don't need librairies like underscore anymore to do functional stuff because Array.prototype has most of it...
Fun stuff.
As you said, Google supports these. Which means the "SLA" is minimum 18 months from release, so you reasonably will have the "latest and greatest" for about 2 years, considering at what pace updates come out. Generally they keep doing minor releases a bit after that too, its just you're not guaranteed the next major Android version, though Cyanogen and whatsnot tend to support nexus devices pretty well afterward.
Its not as long as I'd like it to be, but at least there's no surprise with Nexus.
You're correct and I fully agree with you.
On the other hand, its not damn hard for the person who wants to cheat to get the divorce FIRST. If my wife's no longer interested in me, I'd hope she'd just tell me. I'd be heart broken, but at least we could clean the slate in a civilized manner. From the moment she tells me (even before the divorce goes through), she'd have no moral obligation whatsoever and can go and sleep with whoever the hell she wants.
Sure, she technically can even without telling me anything...but that's one hell of an assholish thing to do. Tell the partner that its over FIRST, sleep around later. Its not that complicated.
Yup. It supposingly got better, but back when i was on FiOS (I moved and don't have it anymore), getting 360p on FiOS to stream ok was miracles. Even back then Netflix worked just fine, so did all the anime services (Crunchyroll, Funimation) in HD. I could download stuff pretty quickly. Youtube however? Even the "music only" videos with static images that should compress fairly well would barely run at all. Some MMO games (ie: FF14) were unplayable unless using a VPN service (1+ second lag spikes, constantly)
If i go eat at a restaurant, I don't get to examine their entire cooking process, and i only have their word on what ingredient goes in. Sometimes shit happens, and sometimes there's lye in the iced tea http://kitchenette.jezebel.com... .
Now, if I get sick because a restaurant employee that's paid minimum wadge (if I'm lucky...it could just be an illegal who's getting screwed and thus doesn't care too much), well, there was a risk and I knew there was a risk. Nobody should expect to go to restaurants their entire life, especially small foodcourt places, and never get sick.
Now, if I DO get sick, and can pinpoint where it came from, I'm STILL GOING TO SUE THE FUCKING RESTAURANT TO OBLIVION (or at least, to the extent the law allows).
This is the same thing, except that the laws didn't evolve yet (because until recently, this wasn't a situation that deserved special cases).
Now even if you change the laws, you very well may never find the hacker. In the same way, a whole lot of rapists are never caught. But if you DO find the damn hacker, you sure as hell should have a case to toss the motherfucker in jail. And if you don't, you should be able to get the photos taken down, assuming you are in the jurisdiction of the hosting company (ie: don't sue Google, please...) In a lot of places, that last thing is NOT true. Even if you find the hacker, or can reach the hosts, its very possible no law applies to them. (at least no sex related ones).
One day society will evolve and sex won't be something that can make it harder to be employed, that won't get people embarrassed, etc, but right now, in many societies, it is the case. Until that change, the laws should be able to appropriately deal with it (ie: the recent issues in Mass where it was legal to take upskirt shots).
Thats the only problem here.
You can have something like Keypass on a dropbox account (or on your own server, ownCloud or whatever), then sync it on your mobile device and access it from there. If you lose the phone or dropbox gets hacked, someone can get your file...then they can start having fun brute forcing your ONE strong password you actually remember for the next 15 years, at which point you probably reset all the passwords anyway.
The main issue there is the input method. If you have it on your phone, you need to look the password and enter it. Entering a randomly generated 20 character password with your TV remote is something directly from hell. Even doing it with a keyboard is NOT fun.
correct horse battery staple may not be all that memorable...
but let say: "I've been married since 1995!!!" or "Man, I fucking love lamb curry~" are pretty easy to remember, and assuming everyone cares about different things, will be pretty darn hard to snatch. Go ahead and dictionary attack it all you want.
The problem with the hundreds of site is the big one. No matter what, even if my password is just 1 dictionary word, I'll never be able to remember it for each site. The closest thing you can do is have an algorithm that defers the password from the site's name or url or something, but thats not practical for the average Joe, and the variety of password rules for each site means it won't really work for all of them, then you have to remember the exceptions...
The password manager only needs 1 password, and the file could be anywhere (ie: different people will keep them in different places), making mass harvesting tricky. And you have to get to the file in the first place (ok, if everyone puts in on iCloud we're back to square 1...)
Getting people to create 1 strong password, and use the manager for the others is one thing.
Getting people to do it 50-100(!!!) times and remember all of them, for all the accounts and services people have to manage in 2014, is insane and won't happen.
I agree its definately an half solution, but its better than the alternative. The password could be biometric too, solving part of the issue.
IMO the biggest problem left is input of long, complex password. Typing out an extremely long password on systems where I can't copy paste (ie: my TV or on home appliances) is crazy.
I use keypass for my passwords. The thing is, as is well known, a huge attack vector is to compromise a service provider (let say Sony or Adobe), get a password database, then go and find all users who used the same password everywhere. I can have the strongest password EVAR!~, if I use it more than once, and someone who stored it improperly gets hacked, its over (thus why the moment a new MMO comes out, a bazillion people get hacked, because their account infos are in every password database available as torrents).
So that means, obviously, you need 1 password per service. Now, looking at my keypass file right now, and including "family" passwords (ie: accounts both myself and my wife need access to), I have _123_ distinct accounts. Some of them include stuff like my router's password, so let say I have 100~ passwords for 3rd party services.
100. A hundred fucking different passwords. These are just the ones I have needed in the last 1-2 months, from services like Hulu and Slashdot, to my town's website to pay taxes, going by banks for every one of my credit cards, and everything in between. It adds up.
No normal human being will be able to efficiently manage this amount of accounts and keep them all secure, keep up with which one recently got hacked to replace passwords, etc. The password managers are too complex for the average joe.
Want to make it worse? When I want to enter a password on my Nest thermostat, it takes fucking forever. Include a mistake or two and i just spent 15 minutes entering a semi-secure password. The Funimation channel makes me do the same thing on my TV. Its just insane.
So what does the average Joe without patience do? Of course, their password is now ABCD123. DONE.
Passwords are a flawed security mechanism, its just easy to implement. We need a new one.
It really depends in what industry or subset of an industry you're in... I had to work on implementing something like that once for legal at an extremely large (and famous, or rather, infamous) company. Lawyers needed to run full searches against all our documents very very quickly to go through the bazillion lawsuit threats we were getting on a daily basis to figure out if they had some weight or not. That very much required full text search.
There's a lot of popular things I've never heard about. The indexing/search space is actually pretty big, because its one of those things everyone thinks is trivial, until you need to actually do it in meaningful ways or scale. Almost everyone hits a big fat roadblock, and start looking for tools to do it (since its more or less a solved problem). For the longest time, Lucene was a defacto standard, but its fairly low level as far as indexing and searching goes, and everyone reinvented the wheel over it.
So then you got stuff like Solr and other commercial product. For a while, the only meaningful ones were Solr, Fast, Autonomy, Endeca, etc... Still, the field is large enough to have a big mix of both open source AND commercial solutions (the last 2 I mentioned above were often part of multi-million dollar contracts, and not because the VP of IT was a moron...), and even more recently it exploded with more solutions than one would expect.
Its pretty much a field on its own, so if you've never had that kind of problem or worked for a company who did (and was close enough to see it), you wouldn't have heard of it. Everyone else did though. Its a bit like content management systems (there's more than Wordpress...), ERPs, etc.
Yup. If this had to be done (I disagree, but let say it has to...), then you need a judge or something to make the call, not some random underpaid bozo making the call. The time it would take would also ensure a lot less requests go through...
People talked about how spam would make email useless and that we'd need a replacement. But spam filters have become pretty good, and my Gmail account is treating me quite well.
My phone however? I use a service to flag known spam callers and have them never reach my phone, but that only use numbers, not the content of the message. So I pretty much just whitelist, and everyone else has to leave a message, and I'll call them back. Since I get a lot of crap spam calls, it takes a while before I go through messages, and can take several days before I call someone back.
So I just tell my friends and families: if you're going to call me without valid caller id, just poke me on Skype or shoot me an email. Its faster.
Phone communication is worthless now unless its plan in advance.
You're in a world where people are so manipulated (by the media, peers, etc), that its very easy to have 3 million people all be wrong. Especially when that 3 million is 1% of the population, and its only the vocal majority (people who like to voice their opinion a lot), you can end up with a non-representative sample pretty easily.
Now in this case, those 3 million people are most likely right (or at least, their idea match my own...so I'd like for them to be right), but it definitely doesn't always happen that way.
You have a standardize application process for college where you'll take standard tests to prepare you for a job industry where you'll be judged on standard interviews.
We could change things from the bottom up (change how you get into college, and then maybe change the tests..and then people that come out of there may interview differently), but the transition period would be awkward at best.
Alternatively you could change things the other way around. Start being smarter about how job interviews are done, then college could change, then their application could change.
Though "creative" people generally go in "creative" fields where things like portfolios and whatsnot are the norm... not just standardized tests, so while there's problems, its not nearly as bad as its made out to be.
Thats done all the time. You just need to give enough incentives (ie: equity with long term conditions) for people to stay.
I don't know how many people work on CyanogenMod, but hiring a douzen or so top notch engineers with knowledge of android's internal could take years. Thats a lot of lost opportunities, projects that have to be canned from lack of resources.
Congratulation, you've just described any kind of software development where you actually make stuff happen (as opposed to just making a stupid command line app that does nothing).
Doing anything meaningful in Java on *nix? Expect to hit quite a few annoying JVM bugs no one ever saw before, because they didnt do quite what you were doing.
Doing anything meaningful on Linux? Make sure to only target a very stable version of a specific distro...otherwise you'll find that libA that depends on libB that depends on libC has a bug that is non-deterministic because of libD.
Doing any kind of browser development? You heard as long as you didnt have to deal with IE you were ok? HAHAHA, jokes on you. Prepare to fight with non-standard mozilla behavior and subtle edge cases between different versions of Webkit/Blink.
Mobile development? /wrist
Need we go on?
Its the same thing as with the whole Document and settings vs C:\users. There's always been a good way to get it, but most developers suck balls and won't spend the 20 seconds it takes to figure it out.
Yeah, poor software developer and computer scientist in the US...Out of college if they're decent they're ONLY in the top 6%* of income in the country (all experience put together). And after a few years they're "only" in the top 3%* without having to sell their soul to a major bank (and they can go much higher if they decide to sell their soul anyway, but they can keep that as an option instead of it being mandatory).
Poor poor things.
*references not posted because the precise numbers vary depending on where you look...but the general idea stays the same.
Exactly. Either all happen OR NONE HAPPEN.
OR NONE HAPPEN.
OR NONE HAPPEN.
OR NONE HAPPEN.
Which means you can simply rerun any failed transaction safely.
Thanks for repeating what I said in different words.
If you can find a lot of qualified people in Detroit, yeah, you're right. That may be difficult though.