Comment Interesting (Score 1) 53
I totally missed this movie when it came out. Reading on it I can't believe the company ever let it be produced. Apparently, it was finacially successful, but not worth moving beyond the oneshot.
I totally missed this movie when it came out. Reading on it I can't believe the company ever let it be produced. Apparently, it was finacially successful, but not worth moving beyond the oneshot.
For a moment there I was having a hard time figuring out why you were embarrased to be from India. But then I saw the extra two letters, well don't fret this proof of your residence will only be archived on slashdot forever.
I'm actually surprised at all the negative post. Everyone of these stories is a chance for us to discuss our fav books or if people want to have a hey day making in-reference post. I've thought several of the point spins were pretty humerious. I haven't had time to post on each story, but I think the blatent day off this April was a better approach then previous years.
Most of the negitive post should just stop giving Slashdot Money by viewing the ads for the day. Instead they insist on making noise which really doesn't discourage this from occuring next year.
There is no wire.
I have to say I saw this even't going a different direction. Given our long history of mechanical engagment I thought we would be creating an army of mechonized infuntry, but based on recent accords I think all hope of a deathless war is lost. And with the new advocacy groups giving AIs more rights then humans we are left with only one choice. Children at war.
I normally hire two classes of people. Rank and file and Leads. My leads typically have to be experts in a given field as they will be making decisions and driving future direction in the project, but my rank and file I just want basic aptitude and interest. I find I get more out of learning about a candidate when ask where he falls on the EMACS vs VI war then anything else. The average candidate is so nervous at an interview they over analyses everything and just plain forget basic information they know. I've seen basic graphics guys forget what a corss-product was then perfectly explain how to calculate a normal map given an arbitrary height-map. These types of mistakes are typically owned up to nervousness.
Now for team leads you need to be very specific on your requirements and they better be able to present a portfolio of prior work. I let the candidate lead on descriptions of what they have done in the past and then ask detailed questions as they come up on more specific implementations. I need to know that the candidate is not only competent, but can relate his work and needs to people who will be under him. If he can communicate about specific solutions he has worked on in the past then he will be unable to clarify system requirements to subordinates. One in every three candidates will try not to talk about specifics due to trade secrets. I normally take this as an attempt to skirt a lack of experience so I then ask hypothetical about a similar system I can relate there work to. I'm satisfied if the response is relevant to my scenario or if the candidate can explain in detail why its different then his previous work, but if he doesn't answer the question then we know he has exaggerated on his resume.
Others, might have different methods, but I find you really don't learn about someones aptitude until they work for you. Its almost impossible to determine if people are professional, punctual, or motivated from an interview since almost every answer is rehearsed and a lye to try and get employment. So, I try to make reasonable evaluations on qualifications and pick people that will fit well with the team. If the guy did lie we will find out soon enough and he will be interviewing again soon after.
Android and iOS do the same thing. Natural Language Processing is difficult so its done in the cloud most of the time. I don't care if the recordings go to 2nd Party or 3rd Party having cloud based LNP on any device is a security risk. I would expect this disclaimer to come on every smart device that requires a net connection to function.
It doesn't mater what OS I play it on, I actively refused to buy a license for any game that doesn't at least run on OSX. Once most games have an OSX/OpenGL port its only a mater of time before Linux becomes a easier port/support option.
I don't know if I'm the only one and to be honest the way I use OS X doesn't make this such a big deal, but at 5K unless they do automatic font scaling. I'm going to need to be able to divide my monitor up in to virtual monitors. That way I can resize zones where if I click the magnify/maximize button it doesn't waste the entire real estate of my monitor. I really enjoy the snap feature in windows 7 enough I use a program called sizeup on OSX to emulate it, but once I start buying 27 and 30" monitors I really would like my desktop tp let me arbitrary subdivide it in to multiple monitors for behavioral reasons.
Anyone have an app for that?
I would cancel my relationship with mastercard. It might also help to never shop at newegg again and to convince others as well. My highschool job was working retail. I was taught something like one unhappy customer was 200 grand in business.
That story is pretty convincing you. I would make it my goal to make people aware of it.
But blue is brighter. It should be important for you to know your devices are on!
Seriously, I have a netgear router that has 1 blue led for every wifi antenna and they dance based on which one just picked up a packet. It took me two years of having it blocked with tape and paper towels before I discovered the thing had a feature to turn them off.
He does accurately describe the majority of my co-workers. I blame broadband myself.
I'm no so sure its a horrible question. I would as an the receiver be very speculative of the presenter, but as a presenter I would be looking for the type of brush off response I get not an actual answer. Does the candidate reference a particular book or does he say he would go to stack exchange. I normally hate programming questions on interviews because its not how we work. We engineer so we draw things out write out UML or some type of logic flow then get to coding.
I personally build little modules then add on higher functional work loads until I have a finished product, asking a user to drop down a random maze algorithm is naive and doesn't really do much, but ask if the candidate happens to have that brain teaser memorized. Instead I like to ask questions that give me an idea of how a user approaches problems that can't be solved immediately and I think asking questions you don't expect an answer to can sometimes help.
This is really a mater of modern convention. Webster's has a good ask the editor video entry on the history of the two forms and how often they changed. Your likely right that most people are ignorantly using the wrong form, but like many things in our language its silly to get upset about it with out some sense of etymology.
"May your future be limited only by your dreams." -- Christa McAuliffe