The solution is regularly teaching business ethics to students. Perhaps even make it mandatory to earn a degree. Certainly mandatory for a graduate degree.
The suggestion that a mandatory degree and ethics classes will solve the problem is laughable. Many examples of why this is so exist: Citigroup, Enron, Worldcom... to name a few. Do they teach business ethics in MBA or CPA programs? Of course they do. Did it help? No.
I wouldn't be so condescending about the suggestion...
Radia Perlman has accomplished more for modern networking and the internet that you probably will in your lifetime. She is more than just a "sun employee." She is inteventer of the Spanning Tree Protocol amoung other things http://en.wikipedia.org/wiki/Spanning_tree_protoco l.
Maybe check out her book, Interconnections, on Amazon to get a feel for the type of work she does.
I've worked help desk and would argue that t-shirts and jeans are an appropriate attire for the job because your interaction with the client is via telephone. Those that disagree would do better to be more concerned with how an individuals professionalism shows through over the phone as opposed as to how they are dressed. This said, whenever I meet with a customer in person I always wear a suit. I think that this lady is missing the point completely.
chip is wirelessly connected to the backup system and keeps it constantly and updated. Would that be a valid backup?
Are you Joking?! In my experience, it is difficult enough to make sure that computer backups happen regularly never mind the contents of a human brain. Hey, even the thought of my computer backups working on a regular basis and without incident is the stuff of science fiction nevermind this nonsense!!!
Re:Microwaves are potentially dangerous---no shit.
on
A Foundry in Every Kitchen
·
· Score: 3, Insightful
no, i've taken apart tv's... television sets are high voltage, low current devices. if you zap yourself on the tube, it'll hurt like hell, but won't kill you. microwaves are a completely different animal.. even if i did own the tool required to properly discharge a capacitor, what makes you think that there's only one cap in there that can kill you? unless you have the schematic/servic manual (which are typically only available to authorized service centers), you don't know for sure
anyways, even if this fear does stem from ignorance (which it does), just because i've been trained in a related area does not mean i even repair electronics for a living (i don't) or even have the desire to learn how to service a microwave (i have better things to do with my time).
anyways, i was just letting the less informed know about this; but since you're so gung-ho about these things, make sure you wrap your fucking balls in tin-foil, because these things can give off a dangerous amount of radiation also. but you already knew that, didn't you.
I feel obliged to say something, before some 13 or 14 year-old kills themselves:
microwaves are high voltage, high current devices. they can kill you EVEN IF THE POWER IS OFF AND THE DEVICE IS UNPLUGGED (ex: by discharging of a large capacitor). Unless you really know what you are doing, don't open one up. i've been trained in servicing electronics, and even i wouln't go near one of these things.
here's an example from an expert. Dennis Ritchie wrote the following code in the Sixth Edition of UNIX back in 1975:
/* * Switch to stack of the new process and set up * his segmentation registers. */ retu(rp->p_addr); sureg(); /* * If the new process paused because it was * swapped out, set the stack level to the last call * to savu(u_ssav). This means that the return * which is executed immediately after the call to aretu * actually returns from the last routine which did * the savu. * * You are not expected to understand this. <------------ *ahem* */ if(rp->p_flag&SSWAP) { rp->p_flag =& ~SSWAP; aretu(u.u_ssav); } /* * The value returned here has many subtle implications. * See the newproc comments. */ return(1);
but in all seriousness, i have found that the two most useful tips when commenting code are as follows:
write comments for code in blocks, describing the function of the code to follow (ex: right before a nasty looking "for" loop, explain what it does)
use variable names that communicate meaning; the code will end up commenting itself this way
Look at my history. Can confirm "adult supervision."
More than you think. I work in Radiology and am aware of public IP Addresses for Ultrasounds and other modalities.
The solution is regularly teaching business ethics to students. Perhaps even make it mandatory to earn a degree. Certainly mandatory for a graduate degree.
The suggestion that a mandatory degree and ethics classes will solve the problem is laughable. Many examples of why this is so exist: Citigroup, Enron, Worldcom... to name a few. Do they teach business ethics in MBA or CPA programs? Of course they do. Did it help? No.
I wouldn't be so condescending about the suggestion... Radia Perlman has accomplished more for modern networking and the internet that you probably will in your lifetime. She is more than just a "sun employee." She is inteventer of the Spanning Tree Protocol amoung other things http://en.wikipedia.org/wiki/Spanning_tree_protoco l.
Maybe check out her book, Interconnections, on Amazon to get a feel for the type of work she does.
I've worked help desk and would argue that t-shirts and jeans are an appropriate attire for the job because your interaction with the client is via telephone.
Those that disagree would do better to be more concerned with how an individuals professionalism shows through over the phone as opposed as to how they are dressed. This said, whenever I meet with a customer in person I always wear a suit.
I think that this lady is missing the point completely.
chip is wirelessly connected to the backup system and keeps it constantly and updated. Would that be a valid backup?
Are you Joking?! In my experience, it is difficult enough to make sure that computer backups happen regularly never mind the contents of a human brain. Hey, even the thought of my computer backups working on a regular basis and without incident is the stuff of science fiction nevermind this nonsense!!!
guess not. just lucky, then ;-)
no, i've taken apart tv's... television sets are high voltage, low current devices. if you zap yourself on the tube, it'll hurt like hell, but won't kill you. microwaves are a completely different animal.. even if i did own the tool required to properly discharge a capacitor, what makes you think that there's only one cap in there that can kill you? unless you have the schematic/servic manual (which are typically only available to authorized service centers), you don't know for sure
anyways, even if this fear does stem from ignorance (which it does), just because i've been trained in a related area does not mean i even repair electronics for a living (i don't) or even have the desire to learn how to service a microwave (i have better things to do with my time).
anyways, i was just letting the less informed know about this; but since you're so gung-ho about these things, make sure you wrap your fucking balls in tin-foil, because these things can give off a dangerous amount of radiation also. but you already knew that, didn't you.
microwaves are high voltage, high current devices. they can kill you EVEN IF THE POWER IS OFF AND THE DEVICE IS UNPLUGGED (ex: by discharging of a large capacitor). Unless you really know what you are doing, don't open one up. i've been trained in servicing electronics, and even i wouln't go near one of these things.
see: Notes on the Troubleshooting and Repair of Microwave Ovens for more information.
here's an example from an expert. Dennis Ritchie wrote the following code in the Sixth Edition of UNIX back in 1975:
but in all seriousness, i have found that the two most useful tips when commenting code are as follows: