3 ms·

Hey folks, author here. I'd love feedback – I'm also happy to answer any questions and/or debate!

• jaksawesome 6y ago
  Have a mirror? Looks like site is already down.
  • AlexDReeve 6y ago
    Ugh, I'm on it!
    • simonw 6y ago
      I love Cloudflare for this kind of thing - it's free (at least for blog-sized sites), it's reasonably easy to configure and it automatically takes effect when you get an unexpected surge in traffic.
      • AlexDReeve 6y ago
        Thanks for the suggestion! I'm on Digital Ocean; I had to do a quick droplet upgrade to avoid the "hug of death" – I'll keep Cloudflare in mind!
  • timsneath 6y ago
    Principle #23: plan for unexpected scale :)
    • AlexDReeve 6y ago
      Too true! =(
• goofballlogic 6y ago
  One of the hard things to get right when writing one of these "Tips for being a great X" is that they're usually written from the point of view of someone who is a clear leader in their field. With some exceptions, the people who write this sort of article have the confidence (or presumption) to see themselves as ahead of the pack. It is rare to see articles like this written by teams of people who, in cooperation, balance tasks like product management, architecture, engineering, operations and customer success between them. And yet that is, imo, the best way to do it. When I read and article like this advising the reader to do X to "their team" (in this case let your team get on with work), it falls into this category where the "how to be a great X" applies to a particular structure - where "X" is somehow in control of the rest of the team, rather than an equal participant.