We all knew it

  • neclimdul@lemmy.world
    link
    fedilink
    English
    arrow-up
    24
    ·
    29 days ago

    Feels like the old php metric. PHP had a ton of great code and successful projects but it also attracted very bad devs as well as very inexperienced devs leading to a real quality problem.

    Honestly kinda see thing in a lot of JavaScript applications these days. Brilliant code but also a ton of bad code to the point I get nervous opening a new project.

    My point? It may be a tough pill but it’s not the project framework that makes projects fail, it’s how the project is run.

    • ChickenLadyLovesLife@lemmy.world
      link
      fedilink
      English
      arrow-up
      17
      ·
      29 days ago

      I witnessed a huge number of failed projects in my 25-year career. The cause was almost always the same: inexperienced developers trying to create a reusable product that could be applied to imagined future scenarios, leading to a vastly overcomplicated mess that couldn’t even satisfy the needs of the original client. Made no difference what the language or framework was or what development methodology was utilized.

      • neclimdul@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        29 days ago

        I’ve seen a lot of contractors over promising timelines too. “No matter how hard you push and no matter what the priority, you can’t increase the speed of light.”

        But yeah exactly.

      • neclimdul@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        1
        ·
        29 days ago

        No it’s a set of tools you can use to run a project.

        My point is that a lot of people use “agile” to mean not planning or don’t put guard rails on scope and they fail. That’s not agile, it’s just bad PM