822 karma · joined February 21, 2011
It was never refuted on the interview, and I don't see it refuted in this comment thread anywhere. Is this actually true?
I think there's a better explanation that is linked to the enforcement of situations such as "someone googles Pirate Bay and gets a link to the site". SOPA puts Google at fault for this, and I assume the enforcement mechanism could very much harm a US company (Google). Unfortunately, time ran out on the segment right as they were getting to this point.
The NBC exec successfully skated around any scenario that may happen in which a US company gets punished due to SOPA. At the very end of the interview, the talk was getting there ("So Google HAS to take Pirate Bay down from search. What happens if it doesn't?") but the segment ended.
We need someone to get out there and clearly enumerate the scenarios in which generally law-abiding US companies can get burned by SOPA. This was not accomplished in the interview.
Even better than phone calls would be the emergence of a non-SOPA supporting Democrat running against Senator Feinstein. I'm sure the prospect of losing Northern California to a challenger would get her attention.
- has experience working in the early stages of a venture-backed startup
- went to one of the top schools in the world, such as Stanford, MIT, Harvard, etc
- has an extensive personal portfolio of software projects on which they contributed
My point is that Silicon Valley "works" because it has lots of people that meet 2 or 3 of these bullet points. There is no place in the world that really comes close.
Nobody is objecting that you can surely hire people cheaper in other countries, but for small companies the cheapest labor source is almost never the winner. It's far more important to have the very best engineers.
Now, you might say "the company that fires all the blond haired people will eventually die at the hands of a company that gains an advantage by accepting blond haired people." True, but it's a slow bleed, and that certainly doesn't help the blond haired people who were arbitrarily fired.
In case you're skeptical, all this and more can be observed in the case of US black people up until the civil rights era.
IMHO, Silicon Valley works because it houses a hugely disproportionate amount of the very best engineers, and from my experience the top .1% or so of engineers open up possibilities that otherwise simply aren't there.
Yes, the capital is here, but I think that's an effect and not a cause. If you took Facebook and started it in any other place in 2004 (with just a handful of exceptions) with exactly the same access to funds I highly doubt it ends up as it is today.
Where I would get scared is if I looked at code that was 2 years old and I couldn't distinguish it from code I would write today. That to me would be a clear sign that I am not improving.
Employees: 1
He's been doing this for almost a year and hasn't hired anyone. Sounds about right.
Also, the website is taking 20s to serve any page. Maybe he should spend less time blogging about how awesome he is and how everyone sucks, and instead build a website that can handle a surge of traffic.
1) You are a self-important douche who writes lengthy blog posts on all the reasons you deem people unworthy of working with you.
The proof is in the pudding - every highly successful, well admired web company you can think of employs the vast majority of its engineers onsite, and those that are offsite are not core contributors. To claim that working in an office is "outmoded" is ludicrous when there has yet to be a successful case that succeeded with a team that is mostly remote. And no, 37signals and its dozen employees don't count as a successful case of remote teams. I'm talking about a venture funded company with dozens/hundreds of engineers.
Also, many of the things you are talking about are red flags that would cause me not to hire an engineer (FWIW I'm a lead engineer). If I'm paying you a good salary to be on my team, I don't want to structure our work arrangement around letting you work on various side projects. We pay well, we expect a lot, and you should deliver as such. And I have consistently found the only way to make that happen is to enforce physically spending the majority of your time with the rest of the team.
It seems to start with the fact that many engineers think 100% of their job is coding, and therefore they can get "more" work done when working remotely. This is absolutely dead wrong. Engineers also should be accomplishing the following in order to maximize overall productivity:
- teaching other engineers
- learning from other engineers
- coordinating engineering tasks to minimize duplication
- doing what is necessary to ensure the software is what is needed
- communicating with others any insights that may be had while developing
- working with other departments to make sure everything is in place to build whatever it is you're building.
This is just what I can come up with off the top of my head in 2 minutes, and each of these things takes a significant hit when the engineer is working remotely. Any engineer I would want to hire has quite a bit more to offer than coding skills, and as soon as you require more than a basic automaton blindly building a product exactly to spec, you need human interaction with that person to maximize potential. We already learned this lesson a few years ago with the total failure of "all software can be outsourced to India!" I don't see why we need to learn this again.
But at the same time, some of the classes had very difficult subject matter and the professors were actually interested in teaching students instead of torturing them. So it wasn't totally a bad experience.
I guess there is some value in having these online classes because they motivate professors to make their subject matter more palatable. I just don't want my degree devalued by people who aren't as astute as yourself when it comes to the gap between the online courses and those taken by Stanford students.
My worry, which is similar to the worry of the student in the linked post, is that these lectures may be devaluing the in-person versions of the course. CS 229 was one of the top 5 hardest classes I have ever taken. I would rather not someone else take it via a dumbed down online lecture and say "I did that too! It wasn't so bad!"
Lots have companies have tried to beat the iPhone/iPad. Nobody has even come close. This guy's whole worldview centers around the fact that since he worked at Amazon, all their engineers are clearly the best. And if that engineering team releases a bad product it's clearly a reflection on someone other than the engineering team.
What is far more likely is that Amazon's engineers weren't going to approach the iPad no matter how hard they tried or how long they worked. It's nothing to be ashamed of - they have lots of great company in this regard.
IMHO, this falls into the category of "it's much easier to criticize someone else's design decisions than to make your own." How about you build an OS over the course of 15 years and then I can pick it apart and write hyperbolic rants about all the design details that annoy me?