You would be technically correct. I talked to an employment lawyer.He said yes, you have a case. It'll cost you 50K after you win. You need to be at least in the hole 100K before it's worth suing. His advice, along with 2 others I consulted, was take it as an expensive lesson in how business is run, at least by some.
I tailor my resume, and remove a lot of dates. No one needs to know when I got my degrees, nor what they were in specifically, nor any special artifacts I created while at school, or even any additional universities of which I may be considered an alumnus. The main school and relevant degree(s) are all that are needed, and at this point, they only serve to back my experience. I also have sliced off at least 10 years of employment history, no one cares what you did 20 or 30 years ago. It's generally irrelevant, at least in the tech industry. Finally, should you have a beard et al, it may pay to trim or shave, especially if it ages you. First appearances with in person interviews can kill you before you've said a single word, so if you're prematurely gray, you may wish to do something to minimize its effects. Don't paint it black though, that is worse than being gray.
You've got to tailor your message to your potential employer. I don't talk about more than 80% of what I've done because it goes in directions that my next employer may have 0 interest in. You have to drive the interview carefully when you have enough experience, to hit highlights that the potential employer may be interested in, and downplay or fully ignore those that they may not. For instance, perhaps you were a sous-chef or the captain of a fishing vessel in an earlier life. This is not something that would come up in your interview, except maybe at the very end during the personality/hobbies outside of work, and then only carefully. Do you know networking (for a company that programs DPI systems): why yes, I've programmed routers and worked on the lower 5 levels of the OSI stack, even if you created the hardware and programmed it. Tailoring your interview is crucial to heightening the interest of the prospective employer, especially if they're going to pay for your experience. Not all companies have good interviewers, so sometimes you have to steer and guide the interview into directions you believe would interest the employer.
H1B should be abolished entirely. So should the backdoor L class, or really any of the things listed here. If we have people on unemployment that are available and able to do the jobs, none of these visas should be granted. Granted, the current unemployment system should make hiring out of the unemployed ranks simpler, but if the unemployment office finds any matches, there should be no visa granted.
Unfortunately, I can relate to his statements, although you'd probably like working for me. I've taken the tact, for instance, when leaving a job I will only give notice once it's beneficial to me. This means that my notice might have 0 lead time, although I truly despise leaving a workplace with no notice. I learned this lesson the hard way, by essentially watching co-workers getting literally walked out the door by security after giving their notice in more than one company, and in others being treated so badly after their notice that several decided to leave early. Early on, I gave a 2 week notice, and then was walked out after 6 days, after, of course, I had transferred what they deemed enough work to other workers. BTW, that meant 4 additional unexpected unpaid vacation days, along with some additional repercussions that were detrimental to me. I was prepared to leave with 2 weeks, or work the full 2 weeks, but not be used the way the company used me. Of course, all my co-workers were aware of the abuse, I believe they got quite a few 0 notices after that. Karma.
I find generally that people that enjoy mindlessly repetitious games with no strategic component (IOW, monster falls from ceiling, shoot twice with shotgun, point right, shoot twice to hit monster behind panel, reload, move forward 10-15 steps until next ceiling panel appears) to be uniquely lacking in imagination and have an amazingly lack of creative potential. Naturally, YMMV, and you also enjoy knitting because you like sweaters.
Sorry, I'd disagree that a developer needs to go to LCD levels (nice overloading of the acronym there:) especially since there's the capability to increase gamma within your OS's display settings, which can make even the darkest of screens seem like they are lit in bright daylight, provided there are contrasting elements in the scene.
It was so boringly repetitious that I, along with many others, wished to return our copies of Doom 3 for a refund. I have no idea how far into the game I got, nor how far left to go, but the lack of fun as you plodded through the same setup every 10-15 steps must have killed off multiple IQ points for those that continued...
You are entirely incorrect on so many fronts, it's funny. I think you should just stop posting on Java since we've probably seen every error you can make already in this story. To finish it off, Javascript is not only sandboxed within each browser's implementation, it is also severely restricted in those implementations in what it can do. Want to edit a local file... can't do it in Javascript in a browser - those capabilities do not exist there. Want to call a new server? Again, can't do it in a browser. Etc etc etc.
Java does have the capability to be signed and sealed, which is about as close to trusted code as you can get. But that's "too hard" for most to deal with, apparently. If applets required signed/sealed jars to run to begin with or pop up a warning, you'd still have a mess of stupid people trained by years of clicking through annoying confirmation boxes in Windows that would still run unsafe applets. So I doubt it would help in any meaningful way.
I don't have java plugins in my browsers, and run noscript in Firefox for non work sites. That's about as safe as you can get.
Well, dumb is as dumb does, or whatever that quote was. Here we see it in action. JRE 7 u 11 has a plugins off option in the configuration, and I believe it prompts you during install as well.
If you support PCs as real work, in a real company, then you should be in control of basic functions. I wouldn't allow a windows machine on the network that wasn't severely restricted. 99% of the work force only needs email, office apps, and web browsing capabilities. If you're not in a real company, and just support fly by night clients, well, then you're in what most of us would define as the 9th circle.
Until we understand time better, the multi-verse remains pure fantasy.
Realize that by that interpretation, somewhere there would a representation of every god humankind has ever devised. I'll withhold signing up for that theory until there's some backing for it, no matter how good (or bad) some of the sci-fi stories on the topic are.
Disingenuous at best, since both parties flagrantly do this as a standard practice. The going broke aspect is because one party in particular believes that we can spend and lower taxes. If they truly wish to lower the spend rate, they could start by removing all congress people from federal payrolls. Since they're supposedly employed by and on behalf of their states, let the states pay them and their office staff. Once removed from federal funds, perhaps they could then look at the spending with a less biased eye.
I dig into various aspects. My job is to evaluate the veracity of their resume regarding experience, as well as the full breath of their experience, beyond what is shared in the resume.
What's funny about that - I once ran into a single class that had more LOCs than that. And it was just one among many hundreds, possibly thousands. But this class stood out for many reasons, not least in that it had a cyclomatic complexity of over 200 after the first round of simplifying refactoring.
I interview many people who talked their way past the first screen or two, but start failing in less than 5 minutes. I don't think we've let a good one go, and we've only hired one questionable one out of the last 10 successful interviews.
...After all, if you have to spend 45 minutes looking up how to do a basic loop, then you're probably not experienced enough for anything beyond entry level (if that), so it helps weed out the people who are outright lying about skills.
I'd say if you need to spend time looking up how to do a basic loop in a language you're supposed to know, perhaps coding isn't a profession you should be in. I hear McDonald's is hiring.
Perhaps it'll mean they get more money devoted to securing the site after this has blown over - time spent testing the site and looking at security is probably more important than the specific technology used (almost every major framework has regular security problems like this), contrary to the righteous flaming and trolling for asp.net/perl/php/other tech which is bound to erupt in the wake of your post.
The best answer to this would be to not use a system that is known to not be secure to begin with. That's a massive failure on the developer's part.
QED
Perhaps, except for the fact that building your security out of what essentially is the equivalent of a rail fence to keep out a flood is doomed to fail. (See what I did there?) There are tools that can work for your stated purpose, and there are tools that are wholly unsuited to the intended application. RoR falls into the latter camp. Oh, and then there's the fact that I didn't talk about about technology xyz, but the actual one selected, and limited my comments to facts regarding said technology. Most other technologies don't have this flaw as a core feature, you have to code it that way. So you might want to revisit your "QED".
Slashdot Mirror
You would be technically correct. I talked to an employment lawyer.He said yes, you have a case. It'll cost you 50K after you win. You need to be at least in the hole 100K before it's worth suing. His advice, along with 2 others I consulted, was take it as an expensive lesson in how business is run, at least by some.
I tailor my resume, and remove a lot of dates. No one needs to know when I got my degrees, nor what they were in specifically, nor any special artifacts I created while at school, or even any additional universities of which I may be considered an alumnus. The main school and relevant degree(s) are all that are needed, and at this point, they only serve to back my experience. I also have sliced off at least 10 years of employment history, no one cares what you did 20 or 30 years ago. It's generally irrelevant, at least in the tech industry. Finally, should you have a beard et al, it may pay to trim or shave, especially if it ages you. First appearances with in person interviews can kill you before you've said a single word, so if you're prematurely gray, you may wish to do something to minimize its effects. Don't paint it black though, that is worse than being gray.
You've got to tailor your message to your potential employer. I don't talk about more than 80% of what I've done because it goes in directions that my next employer may have 0 interest in. You have to drive the interview carefully when you have enough experience, to hit highlights that the potential employer may be interested in, and downplay or fully ignore those that they may not. For instance, perhaps you were a sous-chef or the captain of a fishing vessel in an earlier life. This is not something that would come up in your interview, except maybe at the very end during the personality/hobbies outside of work, and then only carefully. Do you know networking (for a company that programs DPI systems): why yes, I've programmed routers and worked on the lower 5 levels of the OSI stack, even if you created the hardware and programmed it. Tailoring your interview is crucial to heightening the interest of the prospective employer, especially if they're going to pay for your experience. Not all companies have good interviewers, so sometimes you have to steer and guide the interview into directions you believe would interest the employer.
H1B should be abolished entirely. So should the backdoor L class, or really any of the things listed here. If we have people on unemployment that are available and able to do the jobs, none of these visas should be granted. Granted, the current unemployment system should make hiring out of the unemployed ranks simpler, but if the unemployment office finds any matches, there should be no visa granted.
Unfortunately, I can relate to his statements, although you'd probably like working for me. I've taken the tact, for instance, when leaving a job I will only give notice once it's beneficial to me. This means that my notice might have 0 lead time, although I truly despise leaving a workplace with no notice. I learned this lesson the hard way, by essentially watching co-workers getting literally walked out the door by security after giving their notice in more than one company, and in others being treated so badly after their notice that several decided to leave early. Early on, I gave a 2 week notice, and then was walked out after 6 days, after, of course, I had transferred what they deemed enough work to other workers. BTW, that meant 4 additional unexpected unpaid vacation days, along with some additional repercussions that were detrimental to me. I was prepared to leave with 2 weeks, or work the full 2 weeks, but not be used the way the company used me. Of course, all my co-workers were aware of the abuse, I believe they got quite a few 0 notices after that. Karma.
I find generally that people that enjoy mindlessly repetitious games with no strategic component (IOW, monster falls from ceiling, shoot twice with shotgun, point right, shoot twice to hit monster behind panel, reload, move forward 10-15 steps until next ceiling panel appears) to be uniquely lacking in imagination and have an amazingly lack of creative potential. Naturally, YMMV, and you also enjoy knitting because you like sweaters.
Sorry, I'd disagree that a developer needs to go to LCD levels (nice overloading of the acronym there:) especially since there's the capability to increase gamma within your OS's display settings, which can make even the darkest of screens seem like they are lit in bright daylight, provided there are contrasting elements in the scene.
It was so boringly repetitious that I, along with many others, wished to return our copies of Doom 3 for a refund. I have no idea how far into the game I got, nor how far left to go, but the lack of fun as you plodded through the same setup every 10-15 steps must have killed off multiple IQ points for those that continued...
You are entirely incorrect on so many fronts, it's funny. I think you should just stop posting on Java since we've probably seen every error you can make already in this story. To finish it off, Javascript is not only sandboxed within each browser's implementation, it is also severely restricted in those implementations in what it can do. Want to edit a local file... can't do it in Javascript in a browser - those capabilities do not exist there. Want to call a new server? Again, can't do it in a browser. Etc etc etc.
Java does have the capability to be signed and sealed, which is about as close to trusted code as you can get. But that's "too hard" for most to deal with, apparently. If applets required signed/sealed jars to run to begin with or pop up a warning, you'd still have a mess of stupid people trained by years of clicking through annoying confirmation boxes in Windows that would still run unsafe applets. So I doubt it would help in any meaningful way.
I don't have java plugins in my browsers, and run noscript in Firefox for non work sites. That's about as safe as you can get.
Well, dumb is as dumb does, or whatever that quote was. Here we see it in action. JRE 7 u 11 has a plugins off option in the configuration, and I believe it prompts you during install as well.
If you support PCs as real work, in a real company, then you should be in control of basic functions. I wouldn't allow a windows machine on the network that wasn't severely restricted. 99% of the work force only needs email, office apps, and web browsing capabilities. If you're not in a real company, and just support fly by night clients, well, then you're in what most of us would define as the 9th circle.
I sure will, when I turn it back on. And the vibrate mode is a single switch, at least on my phone.
And for an example of how truly bad that can be, look at "Immortal".
Until we understand time better, the multi-verse remains pure fantasy.
Realize that by that interpretation, somewhere there would a representation of every god humankind has ever devised. I'll withhold signing up for that theory until there's some backing for it, no matter how good (or bad) some of the sci-fi stories on the topic are.
You're making the claim he is not dead. Prove it. Failure to provide tangible proof will support the hypothesis that he is completely dead.
You might as well claim that he's alive on Jupiter or something even more whacky.
Disingenuous at best, since both parties flagrantly do this as a standard practice. The going broke aspect is because one party in particular believes that we can spend and lower taxes. If they truly wish to lower the spend rate, they could start by removing all congress people from federal payrolls. Since they're supposedly employed by and on behalf of their states, let the states pay them and their office staff. Once removed from federal funds, perhaps they could then look at the spending with a less biased eye.
I dig into various aspects. My job is to evaluate the veracity of their resume regarding experience, as well as the full breath of their experience, beyond what is shared in the resume.
What's funny about that - I once ran into a single class that had more LOCs than that. And it was just one among many hundreds, possibly thousands. But this class stood out for many reasons, not least in that it had a cyclomatic complexity of over 200 after the first round of simplifying refactoring.
These are the ones that kill me. I know of one that was hired as a high level architect. Needless to say, not a single project succeeded under him.
I interview many people who talked their way past the first screen or two, but start failing in less than 5 minutes. I don't think we've let a good one go, and we've only hired one questionable one out of the last 10 successful interviews.
Java would be about the same, shockingly.
...After all, if you have to spend 45 minutes looking up how to do a basic loop, then you're probably not experienced enough for anything beyond entry level (if that), so it helps weed out the people who are outright lying about skills.
I'd say if you need to spend time looking up how to do a basic loop in a language you're supposed to know, perhaps coding isn't a profession you should be in. I hear McDonald's is hiring.
so this should take you what, about 3 minutes, given a normal typing speed, compile and run time?
You have already been numbered - courtesy of your DNA.
Perhaps it'll mean they get more money devoted to securing the site after this has blown over - time spent testing the site and looking at security is probably more important than the specific technology used (almost every major framework has regular security problems like this), contrary to the righteous flaming and trolling for asp.net/perl/php/other tech which is bound to erupt in the wake of your post.
The best answer to this would be to not use a system that is known to not be secure to begin with. That's a massive failure on the developer's part.
QED
Perhaps, except for the fact that building your security out of what essentially is the equivalent of a rail fence to keep out a flood is doomed to fail. (See what I did there?) There are tools that can work for your stated purpose, and there are tools that are wholly unsuited to the intended application. RoR falls into the latter camp. Oh, and then there's the fact that I didn't talk about about technology xyz, but the actual one selected, and limited my comments to facts regarding said technology. Most other technologies don't have this flaw as a core feature, you have to code it that way. So you might want to revisit your "QED".
The best answer to this would be to not use a system that is known to not be secure to begin with. That's a massive failure on the developer's part.