Code was not less buggy. It's less buggy now, there's just a much higher multiplier thanks to superior developer productivity tools.
As you said, 6000 lines, one bug.
How many bugs do you suppose are in our 300 Million line codebase?
Re:One person's myth is another person's fact.
on
Myths About Code Comments
·
· Score: 2, Insightful
Most are not hot shots. We have a programming test for applicants to my company. It is really close to trivial. 4 out of 5 applicants for the job of senior software engineer submit a solution so bad they are dismissed immediately. Out of the remaining 20%, only about 1 in 10 submits a solution I consider 'good' (and is therefore a person I consider a possible hot shot candidate). The rest are merely adequate and clearly not hotshot material.
So that's 2% hotshots at best by my reckoning. Of course, this ignores the fact that our trivial programming problem probably pisses off a few hotshots enough that they don't submit, but we don't want to hire that kind of personality, hotshot or not.
It's even worse than not one person with one opinion. It's not even one audience. The self selecting sample who read apple stories is not the same group as the self selecting sample who read google stories.
Y does something bad to X X sues Y Y agrees to pay X say $1m as part of the lawsuit Y can't comment forever If X talks then X violated the agreement and Y can sue them for breach of contract. Since quite often the statue of limitations has run out on the original bad act, X could end up deeply underwater.
In fact in real lawsuits it is always X who can't comment forever. If X talks then Y can sue them for breach of contract, to recover the $1M they paid, and more.
Right, but the gps question, the one I was directly answering, was whether your settlement was worth anything if the person ordered to pay could just walk away. Your answer was for whether the other person, the person ordered not to disclose in exchange for the payment, could just walk away.
That's a list of how long you can sue your insurance for failure to cover, not a private party. Yes, there are some exceptions for specific contractual situations like that, but not on the general case being discussed.
In any case, you've also reversed the settlement violation being discussed from the suee being the violator to the suer.
Well that just makes no sense. If you were effectively offering higher than contract rates of pay, I don't know a single contractor who would turn that down. I've done a lot of contracting, and would always have been willing to take such an offer. It's not like the employment contract comes with some long term commitment that you can't back out of. Yours must have been a really exceptional case... did you have some problem with your work environment maybe?
In any case, yours does not represent more than a tiny minority of h1b experiences.
I've yet to see it in reality though, and i've met a couple hundred h1bs at this point. For every one, I alone know dozens of programmers who would and could have taken the job if the pay rate had been what you would have to pay to get an American instead of an h1b.
There's typically no statute of limitations placed on bringing a civil suit. You're thinking of criminal. And with criminal, there is no out of court settlement allowed, as the action is brought by the state, not by a private party.
In any case, you'd be stupid to accept a slow-release payment. Why give up your suit for something Y can ever withdraw?
I have seen hundreds of h1bs. Not one of them had a skill that was not available from numerous unemployed american programmers.
Every one of them was paid less than Americans doing the 'same' job (note: technically, the job definition was different, which is how they game the system. The work in fact was the same.)
The problem is you didn't raise the salary to a level competitive with contracting. If you did so, the contractors would be willing to make the employment commitment. Instead, you got a foreigner to take a job that could be done by an American if you were willing to pay the higher salary.
Thus, h1b drove down american IT salaries, and YOU are the proof.
Unfortunately, copyright is in diametric opposition to free speech. So you have to have the courts and the army back up the regime in suppressing the first amendment to have copyright work at all.
If they violate the contract, you get to walk away too, which means you may return to pursuing your previously dropped lawsuit, the fear of which is why they decided to settle in the first place.
Not true, the government has already proven it can get carriers to hand over communications without a warrant.
Re:And this is a nearly unsolveable problem.
on
GSM Decryption Published
·
· Score: 4, Interesting
It's a strange design given that they have unfettered access to the unencrypted backbone transmission. Why not just do the spying there, and use real security between cell and base? It gives you a real feeling of security, and them the same level of spying capability.
Consumer OS, and not XP, which is in widespread use. (why is consumer OS important to clarify? Because all that really matters for ipv6 adoption is the router OSs.)
Actually, due to the number of cosmic events, this is in fact true and inevitable. Every large earthquake is tightly correlated with a nice selection of cosmic events.
With the car deaths, you can reasonably claim that the dead knew the risks they were taking with their lives. We all pass the fatal wrecks every day on our way to work. That's why we all slow down to pay our respects as we pass.
It would be hard to argue that the dead in the towers should reasonably have assessed the risk of plane collision in their life plans. Everyone who works in a big tower since 9/11 certainly should, though. So we'll be less outraged the next time it happens, and even less outraged as it becomes a day to day thing.
Slashdot Mirror
Code was not less buggy. It's less buggy now, there's just a much higher multiplier thanks to superior developer productivity tools.
As you said, 6000 lines, one bug.
How many bugs do you suppose are in our 300 Million line codebase?
Most are not hot shots. We have a programming test for applicants to my company. It is really close to trivial. 4 out of 5 applicants for the job of senior software engineer submit a solution so bad they are dismissed immediately. Out of the remaining 20%, only about 1 in 10 submits a solution I consider 'good' (and is therefore a person I consider a possible hot shot candidate). The rest are merely adequate and clearly not hotshot material.
So that's 2% hotshots at best by my reckoning. Of course, this ignores the fact that our trivial programming problem probably pisses off a few hotshots enough that they don't submit, but we don't want to hire that kind of personality, hotshot or not.
But not in 3.5.6 (yes, popups allowed) :-(
It's even worse than not one person with one opinion. It's not even one audience. The self selecting sample who read apple stories is not the same group as the self selecting sample who read google stories.
Yes, as slashdot is a us-centric site, if you read the us-centric portions of that very page you'll see that I'm correct.
It's more like judging people by the cost of living where they come from. It's classism, not racism.
But the error in the 3rd line renders the last line nonsensical.
Yes, that comment seems confused.
In fact in real lawsuits it is always X who can't comment forever. If X talks then Y can sue them for breach of contract, to recover the $1M they paid, and more.
Right, but the gps question, the one I was directly answering, was whether your settlement was worth anything if the person ordered to pay could just walk away. Your answer was for whether the other person, the person ordered not to disclose in exchange for the payment, could just walk away.
That's a list of how long you can sue your insurance for failure to cover, not a private party. Yes, there are some exceptions for specific contractual situations like that, but not on the general case being discussed.
In any case, you've also reversed the settlement violation being discussed from the suee being the violator to the suer.
Well that just makes no sense. If you were effectively offering higher than contract rates of pay, I don't know a single contractor who would turn that down. I've done a lot of contracting, and would always have been willing to take such an offer. It's not like the employment contract comes with some long term commitment that you can't back out of. Yours must have been a really exceptional case ... did you have some problem with your work environment maybe?
In any case, yours does not represent more than a tiny minority of h1b experiences.
I've yet to see it in reality though, and i've met a couple hundred h1bs at this point. For every one, I alone know dozens of programmers who would and could have taken the job if the pay rate had been what you would have to pay to get an American instead of an h1b.
There's typically no statute of limitations placed on bringing a civil suit. You're thinking of criminal. And with criminal, there is no out of court settlement allowed, as the action is brought by the state, not by a private party.
In any case, you'd be stupid to accept a slow-release payment. Why give up your suit for something Y can ever withdraw?
That meme bugs the heck out of me. The internet IS a series of tubes. Plastic tubes with little metal or glass wires inside.
I have seen hundreds of h1bs. Not one of them had a skill that was not available from numerous unemployed american programmers.
Every one of them was paid less than Americans doing the 'same' job (note: technically, the job definition was different, which is how they game the system. The work in fact was the same.)
The problem is you didn't raise the salary to a level competitive with contracting. If you did so, the contractors would be willing to make the employment commitment. Instead, you got a foreigner to take a job that could be done by an American if you were willing to pay the higher salary.
Thus, h1b drove down american IT salaries, and YOU are the proof.
Unfortunately, copyright is in diametric opposition to free speech. So you have to have the courts and the army back up the regime in suppressing the first amendment to have copyright work at all.
You pay an h1b worker generous wages even though there are literally thousands of qualified americans begging for work?
If they violate the contract, you get to walk away too, which means you may return to pursuing your previously dropped lawsuit, the fear of which is why they decided to settle in the first place.
Not true, the government has already proven it can get carriers to hand over communications without a warrant.
It's a strange design given that they have unfettered access to the unencrypted backbone transmission. Why not just do the spying there, and use real security between cell and base? It gives you a real feeling of security, and them the same level of spying capability.
Consumer OS, and not XP, which is in widespread use.
(why is consumer OS important to clarify? Because all that really matters for ipv6 adoption is the router OSs.)
Actually, due to the number of cosmic events, this is in fact true and inevitable. Every large earthquake is tightly correlated with a nice selection of cosmic events.
A najor douchebag that wasn't evolved against.
With the car deaths, you can reasonably claim that the dead knew the risks they were taking with their lives. We all pass the fatal wrecks every day on our way to work. That's why we all slow down to pay our respects as we pass.
It would be hard to argue that the dead in the towers should reasonably have assessed the risk of plane collision in their life plans. Everyone who works in a big tower since 9/11 certainly should, though. So we'll be less outraged the next time it happens, and even less outraged as it becomes a day to day thing.