See, the funny thing is, I do tell my manager how fast I can go. It's part of my job to let my manager know how much I can accomplish. And I'm not just talking about my current one, but every manager I've had in the past 15 years. As in I'm a professional and I take my work seriously, which means I expend some effort to ensure that I can do the best work I can. It also means I expect and receive proper equipment and applications to allow me to do my work efficiently. Sometimes the company provides those resources and sometimes I do, but you can't build good software by slapping crap together at a thousand miles an hour. Or rather you can. For about fifteen minutes.
This is a BS mindset. It is the equivalent of an automobile manufacturer saying I don't have time to tighten the bolts on the car properly. Yes, it's probably good enough to roll out the door, but the flaws will start showing through soon -- perhaps catastrophically. I think it's our job as developers to push back against those crushing deadline and own up to some professional pride. Stop being bossed around. There is a difference between a job and a profession, the person doing the work.
Apple delivers a standard one year warranty which you can pop to 3, Dell provides the same warranty but extends to 4 years AND I've never so much as talked to a Dell rep since I'm certified, I just RMA my own hardware without an issue. Can't do that for the Mac w/o a huge hassle. I won't mention that we replace more power supplies out of Macs than we do Dell desktops and its not uncommon for a crapped out PS to toast the entire Mac.
FWIW, the OP can buy an AMD Neo whatever now, pocket the other $500 bucks and buy a newer model when the original dies. Now he's still spent less than the MBA and he's got newer faster hardware. And honestly, he can probably scrap parts out of the old netbook if he desires. After three years your non-replaceable battery has shortened up it's lifespan to the point where it's easier to measure in minutes than hours and if our customers are any example, at least one hinge is busted and you've lost a key.
Logically you can't both resell your laptop and keep it for the long hall. Either it dies and you buy a new one, or you sell it and it's a case of diminishing returns, no one will want your four year old MBA badly enough to let you buy another one anyway.
Eventually you too will realize that all hardware sucks, all software sucks and all technology sucks. Or you'll still be a fanboi, either way I'm too old and tired to give a crap as long are you're too stupid to care.
You know, having been through both a professional program and a graduate program, it's all crap. Everyone (including programmers) wants everyone else to think they're busting their humps 25 hours a day, but it just ain't so. Being still active in a professional program (Veterinary if you must know), I can tell you that we do dump a load of work, but given the rate of parties/social events/professional & club meetings that go on, it certainly isn't a crippling workload.
On the plus side, I do agree that undergrad degrees prepare you for professional degrees like toilet training prepares you to drive.
Sigh. The problem is a failure to correctly parameterize the LD50 and LD90 of the substance. Every substance (and I do mean EVERY -- human protein, interplanetary lint or whatever else may come) has a lethal dose. It's the trials function to determine if the new drug A) works properly and B) works safely.
The problem with human trials is that they aren't terminal studies. You can't have a pathologist go over each of the subjects with a fine tooth comb or do a complete histopathic workup (you can get close, but very few people want to give up heart and/or brain samples).
Around here at least the trials coordinator determines the protocol to be used, which would (if this is how Paraxel runs) put the blame squarely on them (provided that the pharm company actually disclosed proper information).
I have to second this. My wife is a medical researcher and having ridden along on many of her research projects I can say that there would be hell to pay for this magintude of screw up. In her trials, things get unglued when there is a test subject with a +/- 1% variance over expected, so I can't bring myself to believe that this company had no clue that this was a possible outcome IF they had done their proper pre-human testing. I'm 99% certain that most of the researcher on a trial drug would have popped their corks, both out of honest moral outrage and as a career saving move.
On the downside, as it becomes increasingly unpopular to test on animals there will be more and more poorly tested drugs making it to human test subjects. I strongly suspect that this won't be the last or worst trial to have this form of traumatic outcomes.
Slashdot Mirror
Really? Try switching where your window controls are located. I'll wait until you get back.
See, the funny thing is, I do tell my manager how fast I can go. It's part of my job to let my manager know how much I can accomplish. And I'm not just talking about my current one, but every manager I've had in the past 15 years. As in I'm a professional and I take my work seriously, which means I expend some effort to ensure that I can do the best work I can. It also means I expect and receive proper equipment and applications to allow me to do my work efficiently. Sometimes the company provides those resources and sometimes I do, but you can't build good software by slapping crap together at a thousand miles an hour. Or rather you can. For about fifteen minutes.
This is a BS mindset. It is the equivalent of an automobile manufacturer saying I don't have time to tighten the bolts on the car properly. Yes, it's probably good enough to roll out the door, but the flaws will start showing through soon -- perhaps catastrophically. I think it's our job as developers to push back against those crushing deadline and own up to some professional pride. Stop being bossed around. There is a difference between a job and a profession, the person doing the work.
Then back the kwality up with a warranty.
Apple delivers a standard one year warranty which you can pop to 3, Dell provides the same warranty but extends to 4 years AND I've never so much as talked to a Dell rep since I'm certified, I just RMA my own hardware without an issue. Can't do that for the Mac w/o a huge hassle. I won't mention that we replace more power supplies out of Macs than we do Dell desktops and its not uncommon for a crapped out PS to toast the entire Mac.
FWIW, the OP can buy an AMD Neo whatever now, pocket the other $500 bucks and buy a newer model when the original dies. Now he's still spent less than the MBA and he's got newer faster hardware. And honestly, he can probably scrap parts out of the old netbook if he desires. After three years your non-replaceable battery has shortened up it's lifespan to the point where it's easier to measure in minutes than hours and if our customers are any example, at least one hinge is busted and you've lost a key.
Logically you can't both resell your laptop and keep it for the long hall. Either it dies and you buy a new one, or you sell it and it's a case of diminishing returns, no one will want your four year old MBA badly enough to let you buy another one anyway.
Eventually you too will realize that all hardware sucks, all software sucks and all technology sucks. Or you'll still be a fanboi, either way I'm too old and tired to give a crap as long are you're too stupid to care.
You know, having been through both a professional program and a graduate program, it's all crap. Everyone (including programmers) wants everyone else to think they're busting their humps 25 hours a day, but it just ain't so. Being still active in a professional program (Veterinary if you must know), I can tell you that we do dump a load of work, but given the rate of parties/social events/professional & club meetings that go on, it certainly isn't a crippling workload. On the plus side, I do agree that undergrad degrees prepare you for professional degrees like toilet training prepares you to drive.
Sigh. The problem is a failure to correctly parameterize the LD50 and LD90 of the substance. Every substance (and I do mean EVERY -- human protein, interplanetary lint or whatever else may come) has a lethal dose. It's the trials function to determine if the new drug A) works properly and B) works safely. The problem with human trials is that they aren't terminal studies. You can't have a pathologist go over each of the subjects with a fine tooth comb or do a complete histopathic workup (you can get close, but very few people want to give up heart and/or brain samples). Around here at least the trials coordinator determines the protocol to be used, which would (if this is how Paraxel runs) put the blame squarely on them (provided that the pharm company actually disclosed proper information).
I have to second this. My wife is a medical researcher and having ridden along on many of her research projects I can say that there would be hell to pay for this magintude of screw up. In her trials, things get unglued when there is a test subject with a +/- 1% variance over expected, so I can't bring myself to believe that this company had no clue that this was a possible outcome IF they had done their proper pre-human testing. I'm 99% certain that most of the researcher on a trial drug would have popped their corks, both out of honest moral outrage and as a career saving move. On the downside, as it becomes increasingly unpopular to test on animals there will be more and more poorly tested drugs making it to human test subjects. I strongly suspect that this won't be the last or worst trial to have this form of traumatic outcomes.