Don't forget to migrate to a new (set of) drives every 5 years or so. Drives get bigger and in my experience you can collapse 4-5 into 1 after that period. This assumes you end up with lots of drives. This also refreshes your copies of the data.
Sidebar - watch out for your O/S silently converting long file names to 8.3 filenames if your filepathnames are too long (esp. if you lengthen the filepathname somehow).
One point regards your professors all thinking it's a good idea. You have a statistical bias to your sample group - they will all have graduate degrees.
That being said - when I made this same decision about 20 years ago I estimated the amount of extra salary and came up with a rough number saying that getting a Masters was worth something like $100 - $200 per hour of time spent doing it.
Silly people. Why try to shoot down a zillion pieces of junk when you just have to move one large thing away from said junk. 1/2 gee acceleration (bad things happen if you go higher than one gee to those on the trailing surface) for a couple hours should do the trick.
Agreed. Forget the salary if at all possible and look for the best internship to give you good experience and/or do one in a company that looks like it will be successful. Don't pick a crappy job to get a few more dollars now.
C'mon. Get on the rant train dude. We all have an inalienable right to get as much gameplay as Blizzard can come up with for the price of a single game. Sounds like they wrote 3 games worth of entertainment. Those bastards.
Sounds like you have more time than money. If you can't afford the cost to beef up the A/C, you can use some of the techniques used in server room design. If you can, take the cold air and put it directly into your hottest (or most expensive to replace maybe) and add partitions to channel the cold air where it will do the most good. Simply mixing a stream of cold air with the warm room air is not efficient. Put the limited cooling where it does the most good, don't let the cold air mix with the hot air, try to channel the hot air away from everything. As an added thought, and exhaust fan somewhere where it is hottest might do considerable good.
Actually, it depends more on how stupid the management is. Bad processes, too many ill-considered corporate and standards constraints will have much more influence on how many "plumber IT" types you need.
One way to help normalize the ratio is by subtracting out the IT people who are in the business half. E.g., those directly adding customer value. In particular, informatics types performing research for the business should not be called part of IT (even if the company puts them into that category), but should still be called part of the denominator (business people).
Also, consider, as implied or even stated elsewhere here, to normalize to the type and perhaps size of the business.
Not necessarily. The worst problems I've seen with database logging were when the database becomes "uncleanly" unavailable and the application doesn't recognize what is happening. Ugh.
Amount of logging to do totally depends on the context. Regarding logging for regulatory/legal/sundry requirements, treat that as "user requirements" or, better, necessary features. Probably should decouple one's thinking of logging for those requirements from logging for development/improvement/troubleshooting purposes.
Afraid you're describing a very natural behavior that's unlikely to disappear. Developers (not just software) tend to work until each constraint is just met and then stop to work on the next constraint. E.g., get the load time down to the maximum acceptable time, then stop working on it.
My almost brand new (6 weeks) HP Vista laptop was semi-bricked by the automatic update. Had to revert/restore to a checkpoint. 32-bit version.//Insert rant here//
Slashdot Mirror
Don't forget to migrate to a new (set of) drives every 5 years or so. Drives get bigger and in my experience you can collapse 4-5 into 1 after that period. This assumes you end up with lots of drives. This also refreshes your copies of the data. Sidebar - watch out for your O/S silently converting long file names to 8.3 filenames if your filepathnames are too long (esp. if you lengthen the filepathname somehow).
One point regards your professors all thinking it's a good idea. You have a statistical bias to your sample group - they will all have graduate degrees. That being said - when I made this same decision about 20 years ago I estimated the amount of extra salary and came up with a rough number saying that getting a Masters was worth something like $100 - $200 per hour of time spent doing it.
Silly people. Why try to shoot down a zillion pieces of junk when you just have to move one large thing away from said junk. 1/2 gee acceleration (bad things happen if you go higher than one gee to those on the trailing surface) for a couple hours should do the trick.
Still making stuff multiple atoms thick? What's next, using bricks?
Technically it is more ethical to kill at random (or everything you can catch) then to justify some sort of self-serving end.
Agreed. Forget the salary if at all possible and look for the best internship to give you good experience and/or do one in a company that looks like it will be successful. Don't pick a crappy job to get a few more dollars now.
C'mon. Get on the rant train dude. We all have an inalienable right to get as much gameplay as Blizzard can come up with for the price of a single game. Sounds like they wrote 3 games worth of entertainment. Those bastards.
Spoilsport. Actually reading the article spoils all the fun.
'nuff said
Ugh. Too recursive.
The article in question actually says that they don't claim causality - but that it should be looked at further.
Odd. My quantum calculations seem to show that the universe has only been existance for about 8 hours.
If only there was a way to preview before submitting.
Sounds like an unreasonable estimate to me. If people were that vindicative and dishonest then IT (and similar) systems wouldn't ever keep working.
Gotta like articles that use the word 'slimy' in the first line. Pretty much ensures fair and reasonable content
Sounds like you have more time than money. If you can't afford the cost to beef up the A/C, you can use some of the techniques used in server room design. If you can, take the cold air and put it directly into your hottest (or most expensive to replace maybe) and add partitions to channel the cold air where it will do the most good. Simply mixing a stream of cold air with the warm room air is not efficient. Put the limited cooling where it does the most good, don't let the cold air mix with the hot air, try to channel the hot air away from everything. As an added thought, and exhaust fan somewhere where it is hottest might do considerable good.
The big sites *must* be interested in privacy. They're plastered with security and privacy notices.
Actually, it depends more on how stupid the management is. Bad processes, too many ill-considered corporate and standards constraints will have much more influence on how many "plumber IT" types you need.
One way to help normalize the ratio is by subtracting out the IT people who are in the business half. E.g., those directly adding customer value. In particular, informatics types performing research for the business should not be called part of IT (even if the company puts them into that category), but should still be called part of the denominator (business people). Also, consider, as implied or even stated elsewhere here, to normalize to the type and perhaps size of the business.
Not necessarily. The worst problems I've seen with database logging were when the database becomes "uncleanly" unavailable and the application doesn't recognize what is happening. Ugh.
Amount of logging to do totally depends on the context. Regarding logging for regulatory/legal/sundry requirements, treat that as "user requirements" or, better, necessary features. Probably should decouple one's thinking of logging for those requirements from logging for development/improvement/troubleshooting purposes.
Afraid you're describing a very natural behavior that's unlikely to disappear. Developers (not just software) tend to work until each constraint is just met and then stop to work on the next constraint. E.g., get the load time down to the maximum acceptable time, then stop working on it.
Money can't buy love. But it can rent it.
It's a typo. He meant "shogun". An angry Samurai stalking the premises is quite a deterrent.
My almost brand new (6 weeks) HP Vista laptop was semi-bricked by the automatic update. Had to revert/restore to a checkpoint. 32-bit version. //Insert rant here//