3
B-Con
1y

I work so hard to name things well and yet last year's code is always full of esoteric and misleading nonsense.

Comments
  • 2
    Maybe you overthink it? The most precise names are not always the most intuitive ones. An example: I named some stuff attachments for example, not scans, because the main Feature of it was, that it gets attached to something else, not that it is a scam or even image - and every other dev is like, I can't find the part in the code where the scanning happens.
  • 0
    yeah, naming things is not an easy task and things r getting even worse when things evolve in new directions. To use the prev. example you can't just name things attachments_of_scans_images_and_pdfs ( in your preferred case ) and call it a day... and expand the name for each new usage
  • 0
    @horus yeah! Choosing between describing the content vs its function is always a tricky trade-off.
Add Comment