• @Buttons@programming.dev
    link
    fedilink
    English
    010 months ago

    Shorter code is almost always better.

    Should you use a class? Should you use a Factory pattern or some other pattern? Should you reorganize your code? Whichever results in the least code is probably best.

    A nice thing about code length is it’s objective. We can argue all day about which design pattern makes more sense, but we can agree on which of two implementations is shorter.

    It takes a damn good abstraction to beat having shorter code.

    • @Vince@feddit.de
      link
      fedilink
      110 months ago

      Here you go: https://codegolf.stackexchange.com/

      But on a more serious note, I don’t really agree. Writing more code needs to be a conscious choice, but going for the shortest code too often creates a mess. I know, since I was that junior dev who just wanted to get stuff done and I would ignore project architecture in order to have to implement less, like accessing the database in GUI code.

      Shorter code with the same amount of coupling between components and with the same readability is always better though.

    • @TanakaAsuka@sh.itjust.works
      link
      fedilink
      110 months ago

      I mostly agree with this but more than shorter code I value readability, I would rather take 3 lines to be clear to any developer than use some obscure or easy to misunderstand structure to write it in 1.