• MashedTech@lemmy.worldOP
      link
      fedilink
      arrow-up
      22
      ·
      3 months ago

      That’s true, never make impactful decisions in a rush. But I feel like the last panel only works in the current context of escalating code changes

    • frezik@midwest.social
      link
      fedilink
      arrow-up
      4
      ·
      3 months ago

      Valid, but if it needs to be decided, then there should be something concrete scheduled to do that followup when people are back in.

    • _NoName_@lemmy.ml
      link
      fedilink
      arrow-up
      10
      ·
      3 months ago

      I think this is coming from a “plugins enshittify projects” mentality where the assumptions are:

      • code bases should be as succinct and stable as possible.
      • plugins add large amounts of unused code and obfuscate many granular aspects of program execution, increasing debug and research time.

      Seems that the author views that the above devs chose to use plugins instead of writing their own code and shot themselves in the foot by doing so. The final portion seems to suggest that the person pushing all these changes then bobs out before any of the problems caused by these changes actually get solved.