• August27th@lemmy.ca
      link
      fedilink
      arrow-up
      20
      arrow-down
      1
      ·
      1 year ago

      Nailed it. Things have changed to allow cheaper (interpretable in several ways) developers to create “good enough” software as quickly as possible. If that involves inefficient frameworks, technology, and practices that unlock this, then so be it; if the “best” code is the code that makes money, and money is what corporations prioritize above all else, and there is a way to do that quicker and cheaper, the outcome is obvious and now ubiquitous. Furthermore, if nobody at the top cares, why should anyone on the ground care? The problem compounds.

      Priorities are fucked.

    • TBi@lemmy.world
      link
      fedilink
      arrow-up
      8
      arrow-down
      2
      ·
      1 year ago

      I wouldn’t say skill issue, more of time issue. You only get a week to implement something. Quicker to use existing libraries than try to optimise yourself.

      • Hawke@lemmy.world
        link
        fedilink
        arrow-up
        9
        ·
        1 year ago

        It’s both, and they are in a sense the same.

        Cheaper less skilled or less experienced programmers take longer to get similar results. One week with a a skilled programmer is a lot more value than one week with an unskilled programmer.

        Even more if you want to invest some of that experienced programmer time to get the new guy up to speed.