13 ms·

I wrote most of the code the day it launched, and I had to get it done that day because I had to help the startups prepare their Demo Day pitches. Thanks for s

• elwell 13y ago
  > much of the development happens in the repl of the live site Wow, I guess that gives me an excuse when I'm too lazy to test on a dev server. "Well, PG live edits HN"
  • batoure 13y ago
    >"Well, PG live edits HN" But HN has a persistent bug where the next button on the first page expires and doesn't work. That's the difference between doing something for work and doing something for fun. The willingnes to tolerate malfunction is higher
    • bdcravens 13y ago
      > HN has a persistent bug where the next button on the first page expires and doesn't work. I don't think that's a bug, but a feature - a type of cache invalidation that forces you to refresh to ensure paging is accurate
      • deleted 13y ago
        [deleted]
      • vacri 13y ago
        There's the same 'feature' which works against insightful commentary. Spend too long crafting a response, get "unknown or expired link". Not particularly endorsing of a considered, pensive response.
      • tempestn 13y ago
        Surely there are better ways. For example, you keep track of which posts a user has already seen, and when they hit the next page button, show them the X most highly ranked posts that they haven't yet seen. Breaking the link is just the easiest way to deal with the problem.
  • gergles 13y ago
    He's also caused significant downtime by doing this, so this may not be a good lesson to take for your own sites.
    • pg 13y ago
      Actually I don't think any of the outages have been caused by this. The prospect does add an edge of excitement to programming though. Gamification for programmers!
      • rdl 13y ago
        There was one outage caused by a runaway which testing would have easily caught; I think about last year.
        • cperciva 13y ago
          Are you thinking of this outage from last month? https://news.ycombinator.com/item?id=7261591 https://news.ycombinator.com/item?id=7261591
          • rdl 13y ago
            There was something from >1y ago.
            • maxerickson 13y ago
              Probably this one: https://news.ycombinator.com/item?id=5239673 https://news.ycombinator.com/item?id=5239673 (I remembered "new user" so was able to get a search to work...)
              • pg 13y ago
                Good catch. But strictly speaking that wasn't doing development in the repl, but repairing data. The live server is the only place you can repair data on the live server.
• cmbaus 13y ago
  This is my all time favorite HN comment! For everyone who claims there is one true way to write successful software, it should be noted that one of the most popular (or least influential) sites frequented by developers was built on the live server using the REPL! Maybe PG is the exception that proves the rule, but damn that's awesome.
  • krapp 13y ago
    I think PG's company is the exception that proves the rule. It's still probably a bad idea.
    • cmbaus 13y ago
      Don't know. It has been shown to work. One of the major benefits touted by the proponents of Agile was that it modeled how successful software teams worked. Well here's a successful software team and this is how it works. For most teams it is probably a truly bad idea. But it shows there is more than one way to do it. Update: The more I think about it, maybe this isn't so crazy. Wasn't Erlang built to work this way, so engineers could modify a telecom switch without taking it offline? As systems get gigantic it gets very difficult to have a staging environment that mimics the live site.
• Natsu 13y ago
  "We tend to think by writing code." That should get added to a quote collection somewhere :)