I mean, it's not like a few thousand person-years of development by people with BS/MS/PhD's and tons of talent, skill, and passion is worth anything, right? And it's not like AutoDesk (to take your example) spent all those talent soaked man-years to develop a product specifically to market in China. That cost has already been amortized over many many sales in the western economy.
You forget that all developing economies emerged and prospered by ripping off and copying technology from developed economies (think Japan). They could re-invent the wheel, but they don't bother. That is not a true loss to the original wheel-inventor.
But that is the fallacy of such an argument. They say that the software traded has a value of $500 million, but the truth is that this is the value placed on it at western RRP prices. The true value of the software is much closer to the actual revenues that the pirates derive. This makes the revenue stream probably closer to a hundredth of that ($200 rrp say selling as a pirate copy for $5). If the pirates could make their $500 million, you bet they would.
College degrees might not expire, but they do depreciate in value. Try getting a college degree, sit on it for 10 years without gaining experience, and see how useful it is for you.
After a period of time, employers are usually looking for recent experience and demonstrated capability. Sure, they do expect to see a degree for most professional positions, but the degree alone (if at all) is not a passport for big-buck jobs.
Exactly the GPs point. The libraries are anally retentive, so the faculty staff get their illicit copies from the 'net (or multi-generation photocopies, as it was in my day)
Correcting my previous entry, it was allegedly a Hep B experiment, and the main peddler of this theory is Dr Alan Cantwell. I did a google check on his credibility and although the extremist media have latched onto the theory, there doens't appear to be much opposition to his work.
I'd be interested if anyone knows any commentary disputing his theory.
I have read reports that the HIV virus and the HHV8 virus were inadvertently transmitted to the New York gay population during some vaccination trials for Hepatitis C, the vaccine in which was developed in Rhesus monkeys contamintated with both HIV and HHV8 viri.
The gay population in these locations were targeted in these trials due to their known promiscuity and exposure to Hep C. Thus AIDS and KS is primarily associated with gay populations. Note that AIDS and KS are two separate illnesses which became prevalent at a similar period and both now associated with gay men.
I think it is a tragedy, of which most people have never heard.
...I can say that a project isn't necessarily a failure if you are smart enough to back out of it in safety before it becomes a total catastrophe. It is still a failure if nothing concrete is delivered, i.e. a totally aborted project. Of course, well documented lessons learned, particularly for investigating use of newer technologies, is something concrete. If the learnings aren't well documented, then this also is a failure, as far as a company is concerned, as the people who had the experience can move on, taking their knowledge with them.
From a company viewpoint, if you are "backing out" of a project, you still have expended some resources, so you'd want to see something for that, if you are to label it as any type of success.
I think you're confusing project prioritizing with delivering projects.
Your first example about balancing the HR project with the operations manager's project seems more about resourcing and scheduling multiple projects than one or the other individually being a failure. The inability to meet HR's schedule expectation is a project management failure, since embarking on that project without knowing it can be finished on time and budget is a failure.
I work for a large multinational engineering contractor, and quite frankly, the company is hopeless at scheduling and resourcing projects, mainly because the projects themselves aren't scheduled properly and the resource requirements calculated. We have about three people scheduling work for about 300 engineers, which is insufficient. This approach causes all sorts of slippage, scope abandonment and short cutting in a (futile) attempt to deliver on time(ish). This doesn't mean that individual projects are unachievable, more that there are insufficient resources to achieve all of them simultaneously. Proper scheduling and resourcing calculations would reveal this, and proper timing and allocation would enable all projects to proceed with less crisis management.
On your second example, you might start some type of R&D feasiblility study to investigate rollout of a new networking infrastructure (n vs g or b), but in fact that investigation is a project in itself. The project outcome is a "next stage", "later" or "abort". Implementation of the new infrastructure is an entirely different project, and should be planned separately.
Your third example is also not a failure, but a sound recognition that you don't have the resources to embark on the project and/or the returns on a successful implementation are not sufficient to justify the capital.
So I wouldn't dismiss the article's comments and recommendations. I think they are pretty much all valid, and if managers at your level recognised that (as the senior management where I work don't) and did something about it, then a lot of people would be a lot happier. The best thing to do about it? Stop pretending that "high level" schedules are sufficient. Recognise that detailed schedules are required and are all about activity durations and dependencies rather than the "gimme the dates" crap that gets bandied about in weekly project review meetings.
Do you really think that Iraq was about oil for domestic consumption? Consider that the modus operandi is to bomb the bejesus out of a country, and then exploit the resources for the purposes of subisdising the costs of cleanup. US military adventures are the pinnacle of pork barreling. The military-industrial complex gets a complete work-out, Halliburton et al make a load on the cleanup contracts, and the US Government gets to justify its part of the expenditure on the back of some demonized dictator.
Sure, oil lubricates this system, but don't be deluded into thinking that they're out their to help fill your Hummer.
I don't think any allowance for military intervention is required. It's most likely an unrelated issue.
Except that the +5VSB is still live, and quite often this rail has a 3A rating (so about 15W). Of course the mobo may not necessarliy draw this much when it is off, but still draws some power.
Wouldn't it be feasible to record and catalog the fonts and manipulations done by a particular site's CAPTCHA engine, and then script some type of automatic "OCR" to suit? Are these CAPTCHA's dynamically generated from an extended "character set" or are the distortions generated in real-time?
I can't get my head around why performing covers will incur royalties? I can understand that royalties might be required if CD is played in a public arena, but a live performance is it's own entity. It isn't a copy of a copyrighted work. It isn't even a performance of a written, copyrighted work (say a theatre production), which might incur royalties.
Cab anybody shed some light on this? Seems like stand-over tactics to me.
Actually, I think the biggest problem/risk is shipping. It would kinda ruin your day if something like Pasha Bulker decided to take out several of your wind turbines.
This is particularly the case with wind turbines, since the quantity and extent of distribution of the structures would be much more significant than offshore oil & gas installations.
You forget that all developing economies emerged and prospered by ripping off and copying technology from developed economies (think Japan). They could re-invent the wheel, but they don't bother. That is not a true loss to the original wheel-inventor.
But that is the fallacy of such an argument. They say that the software traded has a value of $500 million, but the truth is that this is the value placed on it at western RRP prices. The true value of the software is much closer to the actual revenues that the pirates derive. This makes the revenue stream probably closer to a hundredth of that ($200 rrp say selling as a pirate copy for $5). If the pirates could make their $500 million, you bet they would.
College degrees might not expire, but they do depreciate in value. Try getting a college degree, sit on it for 10 years without gaining experience, and see how useful it is for you.
After a period of time, employers are usually looking for recent experience and demonstrated capability. Sure, they do expect to see a degree for most professional positions, but the degree alone (if at all) is not a passport for big-buck jobs.
x) ???
is always required before:
x+1) profit!!!
Exactly the GPs point. The libraries are anally retentive, so the faculty staff get their illicit copies from the 'net (or multi-generation photocopies, as it was in my day)
[insert Olestra joke here]
Sure:
Correcting my previous entry, it was allegedly a Hep B experiment, and the main peddler of this theory is Dr Alan Cantwell. I did a google check on his credibility and although the extremist media have latched onto the theory, there doens't appear to be much opposition to his work.
I'd be interested if anyone knows any commentary disputing his theory.
I have read reports that the HIV virus and the HHV8 virus were inadvertently transmitted to the New York gay population during some vaccination trials for Hepatitis C, the vaccine in which was developed in Rhesus monkeys contamintated with both HIV and HHV8 viri.
The gay population in these locations were targeted in these trials due to their known promiscuity and exposure to Hep C. Thus AIDS and KS is primarily associated with gay populations. Note that AIDS and KS are two separate illnesses which became prevalent at a similar period and both now associated with gay men.
I think it is a tragedy, of which most people have never heard.
It comes complete with instructions (cypher-text of course) on how to win the War on Terror. Ask DVD Jon for the key.
...I can say that a project isn't necessarily a failure if you are smart enough to back out of it in safety before it becomes a total catastrophe. It is still a failure if nothing concrete is delivered, i.e. a totally aborted project. Of course, well documented lessons learned, particularly for investigating use of newer technologies, is something concrete. If the learnings aren't well documented, then this also is a failure, as far as a company is concerned, as the people who had the experience can move on, taking their knowledge with them.From a company viewpoint, if you are "backing out" of a project, you still have expended some resources, so you'd want to see something for that, if you are to label it as any type of success.
I think you're confusing project prioritizing with delivering projects.
Your first example about balancing the HR project with the operations manager's project seems more about resourcing and scheduling multiple projects than one or the other individually being a failure. The inability to meet HR's schedule expectation is a project management failure, since embarking on that project without knowing it can be finished on time and budget is a failure.
I work for a large multinational engineering contractor, and quite frankly, the company is hopeless at scheduling and resourcing projects, mainly because the projects themselves aren't scheduled properly and the resource requirements calculated. We have about three people scheduling work for about 300 engineers, which is insufficient. This approach causes all sorts of slippage, scope abandonment and short cutting in a (futile) attempt to deliver on time(ish). This doesn't mean that individual projects are unachievable, more that there are insufficient resources to achieve all of them simultaneously. Proper scheduling and resourcing calculations would reveal this, and proper timing and allocation would enable all projects to proceed with less crisis management.
On your second example, you might start some type of R&D feasiblility study to investigate rollout of a new networking infrastructure (n vs g or b), but in fact that investigation is a project in itself. The project outcome is a "next stage", "later" or "abort". Implementation of the new infrastructure is an entirely different project, and should be planned separately.
Your third example is also not a failure, but a sound recognition that you don't have the resources to embark on the project and/or the returns on a successful implementation are not sufficient to justify the capital.
So I wouldn't dismiss the article's comments and recommendations. I think they are pretty much all valid, and if managers at your level recognised that (as the senior management where I work don't) and did something about it, then a lot of people would be a lot happier. The best thing to do about it? Stop pretending that "high level" schedules are sufficient. Recognise that detailed schedules are required and are all about activity durations and dependencies rather than the "gimme the dates" crap that gets bandied about in weekly project review meetings.
Netcraft confirms it.
Do you really think that Iraq was about oil for domestic consumption? Consider that the modus operandi is to bomb the bejesus out of a country, and then exploit the resources for the purposes of subisdising the costs of cleanup. US military adventures are the pinnacle of pork barreling. The military-industrial complex gets a complete work-out, Halliburton et al make a load on the cleanup contracts, and the US Government gets to justify its part of the expenditure on the back of some demonized dictator.
Sure, oil lubricates this system, but don't be deluded into thinking that they're out their to help fill your Hummer.
I don't think any allowance for military intervention is required. It's most likely an unrelated issue.
...with other Zune The flaw in your argument...
...or some kind of technology with an 'x' in it. sex?Hmmm.. A new definition for news anchor?
He said the next one. Not the current one...
Except that the +5VSB is still live, and quite often this rail has a 3A rating (so about 15W). Of course the mobo may not necessarliy draw this much when it is off, but still draws some power.
Except that it is Siemens who involved, and Siemens Wind Power is based in Denmark.
Wouldn't it be feasible to record and catalog the fonts and manipulations done by a particular site's CAPTCHA engine, and then script some type of automatic "OCR" to suit? Are these CAPTCHA's dynamically generated from an extended "character set" or are the distortions generated in real-time?
I'd hope a shipping port would be closer than 100km from land...
A sea-star type TLP/a) would not suffer this problem, as the buoyancy and eccentricity of the tendons would provide a restoring moment. The amount of "residual" buoyancy (tendon pre-tension) could easily be designed to provide this.
I can't get my head around why performing covers will incur royalties? I can understand that royalties might be required if CD is played in a public arena, but a live performance is it's own entity. It isn't a copy of a copyrighted work. It isn't even a performance of a written, copyrighted work (say a theatre production), which might incur royalties.
Cab anybody shed some light on this? Seems like stand-over tactics to me.
Actually, I think the biggest problem/risk is shipping. It would kinda ruin your day if something like Pasha Bulker decided to take out several of your wind turbines.
This is particularly the case with wind turbines, since the quantity and extent of distribution of the structures would be much more significant than offshore oil & gas installations.