Its more than that. Managers prefer mediocre programmers because then you are not dependent on them.
Managers have this dream that programmers are a kind of generic glorp that can be poured into any job slot and be easily replaced with another generic glorp programmer.
One manager had this dream of putting all programmers for a multi billion dollar company into a single oncall rotation. Whoever was up that night would cover accounting, inventory, plant, invoicing, database, pc problems, etc..
Deloitte tried classical waterfall for our SAP implementation.
The specs delivered by the first wave (who got bonuses, parties, and 24 months of 45 hour weeks) were not even FUNCTIONAL in many cases and did not capture essential business rules. Noone at the start really knew what was right or wrong so they just wrote up crap and it got signed off on as complete specs.
Then the rest of us got 36 months of 60 to 80 hour weeks (multiple deaths, non fatal heart attacks, divorces) doing the work in a waterfall mode with a FIXED schedule as features were constantly being discovered.
For a large project, you really need to do a prototype and then throw it away and then do the work again.
But fundamentally, it was the bad market which helped them abuse everyone so badly and which lead to so many bad decisions (the executives making the decisions were sending out emails at 9pm and responding at 3am. They went multiple years with basically no sleep just like the rest of us... and it showed in the quality of their decisions).
As I said in my other post, I prefer RUP for the focus on resolving risk early and the time boxed delivery of functional code. Not because you can succeed-- but because you can prove you are failing so much sooner and adjust scope, resources, or cancel the project.
I very much doubt they used a device that moved back and forth and selectively deposited a layer of material and then fused it together with heat or glue.
Your brick examples would be more suitable if they moved the serfs back and forth on a lift and the serfs deposited bricks as they passed over an area that was supposed to have bricks.
That's why we have different words: "Building" and "Printing".
You are right about the definitions. However it seems pretty obvious they mean the total bandwidth consumed during a period. Otherwise their statement makes no sense.
Consider:
"You also may not exceed the bandwidth usage limitations that Verizon may establish from time to time for the Service"
combined with
They physically block you from exceeding your bandwidth
. I.e. you CAN'T exceed their bandwidth. It's not physically possible per your own post.
I can't find the link for this but there is already a business with a huge 3d printer which uses sand/cement. The printer is mobile and can be set up on site.
2900k LED and CFL- for whatever reason looks pink or orange-- especially when they first start (and even LED's have some ramp up time to reach full luminance).
However, the G7 brand produces light indistinguishable from incandescent bulbs (based on blind testing with picky friends).
The brand isn't the key. The 3000k is.
Personally, sort of prefer the 3500k at home depot in the red packaging for "true white".
5000k looks blue. I think normal sunlight doesn't look so blue because it's bouncing off of green plants brown/yellow/green grass and warm colored objects on the ground before entering your house and eyes.
Just not the implications of iterating microevolution over even ten thousand years-- much less a million-- much less a hundred million-- much less a billion years.
My main point of irritation is that I can't legally buy movies, medicine, software development packages, and many other products for the extremely low price the same corporations legally sell them to indians and chinese for.
I have to pay $19.99 for a movie selling legally in china for $2.49. I have to pay $5.00 a day for blood pressure medication selling legally in india for 10 cents.
It's ILLEGAL for someone to buy a bunch over there and ship it back here and sell the movies for $3.49 and the pills for 20 cents (100% mark up).
A few years ago Microsoft was GIVING development suites to indians free while I had to pay $750 for the same product.
Indian wages (as of novermber 2012) were going up 20%. China is seeing 12% to 100% annual wage inflation.
It's been a long painful walk, but sometime in the next 4-8 years it won't be worth it to offshore any more. These automation programs are a leading edge. Infosys also is trying to rebrand themselves from being a company that sells legions of code monkeys and grunt programmers to a company that sells managers and ceos. That's also a sign of the increasing wage structure.
I was lucky. I lived on half of what I made since 2000 and I was able to retire early. Now I do massage therapy, draw, and paint for fun. I'm looking at doing some programming for fun but haven't done so yet. Either Libreoffice (I read they are friendly), or Android (for my dnd game), or some kind of board gaming table software.
Infosys does something else that american companies used to do with Aramco.
They bring a bunch of infosys people over, warehouse them near the client, and pay them indian wages. They keep them in the country for six months-- preferably from july to december so they can keep them in the country for six months until the next july.
Then they ship them back home. They were never american employees to begin with. They were indian employees. Which leaves us competing here with experienced software developers working for under 30k. It was some special kind of non h1b visa. Perhaps an L1?
The company I retired from laid off about 5k people-- found it had to hire about 800 of those back (and is having a hard time getting suck.. people... to take those jobs).
It's designing it's order entry system to allow it to lay off most of its ma and customer support (another 8000 or so people). But it's SO obvious about it that its losing the good staff which is ironically slowing down the automation.
One thing to watch out for is oversell by the retirement industry.
As I said above, only 1.8% of us make it to 90. If you are in poor health or your parents and grandparents all died by 80, your odds of being in the group that makes it to 90 are not good. A lot of people really "know" they are going to die before 80 based on their health and parents mortality.
From experience, when you retire your spending drops enormously.
Your apple comment is odd. Didn't we have an article on slashdot that the "jobs" they were bringing back were almost all going to be done by robots?
Five million people went on social security between 2000 and 2009. Five million people went on social security in 2010 and 2011 alone (numbers not in ofr 2012 yet).
The boomers (71 million more to go), the chinese boomers (460 million), and the european boomers (I don't have a figure) are going to be retiring (or dying) fast over the next 18 years.
Only 15% of men and under 10% of women work past age 67 (despite statements that they have to or want to when they were younger).
Half the men are dead by age 75, half the women are dead by age 78.
Currently, only 1.8% are making it to age 90. They make up under 1% of the population but that's because of immigration and population growth since their cohort was born.
I think this boomer situation is going to hit really hard between now and 2016. Essentially, an extra 3.6 million people retire compared to the base rate. Then in 2017, it rises to 2 million extra people per year. That continues for the next 18 years. So 11.6 million extra people retire (from a total population of about 28 million) over the next 8 years alone. That's enough to eradicate the unemployment rate.
And... at least in my case when my early boomer parents passed away, I'd been saving so hard that I was able to retire at 52 and I didn't even go on social security.
So I guess I think thing will get really good for employees between now and 2020 (and probably be quite nice by 2016).
However, robotics and automation are coming on very fast and i think after 2020, that trend will cancel many of the benefits of the fast retirement. It gets very singularity like by the 2030's.
Oh yea, and the life expectancy you quote is almost entirely due to infant mortality. If you made it past 12, you had a very good chance of making it to 60. Look it up.
I made the same mistake years ago and was corrected (tho I was saying life expectency was 45).
Think of it this way.
2 people are born. One dies at age 1 The other dies at age 69. Their average life expectancy is 35 years.
Most hunter gatherers "worked" about 4 hours a day and socialized the rest of the time. They mostly slept from dusk until dawn.
Working 60 hours or more is strongly associated with higher risk of death from heart attacks and heart disease, higher blood pressure, unclear thinking ( 21 hours in one day makes you the equivalent of being legally drunk), higher risk of multiple kinds of cancer, lowered immunity (which means diseases that would make you sick if you were more rested kill you instead). Accidents have been proven to be much more likely (Surgeons and Doctors are being moved away from these schedules because patients were dying or being seriously injured by errors due to lack of rest).
I agree- some people can work 80 hours a week. And some people can run multiple miles at under 4 minutes per mile. Most people get sick and die. And a lot of people just collapse and are unable to continue working.
Slashdot Mirror
Its more than that. Managers prefer mediocre programmers because then you are not dependent on them.
Managers have this dream that programmers are a kind of generic glorp that can be poured into any job slot and be easily replaced with another generic glorp programmer.
One manager had this dream of putting all programmers for a multi billion dollar company into a single oncall rotation. Whoever was up that night would cover accounting, inventory, plant, invoicing, database, pc problems, etc..
Deloitte tried classical waterfall for our SAP implementation.
The specs delivered by the first wave (who got bonuses, parties, and 24 months of 45 hour weeks) were not even FUNCTIONAL in many cases and did not capture essential business rules. Noone at the start really knew what was right or wrong so they just wrote up crap and it got signed off on as complete specs.
Then the rest of us got 36 months of 60 to 80 hour weeks (multiple deaths, non fatal heart attacks, divorces) doing the work in a waterfall mode with a FIXED schedule as features were constantly being discovered.
For a large project, you really need to do a prototype and then throw it away and then do the work again.
But fundamentally, it was the bad market which helped them abuse everyone so badly and which lead to so many bad decisions (the executives making the decisions were sending out emails at 9pm and responding at 3am. They went multiple years with basically no sleep just like the rest of us... and it showed in the quality of their decisions).
As I said in my other post, I prefer RUP for the focus on resolving risk early and the time boxed delivery of functional code. Not because you can succeed-- but because you can prove you are failing so much sooner and adjust scope, resources, or cancel the project.
Two principles were key and could be used in any methodology.
1) Address risky (new technology, undefined specs, etc.) first
2) Regular time boxed functional builds.
If you can't address the risks successfully, then at least you can cancel the project early.
As I said, It's clear to me they are using bandwidth to mean consumption of your bandwidth during a period.
You can't violate a rate that they control (and really that is controlled by those upstream of them too).
You can violate their consumption limits unless they cap them.
Be legalistic all you want- it doesn't matter- they'll call you up and cut your service.
I very much doubt they used a device that moved back and forth and selectively deposited a layer of material and then fused it together with heat or glue.
Your brick examples would be more suitable if they moved the serfs back and forth on a lift and the serfs deposited bricks as they passed over an area that was supposed to have bricks.
That's why we have different words: "Building" and "Printing".
You are right about the definitions. However it seems pretty obvious they mean the total bandwidth consumed during a period. Otherwise their statement makes no sense.
Consider:
"You also may not exceed the bandwidth usage limitations that Verizon may establish from time to time for the Service"
combined with
They physically block you from exceeding your bandwidth
.
I.e. you CAN'T exceed their bandwidth. It's not physically possible per your own post.
and also this part spells it out ...
"You also may not exceed the bandwidth usage limitations that Verizon may establish from time to time for the Service"
I think in this case it was more like
average User Week 1: 5gb , Week 2: 10gb , Week 3: 12gb , Week 4: 6gb
vs
This User Week 1: 19TB , Week 2: 20TB , Week 3: 19TB , Week 4: 19TB
It sounds like it was covered in their terms of service.
Companies can't sell product at a loss.
Things change... perhaps in another 10 years, 19TB will be on the low end of weekly usage.
I can't find the link for this but there is already a business with a huge 3d printer which uses sand/cement. The printer is mobile and can be set up on site.
It was referenced here last year I think.
2900k LED and CFL- for whatever reason looks pink or orange-- especially when they first start (and even LED's have some ramp up time to reach full luminance).
However, the G7 brand produces light indistinguishable from incandescent bulbs (based on blind testing with picky friends).
The brand isn't the key. The 3000k is.
Personally, sort of prefer the 3500k at home depot in the red packaging for "true white".
5000k looks blue. I think normal sunlight doesn't look so blue because it's bouncing off of green plants brown/yellow/green grass and warm colored objects on the ground before entering your house and eyes.
Just not the implications of iterating microevolution over even ten thousand years-- much less a million-- much less a hundred million-- much less a billion years.
They also collect a million dollars based on an actuarial expectation of paying out $850,000.
And then they spend $50,000 of that to reinsure outlays over a million dollars.
The synthesized extract from Khan's blood will never ever EVER be used again in any abrahms star trek film.
Agree... they didn't use your native vocabulary.
Try saying it as "zero". "Zee Roh".
It's one of those odd differences in dialect between our versions of english.
Wages are leveling out.
My main point of irritation is that I can't legally buy movies, medicine, software development packages, and many other products for the extremely low price the same corporations legally sell them to indians and chinese for.
I have to pay $19.99 for a movie selling legally in china for $2.49.
I have to pay $5.00 a day for blood pressure medication selling legally in india for 10 cents.
It's ILLEGAL for someone to buy a bunch over there and ship it back here and sell the movies for $3.49 and the pills for 20 cents (100% mark up).
A few years ago Microsoft was GIVING development suites to indians free while I had to pay $750 for the same product.
Indian wages (as of novermber 2012) were going up 20%. China is seeing 12% to 100% annual wage inflation.
It's been a long painful walk, but sometime in the next 4-8 years it won't be worth it to offshore any more. These automation programs are a leading edge. Infosys also is trying to rebrand themselves from being a company that sells legions of code monkeys and grunt programmers to a company that sells managers and ceos. That's also a sign of the increasing wage structure.
I was lucky. I lived on half of what I made since 2000 and I was able to retire early. Now I do massage therapy, draw, and paint for fun. I'm looking at doing some programming for fun but haven't done so yet. Either Libreoffice (I read they are friendly), or Android (for my dnd game), or some kind of board gaming table software.
Infosys does something else that american companies used to do with Aramco.
They bring a bunch of infosys people over, warehouse them near the client, and pay them indian wages. They keep them in the country for six months-- preferably from july to december so they can keep them in the country for six months until the next july.
Then they ship them back home. They were never american employees to begin with. They were indian employees. Which leaves us competing here with experienced software developers working for under 30k. It was some special kind of non h1b visa. Perhaps an L1?
The company I retired from laid off about 5k people-- found it had to hire about 800 of those back (and is having a hard time getting suck.. people... to take those jobs).
It's designing it's order entry system to allow it to lay off most of its ma and customer support (another 8000 or so people). But it's SO obvious about it that its losing the good staff which is ironically slowing down the automation.
It's increasingly common so it must not be too hard.
Some companies I deal with have no human "escape hatch" option available any more.
One thing to watch out for is oversell by the retirement industry.
As I said above, only 1.8% of us make it to 90. If you are in poor health or your parents and grandparents all died by 80, your odds of being in the group that makes it to 90 are not good. A lot of people really "know" they are going to die before 80 based on their health and parents mortality.
From experience, when you retire your spending drops enormously.
Your apple comment is odd. Didn't we have an article on slashdot that the "jobs" they were bringing back were almost all going to be done by robots?
Or really triggers that require 30-50 pounds pressure to pull.
I've been watching Voyager lately. THERE, they have female security officers.
Five million people went on social security between 2000 and 2009.
Five million people went on social security in 2010 and 2011 alone (numbers not in ofr 2012 yet).
The boomers (71 million more to go), the chinese boomers (460 million), and the european boomers (I don't have a figure) are going to be retiring (or dying) fast over the next 18 years.
Only 15% of men and under 10% of women work past age 67 (despite statements that they have to or want to when they were younger).
Half the men are dead by age 75, half the women are dead by age 78.
Currently, only 1.8% are making it to age 90. They make up under 1% of the population but that's because of immigration and population growth since their cohort was born.
I think this boomer situation is going to hit really hard between now and 2016. Essentially, an extra 3.6 million people retire compared to the base rate. Then in 2017, it rises to 2 million extra people per year. That continues for the next 18 years. So 11.6 million extra people retire (from a total population of about 28 million) over the next 8 years alone. That's enough to eradicate the unemployment rate.
And... at least in my case when my early boomer parents passed away, I'd been saving so hard that I was able to retire at 52 and I didn't even go on social security.
So I guess I think thing will get really good for employees between now and 2020 (and probably be quite nice by 2016).
However, robotics and automation are coming on very fast and i think after 2020, that trend will cancel many of the benefits of the fast retirement. It gets very singularity like by the 2030's.
Oh yea, and the life expectancy you quote is almost entirely due to infant mortality.
If you made it past 12, you had a very good chance of making it to 60. Look it up.
I made the same mistake years ago and was corrected (tho I was saying life expectency was 45).
Think of it this way.
2 people are born.
One dies at age 1
The other dies at age 69.
Their average life expectancy is 35 years.
Most hunter gatherers "worked" about 4 hours a day and socialized the rest of the time. They mostly slept from dusk until dawn.
Working 60 hours or more is strongly associated with higher risk of death from heart attacks and heart disease, higher blood pressure, unclear thinking ( 21 hours in one day makes you the equivalent of being legally drunk), higher risk of multiple kinds of cancer, lowered immunity (which means diseases that would make you sick if you were more rested kill you instead). Accidents have been proven to be much more likely (Surgeons and Doctors are being moved away from these schedules because patients were dying or being seriously injured by errors due to lack of rest).
I agree- some people can work 80 hours a week. And some people can run multiple miles at under 4 minutes per mile. Most people get sick and die. And a lot of people just collapse and are unable to continue working.
They should compare BTU's of cooling to see efficiency.
Dollars just compares costs.
Cost of power can due to many factors.
Note the security officers escorting the villain in the picture here...
ALL men.
Because, you need BIG STRONG ARMS to pull the trigger on a recoil-less phaser rifle.
I guess if a woman had been in the security detail, the villain wouldn't have escaped and the movie would have ended too quickly.