That may not be an option. Many employment contracts state that any IP developed while in the employ of the company is the property of the company. (I remember that Control Data had an expecially onerous one, basically if you developed a better tire tread design, CDC owned it, even though they didn't make tires.) Even if you quit, they still own the IP and could legally track you down and require that you sign.
Yep. Speaking as a former consultant, that's often because the last item in the specification is the delivery date. You can't tell the client it's unreasonable, so you throw together as much as you can as fast as you can (which goes a long way towards explaining VB's popularity). And since clients frequently either don't have any documentation standards or waive them for this "critical, fast-track" project, it's a real nightmare for the staff people who have to support this stuff.
OTOH, I've also been hired to augment/port projects produced this way, too. Jobs like that help balance your karma out.
But does MS Reader support highlighting or annotation? One of the reasons I keep all my old college textbooks is because of all the annotations I made in the margins.
did you know that the old cyrix chips had the same architecture as the failed pentium pro?
'Failed'? JFC, last I checked, a PPro w/1M cache was still in the several-hundred-dollar bracket. For a long time it was the only way to get a 4-CPU server w/ Intel arch. Check out this page under "Intel" and then explain to me how an ancient "failed" chip still commands the same price as the latest silicon.
No, it's not a convenient as just whipping out a phone, but it's hardly effort-prohibitive. And with the ability to phone-patch through one of the OSCAR satellites, you've got 90% of the capability of an Iridium phone anyway.
It's funny, but I recently became obsessed with fountain pens, and writing with them has really improved my handwriting. It's actually pleasant to compose a paragraph, laying down the ink in swooping lines, feeling the nib glide across the paper like the feeling of the road through the steering wheel of a fine sports car...
No way in hell I'd do that for code-writing though. Electronic signatures, sure -- writing a Perl script, no way!
I would stick with Sybase Absolutely. I spent several months last year adding Oracle support to an application designed around SQL Server and cross-vendor development is really something you should avoid if you can. Leverage your existing DBA knowledge and you can probably use one DBA for both sites. If you do go with another vendor, you'll wind up with another DBA either on salary or on retainer.
clockspeed, because that's all the clueless average computer user looks at
What *is* the average computer user? Don't corporations buy more computers than anybody? Do they base their purchasing decisions on clock speed? (I wish my company did -- I'm working on a 200MHz PPro here at the orifice!) I'm not saying they're not, just curious if indeed most system purchases are based primarily on clock speed.
IBM at the moment is doing an SAP conversion, and I can't get Netfinity servers. Not because they don't have the parts, but because they are having SAP problems and can't ship anything.
Heh, talk to Hershey. Last I heard, they were having district sales managers calling individual stores asking if they could fax a copy of their latest order, because they couldn't get it from their SAP system.
They're apparently the poster child for How NOT To Install SAP -- they implemented everything (sales, inventory, distribution, accounting -- everything!) all at once. Common wisdom has it that you implement one thing (say accounting) first, then run that in parallel with your existing system for a few months, then go on to the next part.
As far as BAAN going open source, I wouldn't count on it -- most ERP systems ship a basic code base, which is then heavily customized for the individual clients. Having a FAIB solution out there (especially a major player like BAAN) would probably cut pretty deep into the other player's pockets. Look to SAP or Oracle to snap up BAAN if things get too bad, just to prevent this sort of thing from happening.
There was a PC product that didn't do anything (don't remember the publisher). I believe there was at least one PC programs that did do something. Ram Doubler for the Mac was a very effective program (largely because of the odd way the Mac organized its memory).
When I was releasemeister for a project, we had a five-tiered system: - Major release number - Minor release number - Release revision number - Lab patch level - Field patch level
Minor release numbers changed when we added significant new features, revisions were for maintenance releases (bug fixes only), lab patches were for hot fixes developed in the lab (which hadn't gone through a complete Q/A cycle), and field patches were fixes done on-site when we couldn't duplicate the problem in the lab. (This was software that interface with phone switches, so it was often necessary to tweak it in the field so it would work with someone else's tweaks to the switch hardware.) We never had development releases, all outstanding (reported) bugs had to be addressed before a release was frozen. Any experimental development work was done on code branched off from the main path, to be integrated (or not) back when it worked. We always released the X.Y.Z.0.0 version, but I remember our most long-lived release was 2.2.0.4.2.
Check out Glass Audio or some of the other tube audio mags. They often have construction projects, and most audio tubes require 200+V power (my old Hallicrafters SX-110 has 384V on some pins!). From what I've seen, though, all those power supplies take big heavy transformers.
Slashdot Mirror
Yeah, but he did get a mall named after him, though...
The minute someone figures out how to beam an ad into my head is when I start pulling triggers
Kind of brings new meaning to the term "target audience"...
That may not be an option. Many employment contracts state that any IP developed while in the employ of the company is the property of the company. (I remember that Control Data had an expecially onerous one, basically if you developed a better tire tread design, CDC owned it, even though they didn't make tires.) Even if you quit, they still own the IP and could legally track you down and require that you sign.
Yep. Speaking as a former consultant, that's often because the last item in the specification is the delivery date. You can't tell the client it's unreasonable, so you throw together as much as you can as fast as you can (which goes a long way towards explaining VB's popularity). And since clients frequently either don't have any documentation standards or waive them for this "critical, fast-track" project, it's a real nightmare for the staff people who have to support this stuff.
OTOH, I've also been hired to augment/port projects produced this way, too. Jobs like that help balance your karma out.
I'll have a special expiration date so that it will differenciate [sic] between me and some other person who got this block before
Or, given the nature of these cards, maybe they'll only be good for one month. That way, they can re-issue every available number every month or two.
3. Any computer is more than a humanities student needs.
Proof left as an exercise for the student...
But does MS Reader support highlighting or annotation? One of the reasons I keep all my old college textbooks is because of all the annotations I made in the margins.
Would you call this a "RIMM-job"?
did you know that the old cyrix chips had the same architecture as the failed pentium pro?
'Failed'? JFC, last I checked, a PPro w/1M cache was still in the several-hundred-dollar bracket. For a long time it was the only way to get a 4-CPU server w/ Intel arch. Check out this page under "Intel" and then explain to me how an ancient "failed" chip still commands the same price as the latest silicon.
...there just isn't an alternative...
Two words: ham radio
No, it's not a convenient as just whipping out a phone, but it's hardly effort-prohibitive. And with the ability to phone-patch through one of the OSCAR satellites, you've got 90% of the capability of an Iridium phone anyway.
It's funny, but I recently became obsessed with fountain pens, and writing with them has really improved my handwriting. It's actually pleasant to compose a paragraph, laying down the ink in swooping lines, feeling the nib glide across the paper like the feeling of the road through the steering wheel of a fine sports car...
No way in hell I'd do that for code-writing though. Electronic signatures, sure -- writing a Perl script, no way!
Speaking of Fowler, his _Analysis Patterns_ book is another must-have. I also find his _UML Distilled_ pretty handy.
I would stick with Sybase
Absolutely. I spent several months last year adding Oracle support to an application designed around SQL Server and cross-vendor development is really something you should avoid if you can. Leverage your existing DBA knowledge and you can probably use one DBA for both sites. If you do go with another vendor, you'll wind up with another DBA either on salary or on retainer.
Actually, I thought it was pretty funny....
I must sue BUSH cause they made me drink.
What, a thousand pints of Lite?
clockspeed, because that's all the clueless average computer user looks at
What *is* the average computer user? Don't corporations buy more computers than anybody? Do they base their purchasing decisions on clock speed? (I wish my company did -- I'm working on a 200MHz PPro here at the orifice!) I'm not saying they're not, just curious if indeed most system purchases are based primarily on clock speed.
Well it certainly is a relief that cars don't have their models incremented by numbers!
Better not let Porsche (makers of the 356, 550, 911/930, 928, 924/931, 944/951 and 968) hear you say that...
IBM at the moment is doing an SAP conversion, and I can't get Netfinity servers. Not because they don't have the parts, but because they are having SAP problems and can't ship anything.
Heh, talk to Hershey. Last I heard, they were having district sales managers calling individual stores asking if they could fax a copy of their latest order, because they couldn't get it from their SAP system.
They're apparently the poster child for How NOT To Install SAP -- they implemented everything (sales, inventory, distribution, accounting -- everything!) all at once. Common wisdom has it that you implement one thing (say accounting) first, then run that in parallel with your existing system for a few months, then go on to the next part.
As far as BAAN going open source, I wouldn't count on it -- most ERP systems ship a basic code base, which is then heavily customized for the individual clients. Having a FAIB solution out there (especially a major player like BAAN) would probably cut pretty deep into the other player's pockets. Look to SAP or Oracle to snap up BAAN if things get too bad, just to prevent this sort of thing from happening.
There was a PC product that didn't do anything (don't remember the publisher). I believe there was at least one PC programs that did do something. Ram Doubler for the Mac was a very effective program (largely because of the odd way the Mac organized its memory).
You'll still be able to get JVMs from third parties that will run under Windows. Unless "Windows ain't done 'til Java won't run"...
They have a message passing system called SOAP ...
It's actually an open standard put out by W3C. Check it out here
Most of these programs could be ported to a new architecture with little effort.
Wake me when we reach the real world...
When I was releasemeister for a project, we had a five-tiered system:
- Major release number
- Minor release number
- Release revision number
- Lab patch level
- Field patch level
Minor release numbers changed when we added significant new features, revisions were for maintenance releases (bug fixes only), lab patches were for hot fixes developed in the lab (which hadn't gone through a complete Q/A cycle), and field patches were fixes done on-site when we couldn't duplicate the problem in the lab. (This was software that interface with phone switches, so it was often necessary to tweak it in the field so it would work with someone else's tweaks to the switch hardware.) We never had development releases, all outstanding (reported) bugs had to be addressed before a release was frozen. Any experimental development work was done on code branched off from the main path, to be integrated (or not) back when it worked. We always released the X.Y.Z.0.0 version, but I remember our most long-lived release was 2.2.0.4.2.
Would you call that "punitive" damages?
Check out Glass Audio or some of the other tube audio mags. They often have construction projects, and most audio tubes require 200+V power (my old Hallicrafters SX-110 has 384V on some pins!). From what I've seen, though, all those power supplies take big heavy transformers.