this post was submitted on 20 Dec 2024
116 points (99.2% liked)
Programming
17666 readers
288 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Very good points. A codebase that gets this VERY wrong is Gitlab. I think it might be a dumb characteristic of Ruby programs, but they generate identifiers all over the place. I once had to literally give up following some code because I could not find what it was calling anywhere. Insanity.
Another point: don't use
-in names. Eventually you'll have to write them down in a programming language, at which point you have to change the name. CSS made this mistake.foo-barin CSS maps tofooBarin Javascript. Rust also made this mistake with crate names. A crate calledfoo-barmagically becomesfoo_barin Rust code.I've been working in Ruby on Rails lately (unfortunately) and yeah it's extremely bad at this. There's so much hidden implicit behavior everywhere.
The dash
-vs underscore_is also a common "problem" with CLI arguments--file-name, that are mapped to variable namesfile_name.Yeah, translating between cases isn't exactly a problem IME. Might be neat to have a case-aware grep though, so you can get kebab-case, snake_case, camelCase and PascalCase all done in one go.