Skip to content
  • Home Home Home, current page.
  • Moments Moments Moments, current page.

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @
  • Language: English
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English UK
    • Español
    • Filipino
    • Français
    • Hrvatski
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Ελληνικά
    • Български език
    • Русский
    • Српски
    • Українська мова
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Have an account? Log in
    Have an account?
    · Forgot password?

    New to Twitter?
    Sign up
BrandonBloom's profile
Brandon Bloom
Brandon Bloom
Brandon Bloom
@BrandonBloom

Tweets

Brandon Bloom

@BrandonBloom

CTO of @LegalpadIO

Seattle, WA
brandonbloom.name
Joined May 2008

Tweets

  • © 2018 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Cookies
  • Ads info
Dismiss
Previous
Next

Go to a person's profile

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @

Promote this Tweet

Block

  • Tweet with a location

    You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more

    Your lists

    Create a new list


    Under 100 characters, optional

    Privacy

    Copy link to Tweet

    Embed this Tweet

    Embed this Video

    Add this Tweet to your website by copying the code below. Learn more

    Add this video to your website by copying the code below. Learn more

    Hmm, there was a problem reaching the server.

    By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.

    Preview

    Why you're seeing this ad

    Log in to Twitter

    · Forgot password?
    Don't have an account? Sign up »

    Sign up for Twitter

    Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

    Sign up
    Have an account? Log in »

    Two-way (sending and receiving) short codes:

    Country Code For customers of
    United States 40404 (any)
    Canada 21212 (any)
    United Kingdom 86444 Vodafone, Orange, 3, O2
    Brazil 40404 Nextel, TIM
    Haiti 40404 Digicel, Voila
    Ireland 51210 Vodafone, O2
    India 53000 Bharti Airtel, Videocon, Reliance
    Indonesia 89887 AXIS, 3, Telkomsel, Indosat, XL Axiata
    Italy 4880804 Wind
    3424486444 Vodafone
    » See SMS short codes for other countries

    Confirmation

     

    Welcome home!

    This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.

    Tweets not working for you?

    Hover over the profile pic and click the Following button to unfollow any account.

    Say a lot with a little

    When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.

    Spread the word

    The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.

    Join the conversation

    Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.

    Learn the latest

    Get instant insight into what people are talking about now.

    Get more of what you love

    Follow more accounts to get instant updates about topics you care about.

    Find what's happening

    See the latest conversations about any topic instantly.

    Never miss a Moment

    Catch up instantly on the best stories happening as they unfold.

    1. Tim Pote‏ @potetm Oct 24

      Has anyone gone months without introducing observed bugs into production? To what do you attribute your defect-free code?

      3 replies 0 retweets 2 likes
    2. Brandon Bloom‏ @BrandonBloom Oct 24
      Replying to @potetm

      Yes: Simplicity. I built a real-time video service that, after an extended shadow-traffic launch, ran for nearly a year with only one hiccup before I stopped paying attention to it. Extreme simplicity is what enabled that stability.

      2 replies 2 retweets 9 likes
    3. Tim Pote‏ @potetm Oct 24
      Replying to @BrandonBloom

      In other words, you methodically broke the system into parts, each of which you understood in their entirety?

      2 replies 0 retweets 0 likes
    4. William Hilton‏ @wmhilton Oct 24
      Replying to @potetm @BrandonBloom

      I don't think that's sufficient. Complicated messes can be composed from elegant simple parts. The composition itself also has to be extremely simple.

      1 reply 0 retweets 3 likes
    5. William Hilton‏ @wmhilton Oct 24
      Replying to @wmhilton @potetm @BrandonBloom

      Another possibility (which I think @BrandonBloom hinted at, but I'm not sure) is you simply don't touch it once it's in production. A simple microservice with a single responsibility could run for years and you never need to change it.

      2 replies 0 retweets 1 like
    6. William Hilton‏ @wmhilton Oct 24
      Replying to @wmhilton @potetm @BrandonBloom

      I don't know how you could frequently change code without introducing bugs. 😔

      1 reply 0 retweets 0 likes
    7. Tim Pote‏ @potetm Oct 24
      Replying to @wmhilton @BrandonBloom

      Is frequently changing code desirable?

      1 reply 0 retweets 0 likes
      Brandon Bloom‏ @BrandonBloom Oct 24
      Replying to @potetm @wmhilton

      Maybe not, but I think it's a business imperative.

      12:01 PM - 24 Oct 2018
      • 1 Like
      • William Hilton
      2 replies 0 retweets 1 like
        1. Tim Pote‏ @potetm Oct 24
          Replying to @BrandonBloom @wmhilton

          True enough I suppose. I've often left subsystems untouched for months or years. Doesn't negate all of the changes that DID occur in other places.

          0 replies 0 retweets 1 like
          Thanks. Twitter will use this to make your timeline better. Undo
          Undo
        1. New conversation
        2.  📶‏ @coreload Oct 24
          Replying to @BrandonBloom @potetm @wmhilton

          Yes. Production is a great place to find out what works for people. Frequent changes gets new things into their hands sooner and minimizes the "distance" btw what was there and what now is there... Bugs tend to correlate to lines of code. Smaller releases, fewer if any bugs per.

          2 replies 0 retweets 1 like
        3. Tim Pote‏ @potetm Oct 24
          Replying to @coreload @BrandonBloom @wmhilton

          "Bugs tend to correlate to lines of code." What I'm talking about (and what Brandon spoke about) stands in defiance of this statement. On the one hand, it's obviously true. On the other hand, there's something not-obvious that appears to make it untrue.

          1 reply 0 retweets 1 like
        4. Tim Pote‏ @potetm Oct 24
          Replying to @potetm @coreload and

          Well... perhaps not untrue. But something out there can push your bug/LoC ratio to zero. I agree w/ the general sentiment btw. Faster feedback cycles tend to be very useful.

          1 reply 0 retweets 1 like
        5.  📶‏ @coreload Oct 24
          Replying to @potetm @BrandonBloom @wmhilton

          Bugs per line of code has been demonstrated over decades, over programming languages (one reason to use succinct programming languages), across teams. There are exceptions, but these would be exceptions to the rule.

          3 replies 0 retweets 0 likes
        6. Tim Pote‏ @potetm Oct 24
          Replying to @coreload @BrandonBloom @wmhilton

          The fact that they're exceptions make them no less untrue! :D Au contraire, these are, by definition, the remarkable cases that are worth studying closer!

          1 reply 0 retweets 1 like
        7.  📶‏ @coreload Oct 24
          Replying to @potetm @BrandonBloom @wmhilton

          Definitely study them. Just don't rely on them until you've demonstrated a repeated benefit. They're no less true but they are more rare.

          1 reply 0 retweets 0 likes
        8. Tim Pote‏ @potetm Oct 24
          Replying to @coreload @BrandonBloom @wmhilton

          Tim Pote Retweeted Hillelraiser II: hellbound

          Ah, just the tweet I was looking for.https://twitter.com/Hillelogram/status/989354024297291776 …

          Tim Pote added,

          Hillelraiser II: hellbound @Hillelogram
          Figure many of my followers would be interested in hearing about Cleanroom, because it's right at the intersection of software anthropology, software correctness, and empirical engineering. It works, we know it works, and yet nobody uses it. In this thread, I'll badly explain it. https://twitter.com/yminsky/status/989269001216970752 …
          Show this thread
          1 reply 0 retweets 0 likes
        9.  📶‏ @coreload Oct 24
          Replying to @potetm @BrandonBloom @wmhilton

          Sure. Also cost per line of code is very large so the benefits of zero defects must be corresponding great. The domains I work in are much more exploratory. Nobody knows what they want for sure, so we iterate and discover the value together, continuously.

          2 replies 0 retweets 0 likes
        10. 2 more replies

      Loading seems to be taking a while.

      Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

        Promoted Tweet

        false

        • © 2018 Twitter
        • About
        • Help Center
        • Terms
        • Privacy policy
        • Cookies
        • Ads info