1. -1

  2. 3

    This is a pretty blatant ad.

    At work, working on back-end microservices, this is pretty much solved by docker-compose and having sensible separations between services. Also I think if your one change implicates five or so services, something is very wrong.

    I can find the humor in a company named Windmills making a product called tilt though.

    1. 2

      “Say you’re making a code change that spans multiple services; that means that you need to go restart all those services…” eek! A reason to do microservices is to split up work between teams. It’s not a great reason, but there’s at least a pretty core assumption in the model that you’re working on one main thing at a time.

      1. 2

        This reads like an ad for tilt. Not sure what it does after reading this article and it seems those things it mentions that are bad could be automated (think ansible, shell, Capistrano etc).

        1. 1

          I can manage most of what seems promised by tilt through docker-compose and docker. What am I missing? The magic?

          1. 1

            I think Tilt is trying to specifically solve Kubernetes development.

            1. 3

              And Kubernetes in turn was supposed to solve container development/deployment.

              A more cynical person would find humor in this.

          2. 1

            I wish this article explained whatever the “magic” is rather than being what feels like an advertisement?