6 ms·
I read Richard Gabriel's "Worse Is Better" essay in my first month hired as a professional programmer, that was almost 12 years ago. Since that time the lessons
by paganel 10y ago
I read Richard Gabriel's "Worse Is Better" essay in my first month hired as a professional programmer, that was almost 12 years ago. Since that time the lessons of that essay have only increased in significance for me, with this FB story as additional proof.
Their back-end code might be bollocks, and I can certainly believe that judging by how sluggish their FB app feels on my phone, but the fact is that they've conquered the Internet (together with Google and a couple of other companies). It's a fact that I personally hate, but they're still winners in the end.
- aaron-lebo 10y agoBut it's not better, it is worse as clearly put forward by this article. ;) We shouldn't attribute Facebook's success to poor quality code, unless we really believe that 429 people working that that slow sluggish app is productive. Do you? Maybe Facebook would be in a better situation than they are if they had a firm foundation? What happens when a competitor comes along and knocks on their door? That mess of code becomes an anchor. They succeeded not because "worse is better" but because ...they succeeded, maybe because they had the greatest social network in the world to expand within, or because of some other reason we don't know. But they didn't succeed because of worse is better, they succeeded in spite of it.
- paganel 10y ago> Do you? It's written between the article's lines, so to speak, but it seems like the bad code quality was generated in part by FB moving at a very fast pace. I think they wouldn't have been as successful as they are had they chosen a slower path with more "correct" code and architecture. > What happens when a competitor comes along and knocks on their door? They successfully managed to "eat" and integrate both Instagram and WahtsApp, both worthy contenders at the time, and they're now on their way to stealing Snap's lunch, so they've proved to be pretty resilient on this front. Not to forget how they successfully kept Google+ in check.
- jheriko 10y agohow would that success have been different if they had used different engineering practices? a big part of their success was delivering results... if they hadn't quickly crapped everything out of the door, how would facebook look today?
- jaredklewis 10y agoNo one is actually arguing that worse is better. It's just a catchy title. A more accurate title would be "worse is faster than better, and being fast but mediocre is better than being slow and amazing." Worse is better makes the observation that doing right thing slows you down. Often, an ok solution is much quicker to get finished than a great one. And it concludes that the projects that prioritize getting stuff done over code quality will suceeed. Would facebook be as successful as it is today if it had taken longer to ship features, but maintained higher code quality? Who knows. But the intuition in worse is better, which matches with my own experiences, is that making that trade off would have cost Facebook, as other faster moving projects closed the gap.
- aaron-lebo 10y agoAs you said, I just don't think anyone can know that alternate history. It's very possible that a better architecture would have allowed them to move quicker and make more changes without breaking as much stuff. It's possible considering features before haphazardly implementing them would be beneficial overall. Nobody can really know that, and to apply intuition to what is an extreme outlier seems off.
- polack 10y agoI agree with you that it's sometimes good to focus on getting things out the door fast instead of the code quality behind it. But surly there must be a point when the pendulum swings back and you should switch focus to quality. I would argue that Facebook have definitely reached the point where they own so much of the market and with their infinite resources they should be able to ship things with good code quality. Sooner or later the costs of supporting all that crappy software will make a dent even in Facebooks chest of gold.
- K0SM0S 10y ago> Sooner or later the costs of supporting all that crappy software will make a dent even in Facebooks chest of gold. I would think that's most engineers gut feeling, at least that's mine too. But reality is vastly different, because market shares are not won solely on quality (it matters, but rarely is the penultimate factor), and software itself isn't always the core product (i.e. it's a medium). We tend to think that success for big tech requires quality code, like Apple and Google produce, but think about Microsoft's history... what a pure software company could get away with. The major reason in that case is probably its quasi-monopoly on several key markets; and that's I wager exactly what plays in favor of Facebook's apps, regardless of the quality of their code we emphasize so much around here: there is no getting access to Facebook without using their apps (webapp included of course). Period. So the question never was "oh, is Fb(the app) good enough?", the question is "do I want to use facebook or not?", and if yes, proceed to use app. Ultimately that's because Fb is providing a service, a social network, and software is just the means, the medium, the tool. It never was about the app, the code, it's about what these enable in the real world --from super-secret groups to circlejerking around fake news and what-have-you-with-your-cats-lulz. We just have to look at a slew of industries that just like Facebook provide a service through software ranging from OK to abysmally painful (like, 80% of set top boxes and TV menus and VHS/DVD UIs... car electronics... ATMs...) I always find the same two culprits: a purely functional design (does the job, sometimes buggily, period) or a situation of monopoly (deal with it, customer!). Or both. Quality-of-life features and user experience are vastly alien to some otherwise pretty tasteful industries, design-wise (the joy of powering up a $10K receiver in the late 90's, hook it up to the TV to be greeted with giant white fonts on a 64x64 blue grid --and that thing does 7.1 DVD yada yada?). So while I tend to agree with you at first and would love to live in a world where that's true (yay engineers all over), I think that's not the way markets operate. Do we enjoy setting the time on most LCD clocks? No. Because that never was the intent, it was purely meant to do the job of letting you set the time correctly, if frustratingly. In much the same way I use software every day that fights against me, but I get to win the function that I seek. There are games like that too, where the reward is part mastering the content and part besting the UI. On a side related note, I don't think the service that would (will, given enough time...) eventually best Facebook would do so on quality or performance or anything of the sort; I think it will be based on a paradigm shift (another way, era of doing 'social stuff'). Otherwise it's pretty locked for this cycle, even if Fb's apps were really bad to use. There's just no alternative present or in sight, and 1.something billion users is a pretty tough lock on a market.
- onewaystreet 10y agoAgility trumps code quality. Stability can be addressed downstream (which Facebook does with heavy testing and rollouts of changes). Code quality problems or not, Facebook has been more stable than its competitors (MySpace, Twitter, etc.) and faster at pushing out changes.
- collyw 10y agoIs it more stable than those two? I can't see the point in Twitter (neither could a number of my colleagues when it was mentioned at a dinner a couple of weeks ago, none of them used it). MySpace was a genuine competitor, but allowing teenagers to style their own HTML made for some horrendous pages. Facebook had a nice clean interface, as well as network effects. I was signed up to a similar service at the time - HighFive I think it was called, but the network effect was what snowballed with Facebook and led to its success. At the time I didn't see either one being better or more stable than the other.
- jasode 10y ago>I read Richard Gabriel's "Worse Is Better" essay Fyi to help set the record straight... RG's "Worse Is Better" is not shorthand for "worse quality" is better than "better quality". Richard Gabriel was trolling readers with the word "worse" for comical effect. His essay is: "simpler with less features" wins in the marketplace of ideas more than "complex". His observation isn't about "quality". That said, there is another meme with the exact same 3 words called "worse is better" which does stand for "worse _quality_ is better than better _quality_" but that's not related to RG. It's just the more common interpretation of those 3 words -- especially for 99% of people that are not familiar with RG's original essay. tldr: Richard Gabriel trolled people so hard that "worse is better" has taken on a life of its own divorced from his original thesis
- coldtea 10y ago>Richard Gabriel was trolling readers with the word "worse" for comical effect. His essay is: "simpler with less features" wins in the marketplace of ideas more than "complex". His observation isn't about "quality". Only it IS about quality. The simpler and with less features" examples he gave were examples of broken implementations, that will succesful in getting "out of the door" and having viral acceptance, have resulted on lots of issues, lost man-months, and piles upon piles of hacks. That's regardless of what Gabriels himself thought he was saying. And while "getting out of the door" pronto might be good for a product, it's not good for infrastructure software.
- emodendroket 10y ago> Richard Gabriel was trolling readers with the word "worse" for comical effect. His essay is: "simpler with less features" wins in the marketplace of ideas more than "complex". His observation isn't about "quality". I have to say that reading the thing again I don't really think that's accurate, since he also talks about sacrificing correctness for the sake of ease of implementation.
- jasode 10y ago>I don't really think that's accurate, since he also talks about sacrificing correctness RG's use of "correct" doesn't mean that it's ok for a program to return "2+2=5" which is "better" than "2+2=4". To refer back to the original essay[1], RG's use of words like "correct" and the "Right Thing" requires careful reading because he's deliberately abusing those terms to burnish the opposing side's philosophy. He's playing with the adjectives "worse/correct/right" to present both sides of the New Jersey vs MIT philosophy. RG says that MIT approach of "backing out of the system routine" is the "correct" way for argument's purposes. It doesn't mean it's The Universally True Correct Way. RG doesn't state it explicitly but the The New Jersey approach of adding user code to test for a failure is also "correct". There are 2 competing semantics of "correct". His observation is that the one with the simpler implementation will spread. Maybe another analogous example would be clearer. Suppose a C++ programmer would label the "~destructors()" as the "correct" approach to clean up code. No extra user code has to be written to do housekeeping after each object goes out of scope. However, a C programmer disagrees and "destructors/constructors" are complicated with "spooky action at a distance". They'd rather write explicit wrapper functions called "cleanup()". Both the C and C++ camps are disagreeing about which "correctness" is better. In this case, RG would award the "correct" label to the C++ philosophy for the sake of a creating a provocative essay. (It's not an exact analogy because the more complicated C++ programming has survived along side the simpler C for decades.) Whether one prefers MIT over New Jersey, it doesn't change the fact that RG is not saying that "low quality is better than high quality". [1] https://www.dreamsongs.com/RiseOfWorseIsBetter.html https://www.dreamsongs.com/RiseOfWorseIsBetter.html
- ebbv 10y agoYou're making an implicit assumption in this comment; that Facebook is in an optimal position and every decision they made contributed to that optimal position in a positive way and so any change is for the worse. But what if they aren't in an optimal position? What if having a higher quality code base all along would have let them dominate social media more and faster, and perhaps be more successful in areas they have stumbled in the past? A lot of people (especially non-technical folks and inexperienced coders) seem to think that code quality comes at a cost and that a bad code base full of technical debt is just a side effect of fast iteration and the cost of being quick to market. I say that's crap. A higher quality codebase with less technical debt actually improves speed tremendously because it lets you iterate faster with fewer rewrites down the road and it will be more stable and result in fewer distractions from having to put out fires with unforeseen bugs making it into production. A sloppy codebase with technical debt is much more costly on your ability to go to market and add features and iterate.
- emodendroket 10y ago> But what if they aren't in an optimal position? What if having a higher quality code base all along would have let them dominate social media more and faster, and perhaps be more successful in areas they have stumbled in the past? Well, I don't know. What if spending so much time on quality would have led to it never catching on? It is curious that the world is full of compromises like Unix, QWERTY, C, VHS, etc., all of which had arguably superior competitors that failed to catch on.
- ebbv 10y ago> What if spending so much time on quality Your reply includes the very fallacy that I mention in my comment that you're replying to. Namely that better quality code requires more time. Again, I say, that's not really the case. If you write better code you will spend less time debugging, adding features and iterating in the future, and I would argue it takes less time to write better code once you're in the habit of it. But of course any number of things are possible, they could have written better code and failed. They could have written even worse code than they did and failed. Who knows. My point wasn't "Facebook should have written better code and then Zuckerberg would have another $10 billion." My point was that the comment I was replying to was based on some assumptions that, for me, aren't true. > It is curious that the world is full of compromises like Unix, QWERTY, C, VHS, etc., all of which had arguably superior competitors that failed to catch on. But it's the arguably superior that matters here. For each of them there are circumstantial reasons why they beat out competitors, and it's usually not really because of the mythical "worse wins" baloney. In reality there's usually a number of reasons that combine together for a given result, and that's certainly the case with, for example, VHS vs. Beta. Costs of tapes and players, Sony's tight control of Beta, camcorders, etc. all combine together. Anyway, we're way off on a tangent now. My point was it's a fallacy that writing worse code is a short cut. It's like driving badly vs. driving well. You're still going to the same place on the same roads.