• AeonFelis@lemmy.world
    link
    fedilink
    arrow-up
    24
    arrow-down
    1
    ·
    10 hours ago

    Thought leaders spent the last couple of decades propaganding that features-per-week is the only metric to optimize, and that if your software has any bit of efficiency or quality in it that’s a clear indicator for a lost opportunity to sacrifice it on the alter of code churning.

    The result is not “amazing”. I’d be more amazed had it turned out differently.

    • SanicHegehog@lemmy.world
      link
      fedilink
      arrow-up
      10
      ·
      6 hours ago

      Fucking “features”. Can’t software just be finished? I bought App. App does exactly what I need it to do. Leave. It. Alone.

    • ChickenLadyLovesLife@lemmy.world
      link
      fedilink
      English
      arrow-up
      14
      arrow-down
      1
      ·
      10 hours ago

      It’s kind of funny how eagerly we programmers criticize “premature optimization”, when often optimization is not premature at all but truly necessary. A related problem is that programmers often have top-of-the-line gear, so code that works acceptably well on their equipment is hideously slow when running on normal people’s machines. When I was managing my team, I would encourage people to develop on out-of-date devices (or at least test their code out on them once in a while).