Chances are that 'American' english will incorporate more and more words from Spanish in the future, due to the close proximity of many Latin American neighbors and the influx of many Spanish speaking people into the U.S.
An agreement would give your employer the right to the work you do outside of normal employment, and which is not directly related to the business of your employer may not be legal in your state. i.e. even if you did sign the contract, that portion of the contract may not be binding. Contacting a lawyer is probably the best thing to do.
I've also seen a few incompetant cs people in my day. Most recently was the architect that decided the best way to transfer data from a database to a message (for xmitting to another location) was to read the entire set of selected records into memory, (into a XML - DOM tree), where each item of data necessitated a memory allocation. Then to access the items in this structure, you supplied it a text string ( xml-path-string) whereby at each level in the tree it had to search through a long list for the proper item.
Needless to say this code ran 5 times slower than the competitor's, couldn't handle large data sets, and the project fell flat on its face.
A computer scientist doesn't necessarily know anything about computers.
You can say that again. I've met more than a few of these during my programming career. They can screw up even a simple project so that it ends in failure.
I think it's because of HP's announcement that IntEl thought it necessary to announce the 64 bit Pentium. I think I read somewhere that IBM and a couple of other significant companies are planning to use the Opteron in their new products as well.
Linux will certainly benefit from the move to 64 bit processors. From what I've read the Microsoft 64 bit os is still a long ways off (2006).
I think in the long run that a new instruction set, as was given the Itanium, will be the road to higer performance.
Good post. The paper on the NET -vs- J2EE projects I thought was quite well done. As you mention, there are a lot of developers out there who will realize that had the comparison been done with a Linux-J2EE solution that was completely open source, the cost would be less for the Linux-J2EE solution.
I believe this article compared the Microsoft.NET environment with a Linux environment that used BEA Web Server and Oracle. The cost of Oracle, and the BEA Web Server (and associated training) are what drove up the cost of development of the Linux based systems.
If a company were really looking to reduce costs, however, there are open source equivalents to these two products (JBoss & MySql) that certainly would reduce the costs.
Looking at this white paper from a managerial standpoint, I believe this paper presented a fair comparison. Certainly there are situations where a Microsoft solution makes sense, although I believe these will be significantly fewer in several years.
Slashdot Mirror
No, you should have said that you're ten times better at drinking a glass of coke than your friend.
Chances are that 'American' english will incorporate more and more words from Spanish in the future, due to the close proximity of many Latin American neighbors and the influx of many Spanish speaking people into the U.S.
A neural net working in conjunction with a fishing net. Two nets working towards the same goal.
I thought the same thing when I read that post.
From what I know, it IS possible to distinguish hemp from marijuana by flying over the countryside, with specialized instruments.
"I'ld like to show you this POS from SCO.
What would it take to get you to buy this POS?"
An agreement would give your employer the right to the work you do outside of normal employment, and which is not directly related to the business of your employer may not be legal in your state. i.e. even if you did sign the contract, that portion of the contract may not be binding. Contacting a lawyer is probably the best thing to do.
I've also seen a few incompetant cs people in my day. Most recently was the architect that decided the best way to transfer data from a database to a message (for xmitting to another location) was to read the entire set of selected records into memory, (into a XML - DOM tree), where each item of data necessitated a memory allocation. Then to access the items in this structure, you supplied it a text string ( xml-path-string) whereby at each level in the tree it had to search through a long list for the proper item. Needless to say this code ran 5 times slower than the competitor's, couldn't handle large data sets, and the project fell flat on its face.
A computer scientist doesn't necessarily know anything about computers.
You can say that again. I've met more than a few of these during my programming career. They can screw up even a simple project so that it ends in failure.
I think it's because of HP's announcement that IntEl thought it necessary to announce the 64 bit Pentium. I think I read somewhere that IBM and a couple of other significant companies are planning to use the Opteron in their new products as well.
Linux will certainly benefit from the move to 64 bit processors. From what I've read the Microsoft 64 bit os is still a long ways off (2006).
I think in the long run that a new instruction set, as was given the Itanium, will be the road to higer performance.
Good post. The paper on the NET -vs- J2EE projects I thought was quite well done. As you mention, there are a lot of developers out there who will realize that had the comparison been done with a Linux-J2EE solution that was completely open source, the cost would be less for the Linux-J2EE solution.
I believe this article compared the Microsoft .NET environment with a Linux environment that used BEA Web Server and Oracle. The cost of Oracle, and the BEA Web Server (and associated training) are what drove up the cost of development of the Linux based systems.
If a company were really looking to reduce costs, however, there are open source equivalents to these two products (JBoss & MySql) that certainly would reduce the costs.
Looking at this white paper from a managerial standpoint, I believe this paper presented a fair comparison. Certainly there are situations where a Microsoft solution makes sense, although I believe these will be significantly fewer in several years.