Joel notes that you can't intelligently criticize a software ecosystem (the Windows ecosystem, the Linux one) until you really know it. You don't really know it until you've spent years learning the tiny details that rarely but importantly affect your job. And I'll add to Joel's point that by the time you really know it, you can no longer criticize at all: you're too deeply bought in (see Influence for commitment and consistency) and too habituated to one way of doing things for any other way to seem at all reasonable.
Subscribe to:
Post Comments (Atom)
Blog Archive
-
▼
2002
(182)
-
▼
December
(24)
- Cory Doctorow links to an article about saving the...
- Is it really so easy to create a hoax that, when s...
- Volokh posts on water privatization, and a reader ...
- I'm back from vacation.
- Good grief. Matt Smith complains that "Calculated...
- More info on risk, particularly traffic related. F...
- I frequently talk to people about risk assessment ...
- Joel Spolsky, aka "Joel on Software", has a fun ra...
- In the NYT editorial pages today, Nicholas D. Kris...
- In addition to several rankings of countries' econ...
- This NYT editorial by Harvard History professor Li...
- If I can paraphrase Innocents Abroad: he writes th...
- If your breasts are larger than DD, read Cat's sit...
- Volokh says that Fumento says (in Reason Online) t...
- I never heard about this recently deceased police ...
- First and second generation immigrants are quite d...
- Maybe this is why I don't like UDDI -- as Sean McG...
- You can now examine wine with a magnetic resonance...
- I just found a slightly dated paper on AOL interop...
- Presence standards for buddy lists (seeing who's o...
- A bunch of bloggers I read occasionally (often lin...
- Google ZeitGeist is still there, though it's getti...
- Chris asked me about mercury levels, how dangerous...
- Now this would be a truly useful genetic modificat...
-
▼
December
(24)
No comments:
Post a Comment