Except you can have a rogue router that is rerouting your data to a false facade of your bank. Sure, it might show up as bogus if you're paying attention, but not a lot of people are trained to mistrust everything and double check every time.
Which in a roundabout way exposes the flaw in removing end user options from many operating systems. Today you basically get a choice of "WPA2 Enterprise" or "WPA2 Personal", without finer grained option (ie, advanced options). Users are being trained to just click the networks that have a lock symbol, but not think further than that.
There have been single player games that have done similar things to prevent piracy. Instead of failing the game immediately when they detect a pirated copy, they wait until near the end of the game to show a notice or give a lower score or prevent completion.
First rule of PvP is that if you lose, the other guy was cheating. Second rule of PvP is that if you win, it was all due to superior skill. Third rule of PvP is that the game creators have a grudge against you (or your role, your class, etc). Fourth rule of PvP is that mom has to knock before entering the basement.
The end result, no matter what party violates the contract, is that the player no longer gets to play the game.
And the EULA is not a real contract anyway. If you read them there are no clauses that say what the game provider is obligated to provide, but often there are clauses that do explicitly say the game providers is not under any obligation.
Compare to a rental agreement, a real contract. I pay rent each month, but I don't get rent in return from the building owner. If I break the rules, I can get evicted. If the building owner breaks their part of the agreement then I have very little recourse except to hire an expensive lawyer and hope for the best.
If the banned players want to start a lawsuit, then good luck to them.
Well, I may have worked at some dysfunctional companies then. In fact, I'm sure of it. But I have seen too many who get in easily because someone knows the contractor, or the contractor had been a previous employee, or it started as a simple contract job that snowballed into a long term major position.
I keep around Windows XP and 7 vmware images so that I can run some important tools and debuggers that won't work on newer Windows versions. Some of of this software of course may have updated versions but they cost money to upgrade. Sure, the problem is often because of drivers but that always feels like a bigger hassle on Windows than on Linux.
You didn't notice the whole start button controversy in Windows 8? It still doesn't have a real start button back. Never mind the dramatic changes it had in each major release since XP (Vista doesn't count). But the point was, using an argument of Linux UI changes as a reason to not use Linux would also apply at least as well to Windows.
So Linux adds some dumb audio drivers, whereas Windows changes it's entire UI that makes even GNOME 3 look good. So you say, that Metro UI is for home users and not servers? Well, GNOME 3 and PulseAudio aren't for back office servers either. Your Red Hat server is going to run the same software from 10 years ago most likely, whereas Windows is bad at doing this.
You will often hear the Windows guru say "have you tried shutting it off and turning it back on?" Yes, sounds like a joke but it happens. But you don't hear that from the Linux guru.
Because MS created this service, it expends a ton of marketing resources trying to convince everyone that it's the only way to go. I have no doubt that his desire to change to only have Windows is due to this marketing; I see so many generic IT people who always without fail will recommend Microsoft products. The people who can easily find who know Microsoft products are not necessarily the best people for the job; their credentials are often nothing more than taking an MS class and paying for the certificate. Cheaper cost, sure, but also cheaper quality.
This is not just a Microsoft practice. Municipal governments get the hard sell from all sides, armies of sales people descend on elected leaders and convince them that they need some new software, or overpriced routers, or that investing all the money in hedge fund is a good idea, or that a new company will bring in tons of jobs as long as they get a tax discount. And since these elected leaders have literally zero knowledge about technology, finance, management, and so forth, they will believe it all.
A musician usually owns their work. And when hiring a musician to play an element, then they usually play someone else's work anyway. They are often asked to sight read something new. Now if you want to hire a composer, then you would like to see examples, and such a composer is likely to have samples and owns the copyright to them. There's really not a lot of comparison between a music professional and a programming professional.
Often a mistake when you hire a Hot Shot developer. A good worker who fits into a team is better than a great programmer who's a braggart and causes friction and drama.
Time spent programming isn't important. What's important is if the person can do the job that the opening is for. More important than time spent programming is the time spent programming on a team. Can the candidate work well with others, or is the candidate just another of those self taught guys who just don't understand why there is source code control, gets defensive and thinks code reviews are pointless, can't manage to give a reasonable time estimate for a task, and so forth.
If the two candidates are identical except for one doing some programming at home, then you may have a point. But usually the candidates have many differing factors that should be considered first.
Plus, after 10-12 hours of programming, dealing with reports and colleagues, sitting in meetings where the director is yelling at everyone, when I get home I usually only have a couple of hours of free time and I have no more stomach for programming. I want to relieve stress on the brain and relax. I do the home programming projects but often they end up languishing and unfinished.
Also, this is very much correlated to the person's age I've found. Young and in college with tons of energy, there's a lot more who are able to get involved with open source. Old with a family and there's not much time available for it.
Well, I do have code from previous employers. But I never share it with anyone, and I don't have any of the bread-and-butter code that has any trade secrets, just code of drivers for standard devices that I wrote myself. Even when I do the same work later I am never copying and pasting.
Yup, Slashdot is a terrible place to find candidates who fit specific requirements. Maybe it's ok for bulk hires of people with simple skills, but for those jobs HR already has thousands of resumes on file.
Also, if there is something on the resume, then someone WILL ask about it! So many candidates seem to not understand this, and think they can just shove in fluff or outright lies. Or they'll describe the company's main product and make it seem like they were central to its design, only to flounder in the interview when asked simple questions. (I often feel like an idiot when I ask simple questions only to be disappointed yet again that the resume doesn't match the person)
For example, someone describes what their past company built and words it so that you think the person is an expert in radio software. The new company is very interested, that's exactly the sort of person they need. But in the interview it seems the person was mostly a build master and gets confused when asked about MAC layers.
In my experience, contractors don't often get interviewed. Which is annoying since we sometimes get bad contractors. But if the need to fill the position is urgent, and a friend of a friend of someone knows the contractor, you're stuck with that person.
Getting 50 lines of code is useless. There's no way to know who wrote the code; it could be 0% to 100% originating with the candidate. Better to get the candidate to write something new.
NEVER share your current company's code. Never share your past company's code. That is not your code to share! I have never seen a place that asked for me to share code, but I'm old, so maybe they do that now.
But a project's code doesn't mean much, we don't know how much of it you actually wrote, it's not uncommon to have the one dumb guy on the project who doesn't do much. I have a coworker who's favorite question is to ask the candidate to describe a past project in terms of functional blocks and so forth, without saying anything requiring an NDA. And it is amazing often people just didn't understand the project they worked on, and most of the time the resumes made it seem like the person was a project lead.
Individual contributions to code really aren't that important for an interview. What's important is whether you can be hired to work in a team, understand complex topics, whether your listed experience is real or fictitious.
Now some code samples might be ok if we had a person spend an hour to code something up. But it's difficult; they don't have their favorite tools handy, if they do it at home they *will* cheat (seriously, I've heard background voices in a phone interview). There are some web based interview tools for having someone write up code on the web, but no one's going to be good using the awful interfaces except by cut-and-past
I still prefer to see the code on the whiteboard, I don't care about the quality but in how the person thinks. If they claim to have a lot of experience but their syntax seems rusty or that they crammed for it, that's a bad sign. If they can't code up something simple that's very bad, it means I'll end up mentoring someone in programming basics. If the candidate seems hung up on getting the right syntax and it's 5 minutes and they're still tweaking the function header, it's a bad sign. But when the person can just start writing down code and go, and seems to understand the complexity and corner cases, then that's good. If they can understand that there are multiple ways to code it up then that's good. If someone says "I don't normally do this since a library should do it" then that's a bad sign since most everything in a new job will be new.
I've been on a jury. There is always at least one person who refuses to believe a law enforcement officer would lie. I was actually on a jury that somehow had 3 people who were ex law enforcement or worked in a police station, and they were more dubious of a police testimony than the others were.
What laws are being broken? I'm lost. The original protest was about the high numbers of black people being shot by cops, including those who did not run, attack, or argue. None of which deserve being murdered by the way. That these officers were exonerated by the juries is a shameful mark on the country.
The new protest isn't really the same, it's about being offended that a moronic president wants to force the owners to fire them.
There were no national anthems played at professional sporting events before WWII. It was added out of guilt that the players got draft deferrals. It's a mock symbol of patriotism exactly like flags on senators' lapels.
Slashdot Mirror
Except you can have a rogue router that is rerouting your data to a false facade of your bank. Sure, it might show up as bogus if you're paying attention, but not a lot of people are trained to mistrust everything and double check every time.
Which in a roundabout way exposes the flaw in removing end user options from many operating systems. Today you basically get a choice of "WPA2 Enterprise" or "WPA2 Personal", without finer grained option (ie, advanced options). Users are being trained to just click the networks that have a lock symbol, but not think further than that.
What if the policy makers are playing golf that day, and can't respond until the optics are better?
There have been single player games that have done similar things to prevent piracy. Instead of failing the game immediately when they detect a pirated copy, they wait until near the end of the game to show a notice or give a lower score or prevent completion.
First rule of PvP is that if you lose, the other guy was cheating.
Second rule of PvP is that if you win, it was all due to superior skill.
Third rule of PvP is that the game creators have a grudge against you (or your role, your class, etc).
Fourth rule of PvP is that mom has to knock before entering the basement.
The end result, no matter what party violates the contract, is that the player no longer gets to play the game.
And the EULA is not a real contract anyway. If you read them there are no clauses that say what the game provider is obligated to provide, but often there are clauses that do explicitly say the game providers is not under any obligation.
Compare to a rental agreement, a real contract. I pay rent each month, but I don't get rent in return from the building owner. If I break the rules, I can get evicted. If the building owner breaks their part of the agreement then I have very little recourse except to hire an expensive lawyer and hope for the best.
If the banned players want to start a lawsuit, then good luck to them.
Well, I may have worked at some dysfunctional companies then. In fact, I'm sure of it. But I have seen too many who get in easily because someone knows the contractor, or the contractor had been a previous employee, or it started as a simple contract job that snowballed into a long term major position.
I keep around Windows XP and 7 vmware images so that I can run some important tools and debuggers that won't work on newer Windows versions. Some of of this software of course may have updated versions but they cost money to upgrade. Sure, the problem is often because of drivers but that always feels like a bigger hassle on Windows than on Linux.
You didn't notice the whole start button controversy in Windows 8? It still doesn't have a real start button back. Never mind the dramatic changes it had in each major release since XP (Vista doesn't count). But the point was, using an argument of Linux UI changes as a reason to not use Linux would also apply at least as well to Windows.
So Linux adds some dumb audio drivers, whereas Windows changes it's entire UI that makes even GNOME 3 look good. So you say, that Metro UI is for home users and not servers? Well, GNOME 3 and PulseAudio aren't for back office servers either. Your Red Hat server is going to run the same software from 10 years ago most likely, whereas Windows is bad at doing this.
You will often hear the Windows guru say "have you tried shutting it off and turning it back on?" Yes, sounds like a joke but it happens. But you don't hear that from the Linux guru.
Because MS created this service, it expends a ton of marketing resources trying to convince everyone that it's the only way to go. I have no doubt that his desire to change to only have Windows is due to this marketing; I see so many generic IT people who always without fail will recommend Microsoft products. The people who can easily find who know Microsoft products are not necessarily the best people for the job; their credentials are often nothing more than taking an MS class and paying for the certificate. Cheaper cost, sure, but also cheaper quality.
This is not just a Microsoft practice. Municipal governments get the hard sell from all sides, armies of sales people descend on elected leaders and convince them that they need some new software, or overpriced routers, or that investing all the money in hedge fund is a good idea, or that a new company will bring in tons of jobs as long as they get a tax discount. And since these elected leaders have literally zero knowledge about technology, finance, management, and so forth, they will believe it all.
A musician usually owns their work. And when hiring a musician to play an element, then they usually play someone else's work anyway. They are often asked to sight read something new. Now if you want to hire a composer, then you would like to see examples, and such a composer is likely to have samples and owns the copyright to them. There's really not a lot of comparison between a music professional and a programming professional.
Often a mistake when you hire a Hot Shot developer. A good worker who fits into a team is better than a great programmer who's a braggart and causes friction and drama.
And your competitors thank you for it.
Time spent programming isn't important. What's important is if the person can do the job that the opening is for. More important than time spent programming is the time spent programming on a team. Can the candidate work well with others, or is the candidate just another of those self taught guys who just don't understand why there is source code control, gets defensive and thinks code reviews are pointless, can't manage to give a reasonable time estimate for a task, and so forth.
If the two candidates are identical except for one doing some programming at home, then you may have a point. But usually the candidates have many differing factors that should be considered first.
Plus, after 10-12 hours of programming, dealing with reports and colleagues, sitting in meetings where the director is yelling at everyone, when I get home I usually only have a couple of hours of free time and I have no more stomach for programming. I want to relieve stress on the brain and relax. I do the home programming projects but often they end up languishing and unfinished.
Also, this is very much correlated to the person's age I've found. Young and in college with tons of energy, there's a lot more who are able to get involved with open source. Old with a family and there's not much time available for it.
Well, I do have code from previous employers. But I never share it with anyone, and I don't have any of the bread-and-butter code that has any trade secrets, just code of drivers for standard devices that I wrote myself. Even when I do the same work later I am never copying and pasting.
Yup, Slashdot is a terrible place to find candidates who fit specific requirements. Maybe it's ok for bulk hires of people with simple skills, but for those jobs HR already has thousands of resumes on file.
Also, if there is something on the resume, then someone WILL ask about it! So many candidates seem to not understand this, and think they can just shove in fluff or outright lies. Or they'll describe the company's main product and make it seem like they were central to its design, only to flounder in the interview when asked simple questions. (I often feel like an idiot when I ask simple questions only to be disappointed yet again that the resume doesn't match the person)
For example, someone describes what their past company built and words it so that you think the person is an expert in radio software. The new company is very interested, that's exactly the sort of person they need. But in the interview it seems the person was mostly a build master and gets confused when asked about MAC layers.
In my experience, contractors don't often get interviewed. Which is annoying since we sometimes get bad contractors. But if the need to fill the position is urgent, and a friend of a friend of someone knows the contractor, you're stuck with that person.
Getting 50 lines of code is useless. There's no way to know who wrote the code; it could be 0% to 100% originating with the candidate. Better to get the candidate to write something new.
NEVER share your current company's code. Never share your past company's code. That is not your code to share! I have never seen a place that asked for me to share code, but I'm old, so maybe they do that now.
But a project's code doesn't mean much, we don't know how much of it you actually wrote, it's not uncommon to have the one dumb guy on the project who doesn't do much. I have a coworker who's favorite question is to ask the candidate to describe a past project in terms of functional blocks and so forth, without saying anything requiring an NDA. And it is amazing often people just didn't understand the project they worked on, and most of the time the resumes made it seem like the person was a project lead.
Individual contributions to code really aren't that important for an interview. What's important is whether you can be hired to work in a team, understand complex topics, whether your listed experience is real or fictitious.
Now some code samples might be ok if we had a person spend an hour to code something up. But it's difficult; they don't have their favorite tools handy, if they do it at home they *will* cheat (seriously, I've heard background voices in a phone interview). There are some web based interview tools for having someone write up code on the web, but no one's going to be good using the awful interfaces except by cut-and-past
I still prefer to see the code on the whiteboard, I don't care about the quality but in how the person thinks. If they claim to have a lot of experience but their syntax seems rusty or that they crammed for it, that's a bad sign. If they can't code up something simple that's very bad, it means I'll end up mentoring someone in programming basics. If the candidate seems hung up on getting the right syntax and it's 5 minutes and they're still tweaking the function header, it's a bad sign. But when the person can just start writing down code and go, and seems to understand the complexity and corner cases, then that's good. If they can understand that there are multiple ways to code it up then that's good. If someone says "I don't normally do this since a library should do it" then that's a bad sign since most everything in a new job will be new.
I've been on a jury. There is always at least one person who refuses to believe a law enforcement officer would lie. I was actually on a jury that somehow had 3 people who were ex law enforcement or worked in a police station, and they were more dubious of a police testimony than the others were.
What laws are being broken? I'm lost. The original protest was about the high numbers of black people being shot by cops, including those who did not run, attack, or argue. None of which deserve being murdered by the way. That these officers were exonerated by the juries is a shameful mark on the country.
The new protest isn't really the same, it's about being offended that a moronic president wants to force the owners to fire them.
There were no national anthems played at professional sporting events before WWII. It was added out of guilt that the players got draft deferrals. It's a mock symbol of patriotism exactly like flags on senators' lapels.
Are people really being offended?
Maybe prices rise as customer's dwindle. The last remaining customer will have a bill for $1,000,000,000, in order to make up the profits.