• 0 Posts
  • 24 Comments
Joined 2 years ago
Cake day: June 8th, 2023
  • fayoh@sopuli.xyztoProgrammer Humor@programming.dev•Slapping on a `.expect` is also error handling!
    8·
    2 months ago

    The crash early, crash often approach of Erlang has made for some amazingly resilient systems.

    One time on a project I was working on, some horribly broken code was merged (nobody in the team had even heard of reviewing code). As soon as a specific call was made, it was executed once and then the thread crashed. The only way we noticed was that response times increased with load. All data and behavior was still correct. Whole nodes could go down and all you notice is a dip in performance until it comes back online.

    Of course it requires special care in designing. Everything runs in stateless server threads with supervisors restarting them as needed. This in turn requires some language support, like lightweight threads. Our application would happily run tens of thousands of threads on an ancient sparkstation.

  • fayoh@sopuli.xyztoProgrammer Humor@programming.dev•When you look at code you wrote last year
    29·
    7 months ago

    Me at a previous workplace.

    -This is a piece of shit, who is the code owner of this module.

    • Ah, it’s me (“inheriting” code ownership when someone left was common)

    • Who did this change

    • Ah, it was me

    • Surely I just made a minor change to this line here, who wrote the function.

    • it was me, it was me all the way down

    Fits the general theme of the thread as it was not giving any trouble for a year before being found.