Forgot your password?

Comment: 2 simple rules (Score 1) 281

by simishag (#47388883) Attached to: Ask Slashdot: How Often Should You Change Jobs?

I have 2 simple rules:

1) If the job is really terrible -- crazy boss, lousy environment, not enough funding -- it should be obvious within 30 days or so. At most companies this is a probationary period anyway. I've quit a couple of jobs quickly for these reasons, and I've found that HR (if not the boss) is generally okay with this. Act professionally, of course, give notice and all that, but It's better to cut ties early if you feel that you and the employer are not a good match.

2) Assuming I get past 30 days and still like it, I've always tried to make it to 2 years before trading up. I've found that after year 1, I'll get a bonus or a bump in salary almost automatically. Year 2 is when the employer starts to look for something more out of me, and also when I'll get a better idea of possible career paths within the company.

My experience is that job hopping is not a big deal as long as you have good reasons, and as long as it's not TOO often. Good reasons include relocation, a substantial (I'd say 25%+) bump in pay, or changing jobs to do what you really want to do. No one will care that you only worked 3 months at The Gap before finding a Web developer job.

Comment: same thing (Score 1) 188

by simishag (#46790051) Attached to: Heartbleed Sparks 'Responsible' Disclosure Debate

I'd say you follow the same process: inform them, wait 1/3/7 days or whatever, then go public. If you suspect the exploit is deliberate, informing the manufacturer isn't telling them anything they didn't already know. Or, maybe it IS telling them, since in the case of open source, the exploit could have been introduced surreptitiously by a developer who's long gone, and the current developers have no idea of the exploit's existence.

Caveat: if you suspect revealing the bug will cause blowback to you. If you think the NSA/FBI/CIA will come after you for threatening to reveal it, I'd say just go public immediately, and include major press orgs so they can't just silence you.

Comment: Re:Suppression of Air Defenses is NOT humanitarian (Score 1) 203

by simishag (#44771725) Attached to: Making a Case For Cyberwar Against Syria

Minor quibble with this. SEAD is a combat tactic which assumes you're already at war and suppressing defenses to advance a specific mission. A no-fly zone is a strategic patrol. It tells the enemy that you have overwhelming air superiority within the theater, and it assumes the enemy isn't willing to risk testing the no-fly zone. In the past no-fly zones have been more or less declared and imposed, and actually SEAD missions were unnecessary.

To be sure, actually enforcing a no-fly zone could require SEAD missions, in which case, it's not so no-fly. But yeah, it's still a dumb idea here, and it could provoke a wider war.

Comment: Suppression of Air Defenses is NOT humanitarian (Score 1) 203

by simishag (#44770193) Attached to: Making a Case For Cyberwar Against Syria

Suppression of Enemy Air Defense (SEAD aka Wild Weasel) is a combat tactic intended to reduce friendly losses and improve the effectiveness of air strikes. That is, to kill more of them and less of us. How in hell does someone consider that "humanitarian"?

This is one of the most Orwellian pieces of doublespeak I've read all year.

Comment: Re:Um, no (Score 1) 211

by simishag (#44752969) Attached to: Writing Documentation: Teach, Don't Tell

No. Experts in their field shouldn't need to be taught how to understand your system; that's part of being an expert ( or indeed, even a professional).

I completely agree but how are we even calling this "expert" or "professional"? Do I need to educate someone, a "programmer" let's say, about the fundamentals of Java? About electronics? About physics? How to type? How to use the toilet?

Maybe that's over the top, but at some point, if someone claims they can do X, we assume a basic level of skill. To use a car analogy: cars basically all work the same way. The car dealer doesn't make you take a test before you buy it and drive it home. They have to make sure you have a valid license, of course, but licensure is not their problem, and licensure by the state assumes that the basics of driving are the same across different models of cars.

Comment: Re:Most disturbing; buffered charges (Score 1) 192

by simishag (#43846331) Attached to: Jeremy Hammond of LulzSec Pleads Guilty To Stratfor Attack
You address it through the statute of limitations and the 6th Amendment. Only the most heinous crimes have no limitations, and for misdemeanors and non-violent felonies, the prosecution must file charges within 2-7 years (depending on the state and crime). Once charges are filed, the right to a speedy trial attaches. Also, it's not really practical for a prosecutor to run serial trials. They basically have to go to all the same trouble, but it ends up costing more time and money since it's not done all at once, and it will piss off most judges royally. Prosecutors are also usually elected, so they don't often get away with this tactic. The only time it's really useful is if you have a defendant who you can charge with, say, burglary, while gathering evidence toward a murder charge. This is more to prevent the defendant from fleeing, but they still might get bail on the lesser charge. Lots of episodes of "Law & Order" use this as a plot device.

Comment: Re:it always baffles me (Score 1) 113

by simishag (#42952477) Attached to: Utilities Racing To Secure Electric Grid
I can appreciate your sentiment, but I think it's wishful thinking. We can certainly argue that these devices SHOULD not be connected to the Internet, but the simple fact is that a great deal of them ARE connected, and many that are not "intended" to be connected will end up connected, and those systems need to be designed with that possibility in mind. They are currently designed with no more security than my pull-start lawn mower.

Comment: Re:Bob's value (Score 1) 379

by simishag (#41915609) Attached to: Ask Slashdot: How Would You Convince Someone To Give Up an Old System?

All good ideas. I think a lot of people are actually open to change as long as they feel their skill and experience is being valued. Suggest that it would be good to simplify and modernise the process and find out what ideas Bob has and the challenges he sees in implementing any changes.

This is definitely true but I would also add "offer to help with the changes" (or find someone who is capable of helping). Outsiders may have good ideas about how to fix things, but anyone can be a critic. That can be annoying to the original maintainer who has to do the work, regardless of how much it improves the system.

Comment: Re:What. What?! (Score 2) 220

by simishag (#41104871) Attached to: CPUs Do Affect Gaming Performance, After All

GPUs only tend to allow you to offload the strait-shot parallelized stuff - graphic blits, audio, textures & lighting - but the core of the game logic is still tied to the CPU. Even if you aren't straining the limits of the CPU in the final implementation, programmers are still limited by the capacity of them.

Your theory is basically valid, but the practical reality and the empirical evidence of the last, I dunno, 20 years or so, is that the graphics processing takes a significant amount of computing power. There's a reason that virtually every computer and every game console has a dedicated GPU. For that matter, a dedicated sound processing chip. It's all offloaded and the APIs have improved to the point that it doesn't seem like much work, but those specialized chips are burning an awful lot of power.

For a wide variety of games, the game logic just isn't that complicated, or rather, it doesn't require as much computing horsepower as the rendering. Sports games and FPS are the most obvious but I'm sure there's others. The most CPU intensive game I can think of is Civilization 4. I'm sure it's been surpassed, and yeah the AI still sucks, but late in games you can really tell that the CPU is chugging away.

The truth, of course, is that something will ALWAYS be a bottleneck. The argument seems to be: is it the CPU or GPU?

Comment: Re:i hope never (Score 1) 381

by simishag (#40993457) Attached to: Could Flying Cars Actually Be On Their Way?
This is sensationalism. Even small planes have a boatload of "distractions" to observe: radio, gauges, displays, maps, etc. Adding a cell phone into the mix isn't exactly overloading the pilot, unless he's doing something REALLY stupid like texting on final. He might have been USING a cell phone, but he was probably just overconfident as to his abilities as a pilot. There's also a major difference between talking on the phone in your car and in a plane. In auto traffic, you have to manage the car continuously, keep an eye out for traffic, deal with traffic lights, and on and on. Piloting certainly requires a lot of skill but you aren't twitching the stick and throttle and braking every 2 seconds, and since most planes have autopilot, it can be pretty relaxed.. There's plenty of time en route to send a text or make a call, and to do so safely.

Anyone can do any amount of work provided it isn't the work he is supposed to be doing at the moment. -- Robert Benchley