How’s it going, I'm a Adam, a Full-Stack Engineer, actively searching for work. I'm all about JavaScript. And Frontend but don't let that fool you - I've also got some serious Backend skills.
Location
City of Bath, UK 🇬🇧
Education
10 plus years* active enterprise development experience and a Fine art degree 🎨
Full stack web dev.
Studying FP web development approaches, while helping Mission Bit create paths to programming for underserved public school kids.
Previously @ Gradescope.
Not OP, but I mentally distinguish between "values," which use const but tend to be local / temporary, and "constants," which also use const but tend to be in outer scope. I use screaming snake case only for the latter, if at all.
IMO when most of your values are immutable, which is a good place to be, the constants stop being special. Instead, the the things that can change over time are special, as they should be, since they require more effort to reason about.
Do you like constant case?
Not OP, but I mentally distinguish between "values," which use
const
but tend to be local / temporary, and "constants," which also useconst
but tend to be in outer scope. I use screaming snake case only for the latter, if at all.IMO when most of your values are immutable, which is a good place to be, the constants stop being special. Instead, the the things that can change over time are special, as they should be, since they require more effort to reason about.
I do, for real constants that are static values. Consider this example:
Since
url
isn't a true constant (it uses another variable to determine its value), I keep it lowercase.Also, I only use constant case at the top level scope, or when I'm importing constants from another file.