751 karma · joined May 30, 2008
I don't know how many times production was saved because there was an automated test written via TDD that prevented bad code from going out. Too many times to count.
What the author is suggesting is to throw this out and go back to the days of broken production apps are okay. This has never bothered Facebook, and it will definitely bother engineers who want to take pride in their work.
Let's say you pony up rent for your YCombinator startup and are paying about $2400 / month + utilities for 3 months. Let's say you get your food & other necessities costs to $80 / week.
That's an $8160 investment.
What you get back are the weekly dinners with great speakers. The connections you make should be worth at least $150k if your startup fails and you have to use that connection to get a job. I'm assuming a markup in your value as an employee for just getting into YCombinator.
$8160 and you can make 20% - 35% more than your peers if it fails.
$8160 in lottery tickets will pretty much get you zero if you fail.
Yes, sending an email can be free.
But the infrastructure for the Internet? The article really ignored how many tax payer dollars went into different public institutions to make the Internet a reality, e.g. Big Government and universities.
Managers often ask me how they can make their workers more productive. What I cannot say is, "There is no productivity."
There is a book that goes into deconstructing productivity. It's called "How to Survive in an Organization" by James Heaphey. It's based on a generation's worth of study on organizations like corporations.
A lawyer could make a very good case just based on her side of the story for the law being broken.
Against the coder who undid her work because he was rejected by a woman, that is classic retaliation pure and simple. Most cases like this that don't go to court settle in the Valley for $250k. It's a million at a minimum in the Valley if it does go to court.
As far as the wife goes, there was so much innuendo in the article that I wasn't sure what to conclude. Was the wife suggesting she hook up with her husband because a happy husband would make the former employee's situation better? If so, another classic open and shut case.
At most, this piece is just a literary exercise that provides no solutions for the imaginary problems it suggests.
I would definitely change my opinion if facts were pointed to of actual projects and persons.
To talk down the scope of lots of projects, I've always educated a client by saying if certain types of thinking were automated then we'd have to say we were creating AI and that the cost of the project would grow exponentially.
You are the lion and the resources of the company are the gazelle. It's time to feast!
It's really a good time to:
1) ask for a raise for more "effort"
2) ask for more budget
3) that new computer they've been holding out on.
Ya, you can ditch that 17" laptop from 2006. ;) Just ask!
We know that throwing resources into the game this late doesn't work, but it's good to have that extra budget for later just in case you wildly do succeed.
This just puts the problem somewhere else.
Now, the new problem is a follower becoming "a flawed" currency. People who try to bot likes will now bot followers to get more likes.
You mention that there isn't a better solution. IMHO, I disagree.
I think Github has figured out a way. They've been around 5 years and haven't fired anybody and nobody has quit.
Most firings are due to a job / job skill mismatch. At Github, they do a week long paid interview so both sides really know what they're getting into.
I don't work at Github, but am such a fan of their company.