Shielding is fine, mostly incidental anyway, and isn't an offense. Transmitting on a licensed band when you're not the licensee, on the other hand, is very illegal. Jammers do not "block" RF; they are transmitters. Unquestionably illegal (the jammer part doesn't even matter, really) unless you're the licensee of whatever it's transmitting on.
You mean CAT scan?
An MRI is a really big superconducting magnet. If you swallowed some of those balls, had them get stuck in your intestines, then went for an MRI... I can't imagine that would be a very pleasant experience, having several balls forcibly pulled through your soft squishy organs.
That was the joke, i.e. "eat them and go die".
I'd say "what's to teach?" They have the source code, and presuming it's documented or well commented, well then that's that. There aren't any secrets. Whether or not the replacement is up to the task at hand is a totally different issue and I'd say is not the poster's problem in the least. If the new kid is worth anything and can actually program then he can easily learn all the "secrets" by reading the code and learning from it. Help familiarize him with the unique points of the particular project? Sure. Teach him how to program? Nope.
All that ended when we went to the Interwbz for phone. Now I have no idea how phone calls can be made unspoofable.
Implement RSA on telephones and have key-signing parties like we did in the good old days. Done.
But the tubes are supposed to be anonymous.
Eh, don't put anything too important that you can't live without on systems outside of your control.
Maybe they tried rolling back to an older version of the cert first.
(Yes, that was sarcasm.)
Throw "on the internet" or "on a computer" in there and you've got yourself a patent.
U-verse over 3k (possibly shorter if it's old copper) wire feet is generally a bad idea no matter what they tell you. My U-verse has worked flawlessly, but I'm only 1.2k wire feet away. There's only so much you can do with old copper pairs.
Unless he's making your own job a lot harder or you're his boss (or project manager), it's not your place. Your "help" will likely only piss him off more and more and cause problems in the office. Not only will it in *no way* benefit you, but it will very likely *hurt* you and your career--since your manager will come to view you as a source of headaches, your co-worker(s) will view you as a pretentious little prick, and (contrary to popular belief) the guy who helps produce better overall product is almost never rewarded for it anyway. About the fastest way for anyone to piss off their co-workers and bosses is to walk around with a "I'm the best coder here" attitude all day, whether it's true or not. Don't do it.
So, STFU and let management deal with him (or not). That's what they're paid for, not you. Don't offer *any* unsolicited criticism, and even if solicited, offer only a few minor criticisms at a time.
In short: Lighten up, Francis.
If I could I'd mod this straight to the top.
Ugh, no. It's crap compared to threading that's been around since usenet days. Why we're going backwards these days is anyone's guess.
If I have to use speakerphone my Polycom is a world better than any cell phone. Headset options are infinitely better than Bluetooth options. Back in the day I preferred a wired headset if I was going to be on the phone all day; now I have a wireless Plantronics since I'm not on the phone as much. The desk phones always work and work well. I notice whenever I'm talking to someone that has VOIP or is on their cell: the worst is when there's a one second lag on the other side's VOIP handling, it really screws up the flow of conversation when both ends end up talking over each other. I guess if you're both on VOIP and have the same amount of voice lag it probably balances out, but it's really pretty much crap when one side is trying to do something "modern" that sucks.
Yes, there's ways to set things up properly, but by and large all these alternate methods end up falling short more often than not. My office phones are VOIP Poloycoms and they work great, but they're on the LAN where every detail can be configured properly.
Plus my work phone is for when I'm working. Call it for work. If I really want to or need to be reached for work things on my cell the desk phone can be set to forward calls.
Although modded as funny, I had to use the hammer on a stuck hinge pin (spring type) on a rack door last week to remove the door.
If the Teamsters think your union is doing something stupid, it just might be.
I have RealCalc on my phone, but at the end of the day I still reach for my TI-86 (home) or 92 (work) on my desk. Probably because it's quicker: no need to wake it, unlock the screen, navigate to the app, launch the app, then constantly repeat the first two steps when it invariably goes to sleep before I'm really done.
Whoops, I meant TI-89 at work, not 92.
I have RealCalc on my phone, but at the end of the day I still reach for my TI-86 (home) or 92 (work) on my desk. Probably because it's quicker: no need to wake it, unlock the screen, navigate to the app, launch the app, then constantly repeat the first two steps when it invariably goes to sleep before I'm really done.
"The four building blocks of the universe are fire, water, gravel and vinyl." -- Dave Barry
