Hi, Tim Cook, is that you?
Anonymous usually = slashvertisement...
Hi, Tim Cook, is that you?
Anonymous usually = slashvertisement...
Take them to 1981 and give then an Apple II or a Commodore PET? And a 100 different copies of "Compute" magazine so they can type in their own programs and get immediate gratification from a small amount of code?
Finding bugs is ALWAYS fun!
What's even more fun is that Tesla Roadster you were able to buy by selling the bugs you find to intelligence agencies, rather than reporting them to the vendor and being sued under the DMCA for reverse engineering their product.
Food is often social and portions are uncontrolled. This is especially true if you eat out a lot to get that social interaction.
There is a rather famous Cornell study that showed people will basically eat what's in front of them until it's gone:
A good trick if you eat out is to immediately ask for a "to go" container, and then put half your restaurant portion into the container, close it, and set it aside. Then enjoy the remainder and the social interaction that usually goes with eating out.
Other people have pointed out that is not the case, but I thought I would address the pregnancy thing.
Pregnancy studies are a high risk/low reward proposition, unless you are talking about fertility, anti-miscarriage or other pregnancy related applications, since including pregnant women in a clinical trial has a really high settlement cost if there's a problem with the pregnancy, and an even higher cost if the baby comes out with a birth defect. As an example, women with hair loss get warned against finesteride, since it acts as a 4-5 reductase suppression agent, which, when it occurs naturally (5-ARD), results in conditions from hypospadias needing surgical correction, all the way to full blown X-Y females (sterile of course).
It's fairly common to warn pregnant women not to take a medication, even if in fact it might be perfectly safe because of the exclusionary nature of the studies. This is purely a legal liability/malpractice issue, not necessarily an issue with the medication itself.
No that's what the summary tries to imply what the research says, count on research from LA being negative towards public transport.
Actually, I read both articles and the summary, and it doesn't seem to be what they are trying to imply at all.
But I agree with the GP that you get more control over people's ability to move around, if you limit them to bicycles or public transportation; for example, the BART stations that have been shut down to try and prevent protests against them shutting of cellular service in order to prevent previous protests, the ability to take busses and trains out of service to limit the ability of people without cars to move around and so on. They also tended to shutdown BART stations near the Occupy movement when it was still going on to any extent. Handy if you are trying to stop a zombie outbreak as well, I guess.
With the exception of short hall train corridors (because BART and CalTrain can't agree to share), and of course the Facebook/Google/Apple/Genentech/etc. busses run by those and similar private companies, public transit is pretty crappy in the SF Bay Area. The incessant BART strikes also tend to discourage use of public transit as well, but that's more about the unions blackmailing the politicians by pissing off voters than it is about controlling peoples movements.
The FDA was very clear about why they stopped it. It wasn't necessarily that the information was misleading, but that it would lead patients to make decisions about their own care without necessarily consulting a doctor, which the FDA thinks is not a good idea -- and I totally see their point, frankly.
The FDA made them stop because doctors dislike being cut out of the loop, and insurance companies like being cut out of the loop even less than the doctors, and they would prefer to have you get the data through a disclosure mechanism which gives your insurance company better actuarial information. "Having a Dr. explain the information to the patients one on one" is just a place to hang that hat.
For example, one of the things that 23andMe can tell you is how well you might respond to one drug versus another, because of your specific genetic makeup. If you take that advice and change the dosage of your medication or switch to a different medication without discussing the issue with your doctor, you could cause yourself serious harm.
Yeah, in case you wondered, people can not self prescribe non-over the counter medications. So that excuse doesn't fly, either, since your doctor will be involved in writing the script for the new medication, and your insurance company will be paying for it, and like mine did, probably try to give you a cheaper generic version of a similar drug in place of the one your doctor actually wrote the script for, and then called it "equivalent". I've had that pulled on me, and been given "generic allergy medication" containing a cornstarch binder in place of the other one - when corn products were why I taking the damn stuff in the first place.
I vote you go with Nightingale, and fix the file organization feature. IT's clear from your FLOSS requirement that you are a fan of Open Source, so send patches: that's what you do with Open Source.
If you don't want to do that because you're not a coder, then you might as well just with a closed source product, since it's not like you'll be looking at the code.
...and report the bullets as stolen.
... just remember that you have to empty a at least one 10 round pistol clip into the guy before you've hosed off five dollars worth of ammo.
Hollowpoints and rifle ammo may add up to more than $5 before you empty the magazine.
analog channels were mostly on VHF (better propagation around obstacles). Digital is mostly on UHF where it's pretty much line-of-sight
There's still lots of digital TV on VHF. In Las Vegas, for instance, five of the local broadcasters are on VHF. One of them (KSNV) is even on low-band VHF.
I don't think it's so much about Facebook = the global water cooler" (what a terrible analogy! I'm sure Facebook corporate loves it...).
Some people are simply not going to pay to access your content, and you can shut down every channel possible (you can't, it's an impossible to achieve goal from a technology standpoint), and doing that is not going to convert these people into your customers. This is a "look at all the money we COULD be making IF ONLY these people were willing to pay for our product, which we are SURE they WOULD, if the only way to see the next episode of our reality TV series was to pay us for it!" argument. It's an invalid argument.
For all the "can not fail" systems I've worked on, there has been an identical set of hardware, along with other hardware to simulate load
Yeah gramps, we did all that in history class, along with slideframes and mainrules and all that.
That's obsolete now because cloud and agile and webscale.
Let me know when you get the next G.E. Medical systems MRI system running "in the cloud" rather than on a a local control system and a console in the next room, and then trust your life to the thing. Meanwhile, I think I will probably stick with the medical equipment I've worked on instead.
P.S.: Let me know when your cloud is HIPPA certified.
Elon Musk should be looking at Ford management and asking himself what they know about making and selling cars that he doesn't.
That's a brilliant Idea! They could introduce a "Tesla Pinto", and have the cars actually explode and kill people, just like Ford: http://en.wikipedia.org/wiki/Ford_Pinto#Fuel_tank_defect
And then they could ask for a bailout from the Term Asset-Backed Securities Loan Facility (TALF) like Ford Credit did (and on which they still owe money to the Fed): http://useconomy.about.com/od/criticalssues/a/auto_bailout.htm
Maybe the media scrutiny is that Tesla's actually caught fire, and Ford is proactively recalling because there is a potential fire?
Actually, if you read the article, you will see that both sets of vehicles are having approximately one fire per 10,000...
"There have been 12 reported fires but no injuries in the bigger recall of 139,917 Ford Escape vehicles."
At some point in their careers, all programmers, after spending a month hunting down a heap corruption, or a race condition, or some other bug nasty like that, come to the realisation that they are spending more time fixing mistakes than writing code. At this moment, most, but not all programmers follow a very logical path of reasoning. They think to themselves, "well, if this code took me 1 week to write, then 4 to fix, that is five weeks, what if I spent 3 weeks writing it carefully, then it would be done right away and I wouldn't have to fix it, I could have been done two weeks earlier!".
From that moment on, this programmer becomes all but useless to their current and future employers.
There are those who build the prototypes, and those who build the products. The second kind is "Mr./Ms. Right"; the first kind is "Mr./Ms. Right Now".
If your business is about churning your web site design every so often, and you aren't doing a lot of back end processing that requires actual business logic, or if you are a startup that's trying to throw something together in a couple months so that you can get a bite from a V.C. and get the company funded by an Angel or other investor, then you can afford to hire a "Mr./Ms. Right Now", and in fact you should do so.
If on the other hand, you have to have a solid product that's going to either be shipped off to customers, or you're trying to do a Saleforce.com SAAS play to try and generate income, then you need the "Mr./Ms. Right" instead.
I've worked at a number of startups, and at some point, someone has to own the "It Works Bit", and that's not going to be the person who just slaps together prototypes with spit and bailing wire, and hopes for the best. I was most often the person owning that bit, and I've halted updates that would have resulted in the bricking of thousands of units at customer sites, with no way to back it out remotely. I've also reworked a lot of code that should have been written as an FSA, but instead was comparing for NULL everywhere because the young turk who wrote it didn't understand the state his variables were in at any given point. I've also done serious detail work that got one well known company out of a threatened $200M lawsuit. And I've done the necessary work to reverse engineer the requirements for embedded controllers on Samsung and Acer laptops so the trackpad didn't suck (one of the reasons for a recently recalled laptop, apart from the charger problem, is that the trackpads sucked because no one did that job this last time).
Yeah, if all you are doing is a Twitter Clone, then you can be pretty slack about the coding, at least until you get funded, but if you need to have real working code that's not just throw-away website code that won't be around next week anyway, you need "Mr./Ms. Right", not some prototyper.
"Everyone's head is a cheap movie show." -- Jeff G. Bone