Fixing a failed or behind software project in my experience was like stories I heard about battlefield medicine. You have to establish a system of triage where you realistically work under the assumption that not everything can be saved. At least not anytime in the near future. You're knee deep in digital blood stripping out one layer of feature after the other right down to the last thing that did work properly, and you have to start with what is the most simplest thing a user absolutely must be able to do that without that ability the project would be considered completely pointless and fix that before you write any other code. You have to act in a way towards users that might seem indifferent or cold, ignoring users' screams about your removing their daily reminder widget and you have to tell them in a tactful way that you won't put it back in anytime soon because your number one priority is making sure the accounting systems can actually add numbers correctly; you also have to make sure that if those users' are powerful stakeholders and order you to add back the fun happy reminded widget that they can be properly countermanded by higher authorities who have the authority to get them to shut up and sit on their hands.
In short, you have to piss a lot of people off and be committed to accomplishing your grim task.
If we make it too costly for American hacktivists to do their work here, then someone's just going to offshore the job of breaking into important industrial military complex computers to China.
Has far more data that is likely to hurt you than the NSA does, and they have no problem selling to anyone with enough money. Potential employers having access to my salary history without my consent scares me and will hurt me far more than the government knowing I called my aunt yesterday. Likewise with my insurance company knowing that I visited Dunkin Donuts yesterday. Put away your tinfoil hats and see the real threat.
It's an engineering tradeoff. You take away user's ability to change to custom keyboards and give them protection from a malicious, or even worse, well-intentioned 1 pixel high custom keyboard that effectively makes the keyboard disappear.
There's this wonderful and probably highly embellished anecdote about mac creator Jef Raskin where he had this friend that ranted and raved about how wonderful it was to be able to skin his Windows installation anyway he wanted, and challenged Raskin to prove otherwise. Raskin proceeded to sit at the computer and make every skinnable element on the friend's Windows UI red. Windows, buttons, toolbars, etc. So effectively the guy had an entirely red monitor and could not see anything to change it back and had to reinstall his OS to get a functional computer again.
As reviled as Apple might be by gearheads about issues like flexibility and not letting samsung et all reap all the rewards for taking none of the risks, Apple stands up to telcos and don't let them put crapware on the phone, and the stuff Apple themselves makes and puts on the phone they actually attempt to make decently. The walled garden keeps the bad people out as much as it keeps the good people in. Stuff like this generates loyalty, folks. It's not just fanboyism.
There's far more significant knowledge you take with you that you're not legally required to give up (procedures setting stuff up, what vendor bugs to work around, what authentication scheme, whatever). No need to go to jail over passwords when there's plenty of other petards for a former employer to hoist themselves on.
It's hard enough to work with one spotty vendor, let alone 55. That number, 55, represents somewhere between 55 and 55-squared lines of possibly iffy communication between possibly iffy organizations. When I first heard that healthcare.gov had 55 contractors working on it, I was surprised that the damn thing ran at all.
The astronauts freeze dried ice-cream would come through intact. Didn't you ever wonder why the stuff in the museum seems like it's been around for trillions of years?
Now what starts with the letter C? Cookie starts with C Let's think of other things That starts with C Oh, Cocaine start with C, too. And other things that start with C? Oh, who cares about the other things?
C is for cocaine, that's good enough for me. C is for cocaine, that's good enough for me. C is for cocaine, that's good enough for me Oh, cocaine, cocaine, cocaine starts with C.
Me thinks Oreo is delicious cookie. And Oreo's white addictive stuff Between two chocolate wafer Make me think of of cocaine Oh and big white moon also look like giant Scarface plate of Cocaine But you can't snort that, so....
C is for cocaine, that's good enough for me, yeah! C is for cocaine, that's good enough for me C is for cocaine, that's good enough for me Oh, cocaine, cocaine, cocaine starts with C, yeah! Cocaine, cocaine, cocaine starts with C, oh boy! Cocaine, cocaine, cocaine starts with C!
Forget that it's an uninhabitable super gas planet. At 25k light years away, it's only 4k light years away from the four million solar mass black hole at the center of the galaxy. That's a next door neighbor that might bring down the value of your real estate.
I think of it like a George Romero zombie that has plodded along consuming and destroying brains for the better part of two decades and clumsily getting around the shotgun programming language deficiencies with each new release.
To throw a few lawyers and systems administrators and delete the problem than it is to hire a few good interaction designers to fix it and deny the folks in marketing their 10 pieces of mandatory Facebook flair.
Well, that bit would make sense. If you divulge too many details, you leave clues as to how to came by your information which puts your spies and methods at risk. Which leads me to the next part...
Take tissue/DNA/blood/whatever samples from bunch of people who are from a very large bunch of people who've been exposed to some chemical and run scientific tests for that chemical. It's basic medical science; I can't believe there'd be anything sensitive or classified about the procedure itself, and there's probably enough medical NGO's operating in Syria that a three-letter organization could easily get samples without raising too many eyebrows.
Fixing a failed or behind software project in my experience was like stories I heard about battlefield medicine. You have to establish a system of triage where you realistically work under the assumption that not everything can be saved. At least not anytime in the near future. You're knee deep in digital blood stripping out one layer of feature after the other right down to the last thing that did work properly, and you have to start with what is the most simplest thing a user absolutely must be able to do that without that ability the project would be considered completely pointless and fix that before you write any other code. You have to act in a way towards users that might seem indifferent or cold, ignoring users' screams about your removing their daily reminder widget and you have to tell them in a tactful way that you won't put it back in anytime soon because your number one priority is making sure the accounting systems can actually add numbers correctly; you also have to make sure that if those users' are powerful stakeholders and order you to add back the fun happy reminded widget that they can be properly countermanded by higher authorities who have the authority to get them to shut up and sit on their hands.
In short, you have to piss a lot of people off and be committed to accomplishing your grim task.
Perhaps Silverlight has become self-aware and assumes that any upgrade would involve Microsoft trying to kill it off.
If we make it too costly for American hacktivists to do their work here, then someone's just going to offshore the job of breaking into important industrial military complex computers to China.
Has far more data that is likely to hurt you than the NSA does, and they have no problem selling to anyone with enough money. Potential employers having access to my salary history without my consent scares me and will hurt me far more than the government knowing I called my aunt yesterday. Likewise with my insurance company knowing that I visited Dunkin Donuts yesterday. Put away your tinfoil hats and see the real threat.
That it burns rubber *before* you hit the accelerator.
It's an engineering tradeoff. You take away user's ability to change to custom keyboards and give them protection from a malicious, or even worse, well-intentioned 1 pixel high custom keyboard that effectively makes the keyboard disappear.
There's this wonderful and probably highly embellished anecdote about mac creator Jef Raskin where he had this friend that ranted and raved about how wonderful it was to be able to skin his Windows installation anyway he wanted, and challenged Raskin to prove otherwise. Raskin proceeded to sit at the computer and make every skinnable element on the friend's Windows UI red. Windows, buttons, toolbars, etc. So effectively the guy had an entirely red monitor and could not see anything to change it back and had to reinstall his OS to get a functional computer again.
As reviled as Apple might be by gearheads about issues like flexibility and not letting samsung et all reap all the rewards for taking none of the risks, Apple stands up to telcos and don't let them put crapware on the phone, and the stuff Apple themselves makes and puts on the phone they actually attempt to make decently. The walled garden keeps the bad people out as much as it keeps the good people in. Stuff like this generates loyalty, folks. It's not just fanboyism.
Between phones and sex toys.
There's far more significant knowledge you take with you that you're not legally required to give up (procedures setting stuff up, what vendor bugs to work around, what authentication scheme, whatever). No need to go to jail over passwords when there's plenty of other petards for a former employer to hoist themselves on.
It's hard enough to work with one spotty vendor, let alone 55. That number, 55, represents somewhere between 55 and 55-squared lines of possibly iffy communication between possibly iffy organizations. When I first heard that healthcare.gov had 55 contractors working on it, I was surprised that the damn thing ran at all.
I guess someone will have to invent a MathJSON to make MathML acceptable for the hipsters.
Battling for the title of who has the smallest one.
Plus it attracted much unwanted attention from the copper-blooded species of the planet Chia 357.
The astronauts freeze dried ice-cream would come through intact. Didn't you ever wonder why the stuff in the museum seems like it's been around for trillions of years?
Now what starts with the letter C?
Cookie starts with C
Let's think of other things
That starts with C
Oh, Cocaine start with C, too.
And other things that start with C?
Oh, who cares about the other things?
C is for cocaine, that's good enough for me.
C is for cocaine, that's good enough for me.
C is for cocaine, that's good enough for me
Oh, cocaine, cocaine, cocaine starts with C.
Me thinks Oreo is delicious cookie.
And Oreo's white addictive stuff
Between two chocolate wafer
Make me think of of cocaine
Oh and big white moon also look like giant Scarface plate of Cocaine
But you can't snort that, so....
C is for cocaine, that's good enough for me, yeah!
C is for cocaine, that's good enough for me
C is for cocaine, that's good enough for me
Oh, cocaine, cocaine, cocaine starts with C, yeah!
Cocaine, cocaine, cocaine starts with C, oh boy!
Cocaine, cocaine, cocaine starts with C!
Forget that it's an uninhabitable super gas planet. At 25k light years away, it's only 4k light years away from the four million solar mass black hole at the center of the galaxy. That's a next door neighbor that might bring down the value of your real estate.
Dark matter must explain why it's bigger than it looks.
I think of it like a George Romero zombie that has plodded along consuming and destroying brains for the better part of two decades and clumsily getting around the shotgun programming language deficiencies with each new release.
Before it turns into a tropical paradise with a race of 36-24-36 sex-starved tribewomen who live next to lakes of single malt scotch.
12 out of 30 Helens agree with your conclusion about statistics.
We Objective-C developers prefer more verbose WTF statements, such as
- (void)whatTheFuckAreYouDoing:(NSString *)wtf withThatAbsurdAlgorithm:(NSString *)algorithm thatOnlyOnePersonOnDevTeamUnderstands:(BOOL)doesHeReallyUnderstandIt;
To throw a few lawyers and systems administrators and delete the problem than it is to hire a few good interaction designers to fix it and deny the folks in marketing their 10 pieces of mandatory Facebook flair.
Take tissue/DNA/blood/whatever samples from bunch of people who are from a very large bunch of people who've been exposed to some chemical and run scientific tests for that chemical. It's basic medical science; I can't believe there'd be anything sensitive or classified about the procedure itself, and there's probably enough medical NGO's operating in Syria that a three-letter organization could easily get samples without raising too many eyebrows.
But I'm not a spy, so what the heck do I know.
Where do you pee?
Must Come Down.