You can always cross out/alter and initial any clauses in your contract that you don't agree with. In some cases, the company doesn't even review the signed contract to notice that you've changed the terms.
I've hired a lawyer in somce cases to review a contract (about $250, IIRC), but many times I don't if the risk is fairly small. Personally, I'd rather do work for a company with a good reputation that pays me in a timely manor than for a lousy company under a good contract.
Seems pretty straight forward to me. There are three types of code involved here:
1. IBM's and Active States GPL'd code. Your company has no right to ditribute it without follwing the GPL (unless they get a different license from the owner).
2. Your original code from before you were hired. You have a verbal contract (legally binding, but hard to enforce) with them that it belongs to you. They should be required to get a license from you to distribute this, but practically speaking, you will have a hard time doing this.
3. Your code written while you were employed by them - probably they own it (depends on your employment contract and exactly what they agreed about the code originally).
I, too, will vouch for Speakeasy. I have had few problems in 4 years of service, and even the couple of times I did call them, their tech support was available, friendly, and helpful.
When we got a console for our kids, we picked GameCube over XBox for because GameCube seemed to have more kid-friendly games, so there is some truth in what he says.
On the other hand, being percived as more mature can't hurt XBox sales in the long run as those kids get older.
So the Russians want to get funding for their space agency by sending some goob on a joy ride. How is this different from what NASA did in sending a senator into space? Oh, except that in Glenn's case, the US public paid the bill.
I guess I disagree with the general trend of comments here. In my experience, it is very easy to introduce new bugs when maintaining code you don't really understand, so making it understandable is often a good first step. You will also find that you end up with less (often much less) code than you started with, so there is less code to maintain, and fewer bugs (assuming constant rate of bugs per line of code). I would suggest:
If a module has had an unusually large number of patches to fix bugs, its time to rewrite it. If you keep metrics on bug fixes, this is easy to determine.
Find some way of automatically testing the code to ensure it does what is supposed to. Run these tests on the old module before you start to make sure they are right.
Clean up the code, a bit at a time. Chek your work by running your automated tests.
Use your own judgement about telling management. Every manager is different. Most will (resaonably) fear that you will introduce more problems into the code by rewriting it. You must yourself be convinced that this is not the case before you can convince management.
I assume he expects people to only buy books that have been reviewed. There are tons of books published, and not enough time to review all of them. If a book is worth buying, then a review helps the reader to determine if he personally would benefit from getting it. If a book is not worth buying, it doesn't really help a potential buyer to have a review. I don't need reasons not to buy a book.
Which, of course, leaves us wondering why this review was posted at all...
Pick an irrelevant candidate (any third party, write in, whatever)
If you are only voting to determine who wins, then a vote for a third party that is unlikely to win is wasted. If you are voting to send a message, then voting for a third party that represents your view carries that message much better than voting someone who is the slightly better of two bad apples.
Here in Virginia, unless something amazing happens between now and election day, George W. is going to get all the state's electoral college votes, regardless of how I vote. A vote for (say), Nader sends a much clearer message about what I don't like about Bush than a vote for Gore. An unexpectedly strong turnout for the Green Party is bigger news than the same extra turnout for the Democrats (or at least it should be, but unfortunately third parties get screwed by the broadcasters, but that's a different rant).
Re:Coding isn't everything (gasp!)
on
Too Old To Code?
·
· Score: 2
Become an independent consultant. Making $130/year is not too hard if you've got good skills and live in the right part of the country. Although most consultants I know are workaholics, you don't have to be, so you can take as much vacation as you can afford. And you get to do plenty of coding.
While the Cold Fusion documentation may be adequate for explaining what the tags do, it does a pretty poor job of telling you how to best use the product. A particularly serious shortcoming is lack of explanation as to how to structure an application. The result, as noted by another poster, is Cold Fusion's well-earned reputation for being hard to maintain.
Any reduction in MS market share helps Linux, even if it goes to Apple, Palm, etc
Because porting to additional platforms is much easier after porting to the second, the essential choice for vendors will be between supporting just MicroSoft or supporting multiple platforms. Thus, any reduction in MicroSoft's market share will make it more likely that vendors will support Linux. Linux wins when more people buy iMacs. All users wins when there is greater choice in the OS market.
Not only that, but a greater number of economically viable platforms will drive more companies to open source. Why? Because most companies can't afford to produce and support binary distributions for a wide range of platforms. While they could contract out such support, moving to Open Source will allow user of even obscure platforms to become customers.
Slashdot Mirror
You can always cross out/alter and initial any clauses in your contract that you don't agree with. In some cases, the company doesn't even review the signed contract to notice that you've changed the terms.
I've hired a lawyer in somce cases to review a contract (about $250, IIRC), but many times I don't if the risk is fairly small. Personally, I'd rather do work for a company with a good reputation that pays me in a timely manor than for a lousy company under a good contract.
Seems pretty straight forward to me. There are three types of code involved here:
1. IBM's and Active States GPL'd code. Your company has no right to ditribute it without follwing the GPL (unless they get a different license from the owner).
2. Your original code from before you were hired. You have a verbal contract (legally binding, but hard to enforce) with them that it belongs to you. They should be required to get a license from you to distribute this, but practically speaking, you will have a hard time doing this.
3. Your code written while you were employed by them - probably they own it (depends on your employment contract and exactly what they agreed about the code originally).
I, too, will vouch for Speakeasy. I have had few problems in 4 years of service, and even the couple of times I did call them, their tech support was available, friendly, and helpful.
When we got a console for our kids, we picked GameCube over XBox for because GameCube seemed to have more kid-friendly games, so there is some truth in what he says.
On the other hand, being percived as more mature can't hurt XBox sales in the long run as those kids get older.
I expect we'll next see Spammers using the DMCA to get their copyrighted SPAM removed from the database...
So the Russians want to get funding for their space agency by sending some goob on a joy ride. How is this different from what NASA did in sending a senator into space? Oh, except that in Glenn's case, the US public paid the bill.
And there is at least one species of Penguin that is found near the equator.
Which, of course, leaves us wondering why this review was posted at all...
If you are only voting to determine who wins, then a vote for a third party that is unlikely to win is wasted. If you are voting to send a message, then voting for a third party that represents your view carries that message much better than voting someone who is the slightly better of two bad apples.
Here in Virginia, unless something amazing happens between now and election day, George W. is going to get all the state's electoral college votes, regardless of how I vote. A vote for (say), Nader sends a much clearer message about what I don't like about Bush than a vote for Gore. An unexpectedly strong turnout for the Green Party is bigger news than the same extra turnout for the Democrats (or at least it should be, but unfortunately third parties get screwed by the broadcasters, but that's a different rant).
Become an independent consultant. Making $130/year is not too hard if you've got good skills and live in the right part of the country. Although most consultants I know are workaholics, you don't have to be, so you can take as much vacation as you can afford. And you get to do plenty of coding.
While the Cold Fusion documentation may be adequate for explaining what the tags do, it does a pretty poor job of telling you how to best use the product. A particularly serious shortcoming is lack of explanation as to how to structure an application. The result, as noted by another poster, is Cold Fusion's well-earned reputation for being hard to maintain.
What we should do is all cut and paste the same data into our double-click cookie, so we all look like the same person to them.
Because porting to additional platforms is much easier after porting to the second, the essential choice for vendors will be between supporting just MicroSoft or supporting multiple platforms. Thus, any reduction in MicroSoft's market share will make it more likely that vendors will support Linux. Linux wins when more people buy iMacs. All users wins when there is greater choice in the OS market.
Not only that, but a greater number of economically viable platforms will drive more companies to open source. Why? Because most companies can't afford to produce and support binary distributions for a wide range of platforms. While they could contract out such support, moving to Open Source will allow user of even obscure platforms to become customers.