You are right. The answer is in the words which is why you should try reading them more carefully
When you walk the mile south you reach the South Pole. How do you go "west". From the South Pole every direction is north.
Why do you doubt that? This movie sounds like exactly what you described. It seems a lot like the road warrior with women instead of fuel. And I assume no "twist" ending but who knows on that count.
The first part is, choose a sprint length that will let you implement the features required. But most companies like them to be one week so they can change requirements and direction more often
Honestly I'm not sure I buy an order of magnitude.
That said if user experience is secondary (internal tools for instance) a quick and dirty web app might manage that order of magnitude but once you want some sparkle, maybe some animations, the advantages dry up quickly. It always seems like the web devs can get the basic feature implemented faster but getting it refined and polished seems to take them more time than app developers and the results are not necessarily as good.
If all you want is a device on your wrist that tells the time then you have the perfect device. This one does more. Either you want that or you don't. Lots of people say they dont but I think that is the standard anti apple knee jerk reaction. The pebble got a ton of support with less features and integration. People said the same thing about the iPhone and the iPod.
Maybe folks will prefer a different smart watch but that doesn't make this any less relevant.
It may not be a thing you want right now but comparing it to your device is as silly as saying nobody in the world needs a car because they have a reliable cheep bike. The bike will last longer. Costs a fraction of the price and never needs fuel!
For what it's worth I get where you are coming from. I like regular watches. But writing this off could prove to be pretty silly in the long run.
Its not about judgement, it is about programming. We are not asking the robot to make a judgement call we are asking who's judgement the robot should follow.
If I buy my elderly grandfather a caretaker robot and I program the robot to bring him juice but not beer (because I know he shouldn't be drinking due to meds), what should it do when he asks for a beer. I would say that the robot should obey the wishes of the owner, not the patient in this case but it should probably not prevent the patient from getting a beer themselves.
Even old stoners... maybe especially in some cases... have a really hard time believing that there are a ton of capable professionals who go to work every day and are very productive and also like to relax with a bowl and an episode of (insert your favorite stoner show here).
Your insurance is insane and in a 40 MPG car that is 250K miles worth of travel at the current cost of gas.
Not that far. Admittedly the Tesla's are nice cars but the thing is the other manufacturers are not standing still. A lot of the traditional manufactures will have their own, lower cost, electrics with similar ranges. Sure the Tesla might be a nicer car but most people cannot afford high end or even midrange luxury sedans. They need something serviceable and ideally at least somewhat nice, but not necessarily the top of the line. This could bite them if their margins are not similar to a company like BMW. If they cannot corner the market then 10 years from now they are just another luxury car manufacturer and might even struggle under their costs. They could find them selves being bought up by someone like VW. Not the worst fate but not the success that i suspect they want.
Just because they are cool does not mean they will prevail.
If I had a dime for every time I have heard that.
I develop for iOS. We use ssl for communication and the binary is cryptographically signed. And I don't actually need to understand how that works in detail to do my job. I understand it a bit because 20 years ago I took a class but if you wanted me to implement a system that does that I would be hard pressed without doing a ton of research.
The problem can easily be the way the question is asked. If you are looking for an answer like "pop" then maybe ask what tool you would use to send a file securely instead of asking a question that sounds like it is from a crypto course final. Interviews are stressful and people seize up. It happens. The number of engineers who are competent and also so good at dealing with people that they don't get flustered in an interview is quite small. Don't set them up for failure and then complain when most do.
To do what you want you have to do both. If you encrypt with your private key anyone could use your public key to decrypt it. That is signing. If you do that and then encrypt with the recipients public key then only they can decrypt and they can use your public key to confirm that you sent the message
I could give you that, but in an interview asking this question makes a dev think that you want much more in depth information which often causes people to choke. I implemented a public/private key encryption system once. In college. I couldn't tell you the first thing about how the math worked now. That was 20 years ago. I could research a turnkey solution if necessary though but if someone hit me with this kind of question in an interview I might thing they wanted me to explain how to implement a solution. Asking the right questions is critical. A good dev can be sunk by a poorly worded question and interviewers don't think nearly enough about it.
Don't undersell yourself. If you work really hard I'm sure you can get poor a lot more quickly