Few weeks ago I wrote about a side project that I’m using to learn, this is my reviewing what I missed on the project, the main issues after a few dozen games in the platform with friends. And what I learned in the process.

All comments, feedback is appreciated.

  • CrypticCoffee@lemmy.ml
    link
    fedilink
    arrow-up
    5
    ·
    10 days ago

    Sounds about right. Fits in with the 80:20 rule. Does the first 80 quicker than the 20% of time it usually takes but does the next 20% which takes 80% of the time even slower.

    Effectively, it optimises the quicker bit so you suffer long term and overall waste more time while screwing the planet. It’s only fine for prototyping and even then, would that be the best base to build off? Is it modular and maintainable? Does it have low coupling and high cohesion? Or is it just trash?

    • Shin@piefed.socialOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      10 days ago

      Heavily coupled code with a lot of duplication of code. These are the main points of the refactor.

      There is some lack of “smart” use of the JS, like the positional arguments instead of objects (for quick fix/change), no separation of concerns, there is something lightly there, but lacks the gross thing.