It would be a shame if that advice wasn't followed. It was posted anonymously, but it is obviosly posted by sombody that has lived it or tried to help someone else that has. Most of the other solutions happend in the later teens, so that doesn't help, or are circumstance specific.
REASONS WHY JOBS LEAVE THE U.S.
a.)Lack of big buisness kick backs. (Even though I hate the idea)
b.)High regulations. (Even though I love the idea)
*one negates the other neither destroys the planet
The cost of living in india is less, therfore people will work for less. Overhead is cheaper. Benifits are not always necessary, and when they are its usually cheaper. There are not as many government standards that a buisness has to follow. If you give a person who never had anything and you give them somthing, they will work there ass off. The money saving is outside this country, and big buisness will milk this contry dry of all of its revenue until the U.S. is a slum, then the cycle will repeat for some other unsuspecting country. In 100 years maybe things will be the other way around.
Lets point fingers in the direction of the people who have the bigger influence over this problem, the government, and big buisness. I hope you all remember who the government is. Its the people who live in this country as a whole.
I think they are smoking the helium. I've seen "Time Machine", and recall the freakiest part of the movie to me was when people populated the moon to mine it, then successfully blew it in half and crashed it into the earth. Can't wait to see what a "Morlock" really looks like.
I remember working for a company in Upstate NY that didn't give me much of a job descriptioin.
One day my job description ivolved finding and replaceing the starter on a drill rig. I found the rig in a swamp. (warning... run-on rant)I spent 2 hrs on my back in the swamp before I found out that the starter they gave me went to the engine that was in it before they replaced the engine with an older one which wasn't compatible.
I remember my clothes freezing to a garage floor once replacing an alternator on a honda civic, but it must have been a different job I had(nevermind that wasn't job related. It was work just not somthing that I got paid for).
On a different day I drove a company vehicle up to a different site where a few of the other workers got there vehicle stuck. After a long day of being a drillers assistant out in a field the other workers left in my vehicle expecting that I got theres unstuck(ie. great coworkers).
A few days later I was in a 2 story diameter by 200 yard rotating kiln used for making concrete. It was stopped for inspection due to a malfunction. But it was still cooling at 90 oC. By the end of the day I was finding cured concrete in my nose.
The list goes on and on with similar yet less spectacular stories of that summer job.
Here here. This is exactly correct especially when deadlines (wich nobody pays any attention to until the night before) are approching.
Pro's:
-The best time to find missing requirements is during design and analysis not halfway through the development and testing.
-In most cases the best roadmap for someone new to a project is the design documents not the code.
-Standards. Everyone knows what everything means without a translator.
Con's:(overcome with experience)
-Overdesign. Creating documents for the sake of having it is a waste of resources.
-People somtimes spend more time looking at the grammer than content.
-If the project is small enough you can somtimes(emphisis on somtimes) get away with just looking at the code, as long as you document what the code does and that it exists.
Recap/furthermore:
-review the requirements.
-analyze the problem and come up with some form of solution.
-design the solution.
-code the solution.
-test the outcome.(are the requirements met?)
Wow. What can you say to that? I didn't realize the passion involved with this. Sombody must have lost their first born. If thats the case I'm sure everyone supports you in your quest for vengence on Trident.
Slashdot Mirror
Indiana tried to set PI equal to 3.2 . http://en.wikipedia.org/wiki/Indiana_Pi_Bill
See the same subject below.
It would be a shame if that advice wasn't followed. It was posted anonymously, but it is obviosly posted by sombody that has lived it or tried to help someone else that has. Most of the other solutions happend in the later teens, so that doesn't help, or are circumstance specific.
REASONS WHY JOBS LEAVE THE U.S.
a.)Lack of big buisness kick backs. (Even though I hate the idea)
b.)High regulations. (Even though I love the idea)
*one negates the other neither destroys the planet
The cost of living in india is less, therfore people will work for less. Overhead is cheaper. Benifits are not always necessary, and when they are its usually cheaper. There are not as many government standards that a buisness has to follow. If you give a person who never had anything and you give them somthing, they will work there ass off. The money saving is outside this country, and big buisness will milk this contry dry of all of its revenue until the U.S. is a slum, then the cycle will repeat for some other unsuspecting country. In 100 years maybe things will be the other way around.
Lets point fingers in the direction of the people who have the bigger influence over this problem, the government, and big buisness. I hope you all remember who the government is. Its the people who live in this country as a whole.
I think they are smoking the helium. I've seen "Time Machine", and recall the freakiest part of the movie to me was when people populated the moon to mine it, then successfully blew it in half and crashed it into the earth. Can't wait to see what a "Morlock" really looks like.
I remember working for a company in Upstate NY that didn't give me much of a job descriptioin.
One day my job description ivolved finding and replaceing the starter on a drill rig. I found the rig in a swamp. (warning... run-on rant)I spent 2 hrs on my back in the swamp before I found out that the starter they gave me went to the engine that was in it before they replaced the engine with an older one which wasn't compatible.
I remember my clothes freezing to a garage floor once replacing an alternator on a honda civic, but it must have been a different job I had(nevermind that wasn't job related. It was work just not somthing that I got paid for).
On a different day I drove a company vehicle up to a different site where a few of the other workers got there vehicle stuck. After a long day of being a drillers assistant out in a field the other workers left in my vehicle expecting that I got theres unstuck(ie. great coworkers).
A few days later I was in a 2 story diameter by 200 yard rotating kiln used for making concrete. It was stopped for inspection due to a malfunction. But it was still cooling at 90 oC. By the end of the day I was finding cured concrete in my nose.
The list goes on and on with similar yet less spectacular stories of that summer job.
That could be dangerous.
After considering the Price/Feature ratio you have to include the "are the requirements being met?" factor.
Here here. This is exactly correct especially when deadlines (wich nobody pays any attention to until the night before) are approching.
Pro's:
-The best time to find missing requirements is during design and analysis not halfway through the development and testing.
-In most cases the best roadmap for someone new to a project is the design documents not the code.
-Standards. Everyone knows what everything means without a translator.
Con's:(overcome with experience)
-Overdesign. Creating documents for the sake of having it is a waste of resources.
-People somtimes spend more time looking at the grammer than content.
-If the project is small enough you can somtimes(emphisis on somtimes) get away with just looking at the code, as long as you document what the code does and that it exists.
Recap/furthermore:
-review the requirements.
-analyze the problem and come up with some form of solution.
-design the solution.
-code the solution.
-test the outcome.(are the requirements met?)
Wow. What can you say to that? I didn't realize the passion involved with this. Sombody must have lost their first born. If thats the case I'm sure everyone supports you in your quest for vengence on Trident.