These days, I test code for a living. I used to design code for a living, but really, how many times can you write "for (i = 0; i < 80; i++)" before you realize your chromosomes are devolving?
Testing involves tons of coding, but it's coding that goes to the heart of computational theory and takes in all the nuances of intended and unintended and irrelevant effect.
In the process of testing code I discover that even the best software engineers, on their best days:
1) make design errors 2) fail to review their specifications for errors 2) code errors into their programs and insert new errors into code that is otherwise specified properly 4) forget what their own code does and use it incorrectly 5) ship it anyway unless some regulating authority demands otherwise
(yes, if you catch it, there's a joke in there)
Some software is bug-free, or as near as 5 hours per line of additional testing and review can make it.
Oh, and I've turned in 100-hour weeks in my past life as a programmer, with no greater a bug rate than normal, but 2X to 5X the code of a 50-hour week.
You can't beat focus for increasing output produced to a consistent thesis.
And code, it turns out, is a lot like any other kind of writing. Come back to your own stuff six months later, and you probably won't even recognize it, and you probably can find several ways to change every function, method, class, structure, or combination thereof.
These days, I test code for a living. I used to design code for a living, but really, how many times can you write "for (i = 0; i per line of additional testing and review can make it.
Oh, and I've turned in 100-hour weeks in my past life as a programmer, with no greater a bug rate than normal, but 2X to 5X the code of a 50-hour week.
You can't beat focus for increasing output produced to a consistent thesis.
And code, it turns out, is a lot like any other kind of writing. Come back to your own stuff six months later, and you probably won't even recognize it, and you probably can find several ways to change every function, method, class, structure, or combination thereof.
The fact is, there isn't any way to certify this thing to occupy airspace on the planet Earth.
If it breaks, it's a 60-thousand-mile kevlar bandsaw blade whipping itself around in the sky.
It would end viability for low-earth-orbit satellites.
It would have to be included in weather reports for pilots.
It would have to be tracked by NORAD and figured into launch windows (and it would be the only thing they track that would have primarily random stochastics).
It would scrape the ground, cutting down or tearing up everything and everyone it touches as it wraps itself twice around the world.
Yeah, it's a fun toy for us geeks to play with in miniature at our basilicas, but unless someone repeals common sense planetwide, you can forget about having it fly.
Hardware buffering of the MPEG3 stream to prevent layer change pauses is a lot cheaper than a new and incompatible technology, and most DVD players seem to have it already.
You can't retrofit it, so it means buying a whole new player.
And adding parts doesn't make players more attractive. Introducing new technologies does.
The only people who stand to benefit from not changing over to blue lasers is the people who actually make the laser chips for the red lasers and would have to pay a royalty (maybe) to make blue lasers.
The rest of it is fungible.
And the first guy to mix the multilayer with the blue laser wins the whole pie.
Taking power from the wind won't reduce worldwide enthalpy.
It will increase worldwide entropy, but that was going to happen anyway.
Only this way, we get something out of it by passing the enhalpy through our homes instead of letting the entropy decrease moving discarded plastic grocery bags around in alleyways.
And don't worry. As long as the sun shines, we get more every day.
There are costs over and above salary that keep outsourcing from being profitable in almost all cases.
Bush removed one of the major barriers and increased outsourcing by several times its old level.
Now virtually the entire code-producing industry has left our shores, and taken most of the intellectual property value of our investment in technology with it.
This is not a good thing, and trying to make it look like a good thing is putting lipstick on a virus.
I think you're one of those middle-skill code monkeys who buys the "consultant" label your job-shop strapped onto you, and thinks $40/hour is "good pay".
My company advertises for jobs about once per quarter. When we do, we get over 3,000 resume's.
In 1999 and 2000, we'd get 5 or 6 per listing.
You're totally deluded if you think that sending the entire core of the information technology industry overseas is in any way good for the domestic job market.
For the next 2 years (until the '08 election season begins) we should focus on making preparations to bug out of Bushitania in case he goes completely over the edge.
We can always enlist our foreign allies to help us get our country back. The way the Afghanis and Iraqis did. The Iranians are still waiting for our help.
You remind me of the Germans who didn't realize Hitler was all that bad until after the war when they were marched at gunpoint into the concentration camp outside their town to see what they had "voted" for.
We, the people of the United States of America, paid over a $Trillion to create this industry. It was generating about $3 Trillion a year in wages--real economic activity.
Now it's been handed to China and India.
It's not being used to enrich our native land, it's being used to enrich our moneyed elites.
China and India couldn't have damaged America's economy more if they had fought a war against us and won.
Just remember that George W. Bush reduced the outsourcing tax from 25% to 5% when you vote on November 2.
Slashdot Mirror
Chase your kids outside every day!
Will he go over to the dark side, or will he spend the next 10 years fixing all the stupid errors in the Encarta encyclopedia?
Embargoing my Usenet posts violates MY TOS. Not to mention everything copyright stands for.
Anyone who wants to "leech" off any site hosting any of my posts has my permission.
And I'll sue Google if they don't.
Force?
It's online. At google.
And as has been noted, just about everything in it is copyright to the authors, not Google.
A few lines of perl later, you have your own copy, a few months of bandwidth later.
Where I live, riding your bike with headphones is illegal and will result in a $130 ticket.
Then the terrorists have already won.
I can generate well over 300 watts on a bicycle. You can generate 100 watts essentially indefinitely without breaking a sweat.
You want to listen to your iPod? Hook it up to your bike!
I wear my iPod when I'm on my bike. Imagine how much cooler it would be if it didn't neeed a battery...
(LET'S TRY THIS AGAIN, JUST ONCE FOR IRONY...)
These days, I test code for a living. I used to design code for a living, but really, how many times can you write "for (i = 0; i < 80; i++)" before you realize your chromosomes are devolving?
Testing involves tons of coding, but it's coding that goes to the heart of computational theory and takes in all the nuances of intended and unintended and irrelevant effect.
In the process of testing code I discover that even the best software engineers, on their best days:
1) make design errors
2) fail to review their specifications for errors
2) code errors into their programs and insert new errors into code that is otherwise specified properly
4) forget what their own code does and use it incorrectly
5) ship it anyway unless some regulating authority demands otherwise
(yes, if you catch it, there's a joke in there)
Some software is bug-free, or as near as 5 hours per line of additional testing and review can make it.
Oh, and I've turned in 100-hour weeks in my past life as a programmer, with no greater a bug rate than normal, but 2X to 5X the code of a 50-hour week.
You can't beat focus for increasing output produced to a consistent thesis.
And code, it turns out, is a lot like any other kind of writing. Come back to your own stuff six months later, and you probably won't even recognize it, and you probably can find several ways to change every function, method, class, structure, or combination thereof.
These days, I test code for a living. I used to design code for a living, but really, how many times can you write "for (i = 0; i per line of additional testing and review can make it.
Oh, and I've turned in 100-hour weeks in my past life as a programmer, with no greater a bug rate than normal, but 2X to 5X the code of a 50-hour week.
You can't beat focus for increasing output produced to a consistent thesis.
And code, it turns out, is a lot like any other kind of writing. Come back to your own stuff six months later, and you probably won't even recognize it, and you probably can find several ways to change every function, method, class, structure, or combination thereof.
"Tell them that we're returning to our roots," Schwartz said, referring to the company's renewed focus on the Solaris operating environment.
That's not their roots.
Solaris is not SunOS.
I don't know why anyone thinks that's "Funny".
The fact is, there isn't any way to certify this thing to occupy airspace on the planet Earth.
If it breaks, it's a 60-thousand-mile kevlar bandsaw blade whipping itself around in the sky.
It would end viability for low-earth-orbit satellites.
It would have to be included in weather reports for pilots.
It would have to be tracked by NORAD and figured into launch windows (and it would be the only thing they track that would have primarily random stochastics).
It would scrape the ground, cutting down or tearing up everything and everyone it touches as it wraps itself twice around the world.
Yeah, it's a fun toy for us geeks to play with in miniature at our basilicas, but unless someone repeals common sense planetwide, you can forget about having it fly.
Hardware buffering of the MPEG3 stream to prevent layer change pauses is a lot cheaper than a new and incompatible technology, and most DVD players seem to have it already.
You can't retrofit it, so it means buying a whole new player.
And adding parts doesn't make players more attractive. Introducing new technologies does.
The only people who stand to benefit from not changing over to blue lasers is the people who actually make the laser chips for the red lasers and would have to pay a royalty (maybe) to make blue lasers.
The rest of it is fungible.
And the first guy to mix the multilayer with the blue laser wins the whole pie.
It may use red lasers, but it won't play in current players.
As people are upgrading, the phrase "no layer-change pause" will become the marketing mantra of the blue-laser crowd.
And they will win.
Someone isn't paying attention.
Taking power from the wind won't reduce worldwide enthalpy.
It will increase worldwide entropy, but that was going to happen anyway.
Only this way, we get something out of it by passing the enhalpy through our homes instead of letting the entropy decrease moving discarded plastic grocery bags around in alleyways.
And don't worry. As long as the sun shines, we get more every day.
There are costs over and above salary that keep outsourcing from being profitable in almost all cases.
Bush removed one of the major barriers and increased outsourcing by several times its old level.
Now virtually the entire code-producing industry has left our shores, and taken most of the intellectual property value of our investment in technology with it.
This is not a good thing, and trying to make it look like a good thing is putting lipstick on a virus.
False.
US companies would have continued to run their domestic operations and even import labor, while selling the results overseas.
Why are you distracting from the truth?
The corporations haven't moved.
Just the jobs.
> How many of those 3,000 are qualified for the job? How do you determine who to hire?
Very few. Most are just desperate.
As we're a real consulting company, how we determine whom to hire is a trade secret.
I am changing things.
The primary problem is right-wing ignorance.
One retard at a time, son.
Clinton let China work on an equal footing in the world so we'd have a huge market to expand into.
Bush handed them our footing, and got a nifty pajama top in return.
I think you're one of those middle-skill code monkeys who buys the "consultant" label your job-shop strapped onto you, and thinks $40/hour is "good pay".
My company advertises for jobs about once per quarter. When we do, we get over 3,000 resume's.
In 1999 and 2000, we'd get 5 or 6 per listing.
You're totally deluded if you think that sending the entire core of the information technology industry overseas is in any way good for the domestic job market.
Note to Cons:
Get over what? Republican sophistry? The reversal of the American Revolution?
We're going to rip your idiot chimp-like "President" to shreds for four years, and there isn't a god damned thing you can do about it.
You pinched off that turd, you sit in it.
Not any more.
For the next 2 years (until the '08 election season begins) we should focus on making preparations to bug out of Bushitania in case he goes completely over the edge.
We can always enlist our foreign allies to help us get our country back. The way the Afghanis and Iraqis did. The Iranians are still waiting for our help.
Yet another duped traitor.
You remind me of the Germans who didn't realize Hitler was all that bad until after the war when they were marched at gunpoint into the concentration camp outside their town to see what they had "voted" for.
We, the people of the United States of America, paid over a $Trillion to create this industry. It was generating about $3 Trillion a year in wages--real economic activity.
Now it's been handed to China and India.
It's not being used to enrich our native land, it's being used to enrich our moneyed elites.
China and India couldn't have damaged America's economy more if they had fought a war against us and won.
Just remember that George W. Bush reduced the outsourcing tax from 25% to 5% when you vote on November 2.
You have no rights.
You are not a corporation.
Your imagination outstrips your power.