27
llamaa
61d

WRITE documentation. Fuck.

Comments
  • 6
    Nah fuck documentation. Use to brain to figure it out loser /s
  • 7
    In an ideal world, just a comment here and there would be enough documentation.
    But if the code is ugly, no amount of documentation can fix that.
  • 11
    You want me to document fucking for you? I'm pretty sure it's a learn on the job skill.
  • 2
    Documentation, one of the things I don't mind a computer replacing me to do.
  • 1
    Both please
  • 3
    "Its self explaining"
  • 4
  • 0
    @C0D4 You'd be surprised
  • 2
    I named my method “getSomething” so now the proceeding 300 lines of complex regex validation, 30+ data mutations and syntax sugared unreadable validations need no explaining.
  • 0
    documentation. Fuck.
  • 0
    The code should be the documentation. It should always be clear what the function or class does by just looking at the name. Only places where comments should be are some complex algolrithms.
  • 0
    @hitzoR if the business rules don’t make sense or are overly complex, that will be mirrored in the code. It does not matter how clean it is when the rules it is based on are fucked to begin with
Add Comment