AFAIK, most medical trials assume a Gaussian distribution for reactions in humans. With programmers, the distribution is not Gaussian. There is a short head of extremely good programmers, and a long tail of average ones (and a few bad ones).
The good programmers massively outperform the average, so if you have a few good programmers in your team, you can see massive productivity gains.
Accidental complexity today is dominated by the overheads of communication. Most agile methods require increased, frequent communication. This keeps the knowledge to be absorbed at one shot to a fairly small value.
It also depends on the team members. If one team has people in the top 10%, and the other team has average programmers, the methodology will be mostly irrelevant.
The question is whether "labour" is a trade good. The US claims it isn't, developing nations claim that labour is a trade good on the same scale as physical goods, or consulting services.
Well, free trade was essentially allowing US consumer goods to be imported by third world countries for cheap, while the US would be free to get cheaper raw materials from them.
Now the US has outsourced manufacturing to China, and the third world has mostly figured out that services are exportable too. In the US, time is valuable, money is cheap. In the third world, money is valuable, time is cheap. So you can have a trade of both, according to the same rules.
The employer gets cheaper time, the third world employee gets money, and if good enough, might even find it worth immigrating. It should be a win-win, except for those who are being undercut. Boohoo, our parents were undercut in the manufacturing segment by more efficient US technology, we are simply asking the US to play by the same rules.
The US pushed Free Trade on the rest of the world. Trouble is, a large portion of the rest of the world thinks that labour is a trade component, and not an immigration component. Part of the free trade game is that you reduce trade barriers. You have goods to sell, I have services to sell. Hence, the US is expected to reduce barriers in trading services, instead of goods.
The US has all rights to determine immigration policy. Trade policy, OTOH, is to be handled by trade agreements, and H1B visas are trade issues, not immigration issues.
Threads are hard, and shouldn't be used when possible. Using green threads, event driven asynchronous IO and processes helps is easier with message passing, and just as or more performant.
Ideas are expensive. They work in the exact opposite way from implementations though. You have to spread them, and let a thousand implementations bloom.
I currently work at Directi [1]. Official abuse policy when I don't get involved is to suspend the domain.
Abuse policy when I get involved is to suspend the customer (that's a few hundred domains for this sort of crap, or a few months ago, a few thousand. Unhappily, I don't have enough political clout yet to suspend large customers).
[1] Dealing with abuse issues is not part of the job description. That's a volunteer activity.
Slashdot Mirror
For those who don't live in developed countries, and those who have been laid off, 300$ is a lot of money.
The Vogons will demolish it to build a hyperspace bypass.
Alternatively, you can convince some people to sacrifice their lives for religion (or nation), and keep launching small, deadly attacks.
There is no enemy to hunt down, because they are right there amongst you.
Only in the US.
AFAIK, most medical trials assume a Gaussian distribution for reactions in humans. With programmers, the distribution is not Gaussian. There is a short head of extremely good programmers, and a long tail of average ones (and a few bad ones).
The good programmers massively outperform the average, so if you have a few good programmers in your team, you can see massive productivity gains.
Accidental complexity today is dominated by the overheads of communication. Most agile methods require increased, frequent communication. This keeps the knowledge to be absorbed at one shot to a fairly small value.
They built technology for that. It's called Java.
If you can leave any time you like, it's not a prison. It's just a really shitty hotel.
It's Hotel California^WMicrosoft.
It also depends on the team members. If one team has people in the top 10%, and the other team has average programmers, the methodology will be mostly irrelevant.
Emigrate to India, like all the others.
You use magnets? Real programmers use butterflies.
The question is whether "labour" is a trade good. The US claims it isn't, developing nations claim that labour is a trade good on the same scale as physical goods, or consulting services.
Well, free trade was essentially allowing US consumer goods to be imported by third world countries for cheap, while the US would be free to get cheaper raw materials from them.
Now the US has outsourced manufacturing to China, and the third world has mostly figured out that services are exportable too. In the US, time is valuable, money is cheap. In the third world, money is valuable, time is cheap. So you can have a trade of both, according to the same rules.
The employer gets cheaper time, the third world employee gets money, and if good enough, might even find it worth immigrating. It should be a win-win, except for those who are being undercut. Boohoo, our parents were undercut in the manufacturing segment by more efficient US technology, we are simply asking the US to play by the same rules.
The US pushed Free Trade on the rest of the world. Trouble is, a large portion of the rest of the world thinks that labour is a trade component, and not an immigration component. Part of the free trade game is that you reduce trade barriers. You have goods to sell, I have services to sell. Hence, the US is expected to reduce barriers in trading services, instead of goods.
The US has all rights to determine immigration policy. Trade policy, OTOH, is to be handled by trade agreements, and H1B visas are trade issues, not immigration issues.
Of what use is the health care system, if you cannot afford it?
Tell that to the Erlang folks.
Threads are hard, and shouldn't be used when possible. Using green threads, event driven asynchronous IO and processes helps is easier with message passing, and just as or more performant.
The browser is an interface to a very small part of the Internet.
The web is NOT the Internet
An iPhone is a web client with voice support.
Ideas are expensive. They work in the exact opposite way from implementations though. You have to spread them, and let a thousand implementations bloom.
League of Professional System Administrators. Ask, and thou shalt receive.
Money is fungible. Data is not.
You get a bash shell with the # prompt.
> game
Shall we play a game? You can choose between
(a) Tictactoe
(b) Chess
(c) Global thermonuclear war
>
The terrorist will watch in shocked silence as all the geeks say, "These are not the virgins you are looking for".
I currently work at Directi [1]. Official abuse policy when I don't get involved is to suspend the domain.
Abuse policy when I get involved is to suspend the customer (that's a few hundred domains for this sort of crap, or a few months ago, a few thousand. Unhappily, I don't have enough political clout yet to suspend large customers).
[1] Dealing with abuse issues is not part of the job description. That's a volunteer activity.
Yes, and yes. Nameservers in dynamic IP space is definitely fast-flux territory.
It worked well for the auto workers too.