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).
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.
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.
The thing is these discourage to take place well before these programs. I'm not saying that there are not barriers later in life but so much of it is formed very early including the tendency for some men to think that women are not able to manage this stuff. For every young girl discoraged there are young boys hearing the same thing. They both learn early that " Girls aren't good at math or engineering."mIf we don't change this at a very young age then a highschool aged program will have little to no effect.
While I disagee about the two genders thing you clearly don't understand what cis means. A cis man was born genetically male and identifies as male. A cis female was born genetically female and identifies as female. The opposite is trans. A trans man was born genetically female but identifies as a man. A trans woman was born genetically male but identifies as a woman.
The prefix is derived from the terms trans and cis as they are used in chemistry. Cis is not a gender, it, like trans, it refers to the dynamic between genetic sex and gender identity.
Really? The extra time you would spend commuting would be at a rate of roughly $180 an hour if you took the higher paying job. I would gladly commute for that much more money per hour of commute.
The entire argument was based on the idea that they won't move it until something horrible happens... but other than that, yeah, bad shit can happen anywhere. The idea here is risk mitigation. If this stuff sits indefinitely at these small storage locations something bad almost certainly will eventually happen because it will be there forever (practically speaking). The same thing is true at a central location, something bad will eventually happen, the hope is that you can push that off and minimize the risk of the bad thing happening by having only one location that has a lot of resources thrown at it.
Transport is hard, its a big deal and it is a problem for a lot of materials. There isn't much getting around that, but it is also a limited operation and you can take the best precautions possible. The question is what has the biggest risk, moving it or not moving it. The problem is that we, as humans, are very bad at assessing risk. The point of my post wasn't that it was the right thing to do to move it all, but that the decision will be made based on the reaction of a bunch of people to an incident happening and not based on a rational assessment of the options. We make decisions out of fear, rarely out of rational thought. Just look a the people who refuse to vaccinate their kids.
don't worry, eventually something bad will happen, hopefully not to close to where you live, and the political motivation to deal with this shit will suddenly exist and some of the same people opposed to yucca now will be clamoring for a centralized storage solution and wondering why we let this stuff sit all over the country for so long.
do you really think that the banks in the rest of the world wont have the same back doors? Even if they don't, any flaws they do have will be exposed to whomever gets their hands on the source provided to the Chinese (here is a hint, most of those people are probably not going to responsibly report the flaws so this is not a case of many eyes resulting in more secure code, but a few eyes finding ways to compromise code).
I know the article says that these companies can't afford to ignore china, but really, if they all got together and said no, could china really afford that? They could always make their own banking software I suppose. Why don't we let them?
It is up to the refs to measure the balls and fill them if they are low. If the refs failed to do their jobs maybe the league should be taking a closer look at them.
It is not likely to be cost effective to keep cities open. Clearing snow at a pace that lets you keep the roads open is very costly and hard on the environment. Keeping public transit running is similarly expensive. The cost is productivity for a day but given that these days many people get work done at home the impact of that is somewhat less than it was in the past. We always used to shut down for the worst storms, sometimes the call was made late and people would get stuck. Now the balance has shifted so it makes more economic sense to shut down services for a day to let the snow pass and clear everything out for the next day.
Where did we get the starting pressure from before game time. Were those numbers ever released? Because without knowing what the pressure was when they were first checked you can't possibly know how much the pressure changed making an analysis using PV=nRT basically meaningless.
I do not believe the NFL has released those numbers. Quite possibly because they don't have them because they balls were never actually measured by the refs at the start of the game (They often are not they are only checked visually and by hand).
Slashdot Mirror
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
Sex (the biological definition, not the act) and gender are not the same thing
The thing is these discourage to take place well before these programs. I'm not saying that there are not barriers later in life but so much of it is formed very early including the tendency for some men to think that women are not able to manage this stuff. For every young girl discoraged there are young boys hearing the same thing. They both learn early that " Girls aren't good at math or engineering."mIf we don't change this at a very young age then a highschool aged program will have little to no effect.
While I disagee about the two genders thing you clearly don't understand what cis means. A cis man was born genetically male and identifies as male. A cis female was born genetically female and identifies as female. The opposite is trans. A trans man was born genetically female but identifies as a man. A trans woman was born genetically male but identifies as a woman.
The prefix is derived from the terms trans and cis as they are used in chemistry. Cis is not a gender, it, like trans, it refers to the dynamic between genetic sex and gender identity.
When everyone is carrying a short sword bet on the guy that also has a shield.
Yes
Really? The extra time you would spend commuting would be at a rate of roughly $180 an hour if you took the higher paying job. I would gladly commute for that much more money per hour of commute.
The entire argument was based on the idea that they won't move it until something horrible happens... but other than that, yeah, bad shit can happen anywhere. The idea here is risk mitigation. If this stuff sits indefinitely at these small storage locations something bad almost certainly will eventually happen because it will be there forever (practically speaking). The same thing is true at a central location, something bad will eventually happen, the hope is that you can push that off and minimize the risk of the bad thing happening by having only one location that has a lot of resources thrown at it.
Transport is hard, its a big deal and it is a problem for a lot of materials. There isn't much getting around that, but it is also a limited operation and you can take the best precautions possible. The question is what has the biggest risk, moving it or not moving it. The problem is that we, as humans, are very bad at assessing risk. The point of my post wasn't that it was the right thing to do to move it all, but that the decision will be made based on the reaction of a bunch of people to an incident happening and not based on a rational assessment of the options. We make decisions out of fear, rarely out of rational thought. Just look a the people who refuse to vaccinate their kids.
don't worry, eventually something bad will happen, hopefully not to close to where you live, and the political motivation to deal with this shit will suddenly exist and some of the same people opposed to yucca now will be clamoring for a centralized storage solution and wondering why we let this stuff sit all over the country for so long.
do you really think that the banks in the rest of the world wont have the same back doors? Even if they don't, any flaws they do have will be exposed to whomever gets their hands on the source provided to the Chinese (here is a hint, most of those people are probably not going to responsibly report the flaws so this is not a case of many eyes resulting in more secure code, but a few eyes finding ways to compromise code).
I know the article says that these companies can't afford to ignore china, but really, if they all got together and said no, could china really afford that? They could always make their own banking software I suppose. Why don't we let them?
It is up to the refs to measure the balls and fill them if they are low. If the refs failed to do their jobs maybe the league should be taking a closer look at them.
Yeah but it's really about all the words you don't repeat.
It is not likely to be cost effective to keep cities open. Clearing snow at a pace that lets you keep the roads open is very costly and hard on the environment. Keeping public transit running is similarly expensive. The cost is productivity for a day but given that these days many people get work done at home the impact of that is somewhat less than it was in the past. We always used to shut down for the worst storms, sometimes the call was made late and people would get stuck. Now the balance has shifted so it makes more economic sense to shut down services for a day to let the snow pass and clear everything out for the next day.
Where did we get the starting pressure from before game time. Were those numbers ever released? Because without knowing what the pressure was when they were first checked you can't possibly know how much the pressure changed making an analysis using PV=nRT basically meaningless.
I do not believe the NFL has released those numbers. Quite possibly because they don't have them because they balls were never actually measured by the refs at the start of the game (They often are not they are only checked visually and by hand).