Infants can't be vaccinated immediately, but they're susceptible to disease. Some people have health problems that prevent them from being vaccinated. If my child died as a result of a preventable disease that they contracted while too young to be vaccinated and I found out they were infected by an the child of an anti-vax nutjob I think I'd have little choice but to kill the anti-vax parents. I'm quite sure I'd have a hard time staying my hand. People who are that anti-social and selfish don't deserve to live.
You mean like this Australian family who's baby died before it could be vaccinated and then they where harassed by anti-vac nutjobs.
Tamiflu is not a vaccine, it is an anti-viral (and only mildly effective at that).
Vaccinations are a numbers game. There are always side effects, but the risk of side effects from the vaccination is so much lower than risk of side effects from the disease that it is worth it. That doesn't mean that someone won't get something from the vaccination, only that on a population level it makes sense.
Why do you think that almost no one gets smallpox vaccinations now? Because the risk from the vaccination is so high compared to the risk of getting the disease (which is now formally eradicated). Basically now only the US military receives smallpox vaccinations.
If the risk from measles is 1 in 20 of getting pneumonia or 1 in 2000 of encephalitis then I think the 1 in millions odds of getting a vaccine complication are worth it.
And having suffered shingles at the age of 40 I can tell you that it was the worst experience of my adult life. Any childhood vaccination that could have prevented that would have saved a week of extreme pain. And I had a very mild case.
But I call total and utter bullshit on "many". It was just a few cases out of millions of vaccination doses and it was determined that the populations affected already had a genetic disposition to narcolepsy.
I'm just annoyed they took away the ability to set the damn desktop fonts. I have a 30" monitor. I don't want to waste all that space with freaking jumbo netbook sized fonts.
Actually someone has put together the entire history of his edits to Star Wars and makes the case that it was exactly as you said. Most of it came about through chance and by bending existing story lines to link it all together.
There never was "9" movies in the series or anything that George Lucas has suggested in the past.
The history used to be available as a free PDF, but in any case it looks like the author has made it into a read book now. http://secrethistoryofstarwars.com/
A lot of this is probably that in OSX there is pretty much one official way to do things and one official development environment and language. In Windows there are dozens of ways, many of which hide from the developer that there are even such features available. Nothing in Windows forces you to support all the possible window messages, and probably most Windows "developers" don't even know what WM_CLOSE or WM_PAINT signify.
Perhaps Apple can force compliance as a requirement to get into the Mac Apps Store.
Yes, Microsoft Office implements the Restart Manager. It might be the only app that does. MS doesn't have any concept of Auto Save, but it is not a new idea. I know that UI experts have requested exactly that feature for decades.
NTFS has supported journelling for years and has Previous Versions feature (available from file Properties). Application resuming/restarting has been around since Vista and the OS has several hooks for registering for these events and messages. The fact that no-one implements it isn't relevant.
That is entirely true, but the question was what to say in such situations (running over a child) that don't invoke any deities. You can just say like the cops in "Law and Order", "I'm sorry for your loss".
For the rational atheists among us in such situations, you may as well say, "shit happens".
In Finnish you say "otan osa" which doesn't literally translate well to English. But it basically means I feel your loss, or I feel for you. Doesn't invoke any gods at all.
SUVs in Europe are in general much smaller than an SUV in the US and are usually not a "truck". SUVs in the US were made on the same chassis as a light truck and with similar weight, so got the truck tax breaks and emission categories.
But in Europe a SUV is most like to be a Honda CRV, Toyota RAV4, or Kia Sportage. Those are most definitely not trucks. The only exception is a large Mercedes 4WD or maybe a Range Rover, but there is very little on the scale of a Ford Explorer.
The main conclusion is that TDD will reduce your fault count significantly, but INCREASES the time taken to deliver a feature. I have heard the same thing for other agile methods.
And from my own experience there are definitely times where 20% of the time was taken to implement a user story and 80% of the time taken writing test cases.
That also doesn't matter. Agile, doesn't say you have to ship at the end of each sprint. It just says that you have a "potentially" shippable product.
The company where I work has many scrum teams (hundreds of developers across the world) all working on different parts of an extremely large product. The entire product is only shipped every 6 months or so, but the sprint is usually only 2 or 3 weeks.
Then you aren't breaking the tasks down into small enough parts.
The point of the sprints is that at the end of each sprint you have something to show and everyone can see your progress. Three months sprints isn't agile, it is mini waterfalls.
Still not quite SCRUM (and I have done a scrum-masters course).
The goal of agile is to deliver the greatest benefit to the customer. Their representative in your team is the product owner. They don't just "throw the requirements at you". They should be making a backlog of implementable features (user stories) initially ranked by priority. You are then supposed to be estimating the complexity of those in order for the product owner to decide which is the most important given the resources and difficulty (this is a periodic backlog grooming session).
At the start of each sprint you select some stories and once you have estimated the tasks and effort for those stories you, as a team, commit to delivering those features. The daily standup meetings are for you to share you progress with each other (and update the burn-down chart). Peer pressure among the team is what gives the guilt-trip if you miss a day. The burn-down chart is what gives the product owner the state of the current sprint.
SCRUM has a very strict process. It is very light, but it still has rules and roles to follow. Anyone who tells you otherwise doesn't know what they are doing.
And there is no such thing as a "fair scrum master". The scrum masters role is just to assist the team to organize itself and keep the wolves away. They are not your boss.
Slashdot Mirror
Infants can't be vaccinated immediately, but they're susceptible to disease. Some people have health problems that prevent them from being vaccinated. If my child died as a result of a preventable disease that they contracted while too young to be vaccinated and I found out they were infected by an the child of an anti-vax nutjob I think I'd have little choice but to kill the anti-vax parents. I'm quite sure I'd have a hard time staying my hand. People who are that anti-social and selfish don't deserve to live.
You mean like this Australian family who's baby died before it could be vaccinated and then they where harassed by anti-vac nutjobs.
http://www.smh.com.au/national/antivaccine-group-a-threat-20100726-10smn.html?rand=1280210266036
There are still vaccinations for polio. Polio is not yet eradicated, although there is hope that its time is coming.
Tamiflu is not a vaccine, it is an anti-viral (and only mildly effective at that).
Vaccinations are a numbers game. There are always side effects, but the risk of side effects from the vaccination is so much lower than risk of side effects from the disease that it is worth it. That doesn't mean that someone won't get something from the vaccination, only that on a population level it makes sense.
Why do you think that almost no one gets smallpox vaccinations now? Because the risk from the vaccination is so high compared to the risk of getting the disease (which is now formally eradicated). Basically now only the US military receives smallpox vaccinations.
If the risk from measles is 1 in 20 of getting pneumonia or 1 in 2000 of encephalitis then I think the 1 in millions odds of getting a vaccine complication are worth it.
Yes, there have been large scale studies of the rates of autism between vaccinated and non-vaccinated and there are absolutely no difference at all.
http://www.ncbi.nlm.nih.gov/pmc/articles/PMC1124634/
Of course the anti-vaccination fucktards will dispute anything.
Actually contrary to popular opinion chicken pox can have serious side effects including encephalitis and death.
http://www.jennymccarthybodycount.com/Jenny_McCarthy_Body_Count/Whats_The_Harm.html
And having suffered shingles at the age of 40 I can tell you that it was the worst experience of my adult life. Any childhood vaccination that could have prevented that would have saved a week of extreme pain. And I had a very mild case.
Actually one particular swine flu vaccination did cause narcolepsy.
http://www.euro.who.int/en/what-we-do/health-topics/communicable-diseases/influenza/news/news/2011/09/finnish-national-narcolepsy-task-forces-final-report-published
http://www.who.int/vaccine_safety/topics/influenza/pandemic/h1n1_safety_assessing/narcolepsy_statement/en/index.html
But I call total and utter bullshit on "many". It was just a few cases out of millions of vaccination doses and it was determined that the populations affected already had a genetic disposition to narcolepsy.
That has been discounted. It was most likely biological contamination when the Surveyor cameras were brought back to Earth.
http://www.space.com/11536-moon-microbe-mystery-solved-apollo-12.html
I'm just annoyed they took away the ability to set the damn desktop fonts. I have a 30" monitor. I don't want to waste all that space with freaking jumbo netbook sized fonts.
Actually someone has put together the entire history of his edits to Star Wars and makes the case that it was exactly as you said. Most of it came about through chance and by bending existing story lines to link it all together.
There never was "9" movies in the series or anything that George Lucas has suggested in the past.
The history used to be available as a free PDF, but in any case it looks like the author has made it into a read book now.
http://secrethistoryofstarwars.com/
This most likely didn't happen at all. It was contamination on Earth after it was brought back.
http://en.wikipedia.org/wiki/Reports_of_Streptococcus_mitis_on_the_moon
A lot of this is probably that in OSX there is pretty much one official way to do things and one official development environment and language. In Windows there are dozens of ways, many of which hide from the developer that there are even such features available. Nothing in Windows forces you to support all the possible window messages, and probably most Windows "developers" don't even know what WM_CLOSE or WM_PAINT signify.
Perhaps Apple can force compliance as a requirement to get into the Mac Apps Store.
Yes, Microsoft Office implements the Restart Manager. It might be the only app that does. MS doesn't have any concept of Auto Save, but it is not a new idea. I know that UI experts have requested exactly that feature for decades.
No, you have to implement it yourself.
Straight from Apple. http://www.apple.com/macosx/whats-new/features.html#autosave
"Apps developed with Auto Save can automatically save changes"
I guess you aren't a developer. It might be easier if you use CoreData, but you don't get it for free.
Who said anything about easy access?!
NTFS has supported journelling for years and has Previous Versions feature (available from file Properties). Application resuming/restarting has been around since Vista and the OS has several hooks for registering for these events and messages. The fact that no-one implements it isn't relevant.
http://msdn.microsoft.com/en-us/library/bb525422(v=vs.85).aspx
http://msdn.microsoft.com/en-us/library/bb525423(v=vs.85).aspx
http://msdn.microsoft.com/en-us/library/aa373651(VS.85).aspx
It will be the same in Lion. Unless the apps are rewritten to support these features they won't work. It doesn't just happen magically.
Windows 7.
That is entirely true, but the question was what to say in such situations (running over a child) that don't invoke any deities. You can just say like the cops in "Law and Order", "I'm sorry for your loss".
For the rational atheists among us in such situations, you may as well say, "shit happens".
In Finnish you say "otan osa" which doesn't literally translate well to English. But it basically means I feel your loss, or I feel for you. Doesn't invoke any gods at all.
SUVs in Europe are in general much smaller than an SUV in the US and are usually not a "truck". SUVs in the US were made on the same chassis as a light truck and with similar weight, so got the truck tax breaks and emission categories.
But in Europe a SUV is most like to be a Honda CRV, Toyota RAV4, or Kia Sportage. Those are most definitely not trucks. The only exception is a large Mercedes 4WD or maybe a Range Rover, but there is very little on the scale of a Ford Explorer.
My point was that fuel reprocessing wasn't a waste of time.
I thought you were meaning that reprocessing was a failure. The grandparent was just confused about the name of the technologies.
I would rather listen to these people than some random commenter or on Slashdot.
http://www.scientificamerican.com/article.cfm?id=smarter-use-of-nuclear-waste
http://energyfromthorium.com/
I'm not going to dig up all the references, but this was one study I had heard of.
http://allankelly.blogspot.com/2010/08/study-on-benefits-of-tdd.html
The main conclusion is that TDD will reduce your fault count significantly, but INCREASES the time taken to deliver a feature. I have heard the same thing for other agile methods.
And from my own experience there are definitely times where 20% of the time was taken to implement a user story and 80% of the time taken writing test cases.
I mean in delivering new features. Main benefit seems to be just adaptability to change and improved fault levels.
That also doesn't matter. Agile, doesn't say you have to ship at the end of each sprint. It just says that you have a "potentially" shippable product.
The company where I work has many scrum teams (hundreds of developers across the world) all working on different parts of an extremely large product. The entire product is only shipped every 6 months or so, but the sprint is usually only 2 or 3 weeks.
Then you aren't breaking the tasks down into small enough parts.
The point of the sprints is that at the end of each sprint you have something to show and everyone can see your progress. Three months sprints isn't agile, it is mini waterfalls.
Still not quite SCRUM (and I have done a scrum-masters course).
The goal of agile is to deliver the greatest benefit to the customer. Their representative in your team is the product owner. They don't just "throw the requirements at you". They should be making a backlog of implementable features (user stories) initially ranked by priority. You are then supposed to be estimating the complexity of those in order for the product owner to decide which is the most important given the resources and difficulty (this is a periodic backlog grooming session).
At the start of each sprint you select some stories and once you have estimated the tasks and effort for those stories you, as a team, commit to delivering those features. The daily standup meetings are for you to share you progress with each other (and update the burn-down chart). Peer pressure among the team is what gives the guilt-trip if you miss a day. The burn-down chart is what gives the product owner the state of the current sprint.
SCRUM has a very strict process. It is very light, but it still has rules and roles to follow. Anyone who tells you otherwise doesn't know what they are doing.
And there is no such thing as a "fair scrum master". The scrum masters role is just to assist the team to organize itself and keep the wolves away. They are not your boss.