This whole Sinofsky drama is a really good lesson for everyone. Nobody is indispensible. Microsoft will be fine without Sinofsky.
282 karma · joined July 29, 2008
This whole Sinofsky drama is a really good lesson for everyone. Nobody is indispensible. Microsoft will be fine without Sinofsky.
This also goes hand-in-hand with "Everyone can be a programmer" mantra that everyone likes to repeat. Go teach pointers to 20-year olds and you'll realize how most people can't be programmers.
I don't understand where this culture is coming from. I definitely can't fix my car; when I see my mechanic, he doesn't tell me how I should go learn how to fix my car. I'm confident he's much better at fixing my car than I am. The same is true with other professions -- lawyers don't tell clients to go interpret laws on their own and dentists don't tell people to go remove teeth on their own. What is it about our community that we ingrained into our youth that "writing code" is the thing that everybody must do?
You realize that the Waterloo CS school is called the "David Cheriton CS School", yeah? Take that for "humble" :-)
How would Google look like if they were to release GMail using an "iterate faster" mentality? Your INBOX just got accidentally erased because of our UI bug. Oops sorry, we'll release a fix in 5 minutes.
How about Windows? or a generic OS driver? Oops, your machine is just blue-screening now. Don't worry, we'll just release an update in an hour. It'll certainly make your OS drivers very reliable.
Don't confuse the Web 2.0 "iterate faster" era with "the right way". Building "iterate faster" systems is easy. Building systems "the right way" is hard.
To this day, I am still shocked as to how many devs have no clue on what I'm talking about, yet they are in charge of Internet-scale systems. Here's a list of symptoms, I've heard over the years:
- I'll put something quick together.
- I implemented Paxos last night.
- I found an optimization in the two-phase commit protocol.
In my opinion, being expert means becoming humble and doubtful about your code when implementing large-scale systems. If your code runs on thousands of machines and serves 100K+ people and you think you rock as a developer/architect then you're doing something wrong.
Facebook doesn't get this. Look at their systems. They barely work. Good thing it doesn't matter. Yet. But it will eventually.
Amazon gets a little of this. Bringing Werner showed signs that they started to get it. They are still in this mix where a small group of people gets it and continues to bring in experts and push amazing things out. We'll see how long this will last.
Microsoft clearly doesn't get it. But that's ok, because they have no Internet-scale systems anyway. They built MSR which is capable of building such systems, but they make sure MSR remains isolated from their code. MSR seems happy to have no role in the company and to continue to publish amazing research.
1. Somebody discovered a security vulnerability in the implementation of a network protocol (i.e., a bug). The bug can be exploited remotely apparently. Which means that somebody from far away can break into your machine if your software has this bug.
2. This was used by someone else to push forward their agenda. In particular, their point is that newer dynamic root of trust trusted technologies are better than older static root of trust technologies. The goal of these technologies is to make a piece of code execute securely (i.e., without being compromised or modified by an attacker). Static root of trust can make a piece of code execute securely only by trusting the entire software stack from boot time until the execution of the piece of code. Dynamic root of trust bypasses this entire software stack -- it allows you to just verify that the piece of code hasn't been modified before it's being executed.
3. Now, the bug from step #1 can (in theory) be used for someone to "break" into the persistent storage of the NIC and compromise the NIC "forever" by changing its firmware to a "bad" firmware. This won't be caught by the static root of trust technology because such technologies do not typically check the firmware of a NIC card at boottime. And thus, in theory, the dynamic root of trust is "better" because it doesn't rely on making sure that the entire software stack remains uncompromised.
Now .. my opinions.
a. Remote vulnerabilities are very problematic because they lead to remote exploits. The lesson here -- get very experienced/senior/skeptical designers to implement networking protocols. Here's where it's worth hiring the smart guy. Implementing a new protocol in C from scratch is crazy. I'd fire this guy if he worked for me.
b. Dynamic root of trust is better than static root of trust on paper. In practice, dynamic root of trust is very hard to implement in a way that stays secure while doing something useful. When executing in "secure" mode with dynamic root of trust, you cannot use interrupts which basically means that's almost impossible to do anything useful (like sending or receiving a network packet).
1. Pollution 2. Traffic 3. Taxes
I'll stop here since I don't want to get all worked up.