3 ms·
Zed's thesis is flawed. He set out to be famous--ostensibly because he didn't get enough respect in Ruby-land. It's not clear what his goal was, but now he's
by dasil003 16y ago
Zed's thesis is flawed. He set out to be famous--ostensibly because he didn't get enough respect in Ruby-land. It's not clear what his goal was, but now he's jumping to the conclusion that fame doesn't bypass bureaucratic red tape. However Zed wasn't satisfied with his small notoriety, and instead chose to accelerate it by deliberately becoming a flaming asshole writing vitriolic rants full of personal attacks.
I enjoyed Zed's rants, and I thought they were fairly insightful. I certainly never interpreted them as being completely out of line, or that Zed was a total asshole. He explicitly stated that he was testing the theory of being an internet blowhard to get attention. Fine.
But the problem is now he's famous for being a blowhard. He went from being moderately famous (and misunderstood) among the Ruby elite, to being widely famous for writing snarky articles. Well, that's obviously not going to get you past any technical interviews. Also, he decided to burn his bridges in the Ruby community, where I guarantee you he could have gotten plenty of jobs without an interview before. Nowadays, as someone who does a lot of hiring, I can tell you that I would think twice before hiring Zed for fear of what kind of drama he would bring to the team. That fear may be totally unfounded--I don't know him personally--but where before I knew Zed as "the guy who made Rails deployment viable", now I know him as "the guy who thinks he's god's gift to programming and hates a lot of shit."
Zed hasn't discovered anything about programmer fame, he just learned that internet-famous is worthless.
- earl 16y agoSadly, no. " Also, he decided to burn his bridges in the Ruby community, where I guarantee you he could have gotten plenty of jobs without an interview before." I think Zed made it pretty clear in the discussion around the "Rails is a ghetto" article that he did not, in fact, get any jobs period. My understanding is that the article was the outcome of his frustration at not reaping any rewards, particularly financial ones, for contributing a pretty important piece of technology to the rails stack.