March 2004 - Posts

Richard Tallent Thinks Americans Aren't Smart Enough Anymore

In response to my comments on offshoring, Richard Tallent writes:

“Here's the issue: if we give away our best industries, we will not have anything *left* to export, except maybe lawsuits, Big Macs, and beaurocracy.

There *is* a difference between a factory worker and a software developer. The former rarely creates innovation on his own, but the latter (if he is good) does so regularly. We shouldn't protect every factory and farm, but we *must* protect young growth industries. Necessity is the mother of invention. If we aren't doing those jobs, we won't start those next Microsofts, we won't invent those new inventions. If we don't want to take the back seat in the next few decades of innovation, we must draw a line in the sand that protects the incentive for our children to work in fields such as engineering and computer science. “ [1]

There was a time when engineering and building automobiles was cutting edge, and the US had no problems staying at the forefront then without a million more laws being written banning the import of foreign goods or the outsourcing of labor. I get sick and tired of hearing people complain that the US just isn't smart enough to compete any more. If we truely aren't smart enough any more then there are plenty of better things to focus on, like improvements to our downward spiraling education system. If things just cost too much out here, then maybe we need to get rid of some tax burdens and do something about the littigations that are costing some of our most successfull and innovative companies millions of dollars a year in lost revenue and sales. Maybe we need to redefine what innovation is in the 21st century so that someone can't file a patents for every process they can dream up and milk the revenues of companies that are actually doing something. And maybe, just maybe, we need to stop acting like a bunch of babbies, go out there, and start kicking foreign ass with truely innovative American solutions. Solutions that make the few dollars and hour in cost savings irrelevant. Oh.. but no... we don't want to innovate. Better tools might make it easy for the average person to develop software and cost us highly trained developers our jobs. Let's just make laws against innovation and protect those jobs while we still can!

[1] http://www.tallent.us/PermaLink.aspx?guid=24150d52-d592-4627-b4cf-3c8ce1a89d7c

 

Posted by Jesse Ezell with 14 comment(s)

Dell Nixes Indian Customer Support

Thanks to Patrick for the link.

“Dell admits it has "learned its lesson" after being forced to drop its Indian call center last year following customer complaints about the quality of service.“ [1]

Another offshoring failure proves that we don't need laws to stop companies from offshoring. Global competition is a good thing. The best way to prevent offshoring is by providing higher quality services than the offshore companies.

[1] http://news.com.com/2100-1001_3-5182611.html?part=rss&tag=feed&subj=news

Posted by Jesse Ezell with 5 comment(s)

IT Offshoring

“Catherine Mann of the Institute for International Economics makes the case in favor of offshoring: High-tech hardware would have been 20% more expensive in the 1990s if not for offshoring. This spurred investment in more high-tech gear, boosting productivity and freeing up cash to plow into still more innovation. Plus, for every dollar spent on offshoring, the U.S. gets back $1.12 (and the global economy reaps another 33 cents), says a report from McKinsey consultants. Think about it: As more workers in India land higher-paying jobs, they can afford to buy more U.S. products, from processor chips to Hollywood films. By spreading the wealth, offshoring makes life a little better in some of the poorest regions of the world. “ [1]

I think all this anti-IT offshoring talk is rediculous. A lot of IT workers are not much more skilled (if at all) than the average assembly line worker. Why should they be paid so much more? If their jobs can be done by IT sneaker factories in Mexico, so be it. You don't see people like Don Box or Bill G getting laid off. They are much to important to their companies. If IT guys would rather sit around and complain all day instead of working on making themselves more competitive in the land of opportunity, maybe they don't deserve their jobs in the first place. Magazines always interview these guys who have been out of a job for like 2 years and finally end up working at McDonalds or something because they just can't find anyone willing to hire them. Wake up and smell the coffee. If no one else wants you either, is it any wonder that you were expendable?

I agree with Greenspan on this one:

"In response to these strains and the dislocations (outsourcing could) cause, a new round of protectionist steps is being proposed," Greenspan said. "These alleged cures would make matters worse rather than better. They would do little to create jobs; and if foreigners were to retaliate, we would surely lose jobs..."

"...We can erect walls to foreign trade and even discourage job-displacing innovation," Greenspan said. "The pace of competition would surely slow, and tensions might appear to ease--but only for a short while. Our standard of living would soon begin to stagnate and perhaps even decline as a consequence.

"Time and again through our history, we have discovered that attempting merely to preserve the comfortable  features of the present--rather than reaching for new levels of prosperity--is a sure path to stagnation," he said. [2]

