Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Re:Eletronic fingerprint? (Score 4, Informative) 143

"return the second laptop because the device was capable of accessing Allegro's IT network"

It sounds like they depend on the MAC address for access security, and not-a-one-of-them has ever heard of MAC spoofing. (Or a Pingles can for extending WiFi range to off of company property.)

Comment Re:All too true (Score 5, Insightful) 266

I came here to say this, mostly.

I *know* that there are plenty of places in our software that I could spend an hour or two, and rewrite an algorithm to run in 1/5th the time. And I don't care at all, because the cost is too low to measure, and usually, performance bottlenecks are elsewhere.

Who really cares if I can get a loop to run in 800ns instead of 1500ns, when the real bottleneck is a complex SQL query 11 lines up that joins 11 tables together and takes 3 full seconds to run?

Comment Re:Mission Critical? (Score 1) 89

No, things haven't changed much. The DS and 3DS also have very easy methods of piracy, and that didn't stop either of them from absolutely dominating the handheld market.

I'm pretty sure GP's "piracy dooms systems to obscurity" meme is borne of the oversimplified copypasta about the failure of the Dreamcast.

Comment Not very effective, anyway (Score 2, Interesting) 1001

I'm an employer. I've interviewed nearly everybody we employ at my company. And treating a hiring interview like a rote memory exam is a terrible way to qualify a potential developer hire!

What do programmers actually do? Try testing that!

We do "whiteboard style" for part of our interviews, but only to cover basic comprehension of algorithms. More than anything, we look for basic familiarity with logic structure, and the demonstrated ability to solve problems. Our coding section of our interview process is in the subject's language of choice, including pseudo code, and is "open book" - we want to see what happens when the dev runs into a problem they don't already know! (Critical test: can they come up with a working, supportable algorithm for a problem they don't yet already know an answer for?)

After 20 years of programming experience, I STILL routinely look up the order of arguments for function calls via Google. Who cares to remember when Google has the answer in 0.10 seconds?

Test what the devs will actually DO in an anticipated normal work day and make your decisions based on that.

Slashdot Top Deals

Nothing makes a person more productive than the last minute.

Working...