Login
You're viewing the front-end.social public feed.
  • Wolf480plwolf480pl@mstdn.io
    Oct 25, 2026, 2:57 PM

    @joshbressers what if we split the pile into multiple piles separated by nonflammable areas, and then preventatively burned down each pile every so often?

    How would that work in software?

    How does fire spread from piece of software A to B?
    I guess
    - B depends on A (or vendors it)
    - B is built using A
    - A happens to be installed on B's developer's workstation / CI server / source repo server

    So we'd need completely separate self-hosted software ecosystems...

    ok maybe not a good idea after all

    💬 1🔄 0⭐ 1

Replies

  • Ian McDowallimcdowall@mastodon.social
    Oct 25, 2026, 5:20 PM

    @wolf480pl @joshbressers
    Maybe the separation could be really well-defined and secure interfaces? But then would burning down separate piles take the form of aggressive testing in isolation? Or replacing with alternatives with the same interfaces?

    Back in the day, I liked the idea of really well defined interfaces and replaceable components but sloppier interfaces and more fuzzy dependencies are cheaper 😔 in most cases.

    💬 1🔄 0⭐ 1
  • Wolf480plwolf480pl@mstdn.io
    Oct 25, 2026, 5:22 PM

    @imcdowall @joshbressers
    well, by burning it all down I meant like, having it be totally pwned by a malicious actor, discarding that whole software stack, treating all machines that ran it as compromised, and starting a new one

    💬 1🔄 0⭐ 1
  • 💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 1