Although laws making IT offshoring less attractive might have the short term benefit of slowing the IT job loss rate, it's long term effect will be to damage American companies in the global marketplace. The immediate effect will be that everyone else will be able to bring their solutions to market at 1/3 the cost, in many situations, or at a much faster pace, in situations where resources have been a limiting factor (sound like any projects you've worked on?). Longer term, it will lead to American consumers looking more and more to non-American software vendors for their software acquisitions (Toyota anyone...?), which definately will not be good for the American software industry either.

[1] http://www.forbes.com/home/free_forbes/2004/0412/094.html

[2] http://news.com.com/2100-1022_3-5172975.html

Posted by Jesse Ezell with no comments

Microsoft

This is a pretty interesting Slashdotted piece about tracking information embedded in some of Microsoft's PR documents. At the very least, it gives you an appreciation for the editing process that Microsoft goes through, which strips out stuff like ad hom. attacks before they make it to the press
Posted by Jesse Ezell with no comments

To GAC or not to GAC?

Chris and Ted are going back and forth on whether to use the GAC. Chris' conclusion is:

“1. Fixing critical bugs without touching the affected apps (and without breaking anything!) 2. Sharing types at run-time between assemblies deployed separately “ [1]

Ted's is:

“the GAC isn't for making silent upgrades of libraries that apps depend on--it's the side-by-side versioning story, first and foremost, that demands the GAC's existence. Yes, I could go ahead and put those third-party libraries into my private application directory, but why? If I start looking to bundle everything I depend on as part of my application's footprint, why not include certain key libraries like KERNEL32.DLL or USER32.DLL, as well? If we take this "avoid the GAC" idea far enough, we're back to Joel's request for a static linker again, and I just don't want to see us go back to the pre-Win16 days all over again.“ [2]

Well, there is at least one very good reason to always GAC DLLs: ASP.NET doesn't support strong named assemblies. There is this nasty little bug whereby if you place strong named DLLs in your bin directory, indexing services will lock up the DLL every once and a while and the web app goes down. However, outside of that (or other similar scenarios that require GAC usage to function), there really isn't a good fixed definition of when to use the GAC. The simple fact is that the GAC's sole purpose of existance is to ease application matinence. Things like System.Xml.Dll belong in the GAC because when you have 500 .NET apps on your machine, applying patches to every one individually would be a nightmare (even if you did patch every copy, if someone installed a new .NET app after you applied the patches, its DLLs would be out of date). Since the GAC is to aid in application matinence, you should only GAC something when it is actually going to save you time. In the situations where GAC'ing is optional, GAC'ing is only useful when the standard machine your app is going to be deployed will have a significant number of applications installed that reference your assemblies. As a result, you probably will never run into a valid reason to make use of GAC'ing unless:

1) You run into a scenario where GAC'ing is an obvious requirement.

2) You write a lot of apps for the same organization.

3) You work for a very large software company.

[1] http://www.sellsbrothers.com/spout/#Avoid_the_GAC

[2] http://www.neward.net/ted/weblog/index.jsp?date=20040330#1080641913997

Posted by Jesse Ezell with 1 comment(s)

AOL Gives Away Spammer's Porsche

This Porsche Boxer S was seized from a spammer as part of his settlement with AOL. AOL is going to be giving it away to a lucky AOL subscriber as payback.

spammer's Porsche Boxster S  [1]

So... Vashill, you have a Porsche we can raffle off to dot net weblogs users for all the spam you've been sending us?

[1] http://www.msnbc.msn.com/id/4631849/

Posted by Jesse Ezell with no comments

Street Climb

Insane

UPDATE: in case you just can't believe it, this is 100% the real deal. If you want to learn how to do this, you can find training tips here.

Posted by Jesse Ezell with 25 comment(s)

IronPython .2 and Paper

Iron Python .2 is out, and this time there is a paper to go along with it. No comparisons to Jython in this one, but still interesting stuff.
Posted by Jesse Ezell with no comments

Flex Released, but It's Not a Flash Killer

“Flex presentation server pricing starts at $12,000 for two CPUs and includes annual maintenance. Special pricing is available for ISVs and discounts are available to government and educational organizations in certain regions.” [1]

Unfortunately, although Flex is 10 times cooler than Flash, it is 30 times as expensive. This is quite unfortunate, since Flex is finally a decent Flash authoring environment, but it won't take off because someone at Macromedia decided to get greedy. Yet another example of Macromedia execs squandering great technology.

[1] http://www.macromedia.com/software/flex/buy/

 

Posted by Jesse Ezell with 7 comment(s)

Bush: Broadband for All Americans by 2007

“ALBUQUERQUE - Reaching back to revive an idea promoted by the man he beat for the White House, President Bush urged Friday that affordable high-speed Internet access be available to all Americans by 2007, saying it was essential to the nation’s economic growth.” [1]

[1] http://www.msnbc.msn.com/id/4609864/

Posted by Jesse Ezell with 3 comment(s)
More Posts Next page »