• techt@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    2 years ago

    I would enjoy seeing the codebase to see the impact of these guidelines. What do you like or dislike about them?

    • Sal Rahman@techhub.socialOP
      link
      fedilink
      arrow-up
      2
      ·
      2 years ago

      @techt@lemmy.world bear in mind, even though I’m the one who came up with these rules, I admit, the code looks incredibly ugly, IMO.

      That said, the goal isn’t clean code; it’s functioning code.

      There’s code with obviously no bugs, and then there’s code with no obvious bugs. We’re trying to minimize the latter.

      • techt@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        2 years ago

        I respect that – kudos for putting your own written rules out here for everyone! After working on a mid-sized? codebase for awhile I think my top priority would of course be functioning code, but right after that: maintainability. As people come and go and you have a Thesius’ Ship situation with your engineering team, readable and maintainable code now pays dividends later. How long have you been working on your codebase? Do you have trouble onboarding new people? I do think Clean Code™ is overrated – even after having read the book – so I agree with you there to an extent.