Uppercase initially and then gradually start introducing lower case letters farther down the statement, in an effort to gaslight the guy who has to debug your code later
this post was submitted on 24 Feb 2024
27 points (96.6% liked)
technology
23218 readers
2 users here now
On the road to fully automated luxury gay space communism.
Spreading Linux propaganda since 2020
- Ways to run Microsoft/Adobe and more on Linux
- The Ultimate FOSS Guide For Android
- Great libre software on Windows
- Hey you, the lib still using Chrome. Read this post!
Rules:
- 1. Obviously abide by the sitewide code of conduct. Bigotry will be met with an immediate ban
- 2. This community is about technology. Offtopic is permitted as long as it is kept in the comment sections
- 3. Although this is not /c/libre, FOSS related posting is tolerated, and even welcome in the case of effort posts
- 4. We believe technology should be liberating. As such, avoid promoting proprietary and/or bourgeois technology
- 5. Explanatory posts to correct the potential mistakes a comrade made in a post of their own are allowed, as long as they remain respectful
- 6. No crypto (Bitcoin, NFT, etc.) speculation, unless it is purely informative and not too cringe
- 7. Absolutely no tech bro shit. If you have a good opinion of Silicon Valley billionaires please manifest yourself so we can ban you.
founded 5 years ago
MODERATORS
You're a monster.
i don't remember posting this at all
Queries can quickly get complex, and I find that using caps increases readability quite a bit.
Editing in something that does blocking and syntax highlighting helps a lot too
I use uppercase for keywords in my database console/script editor mostly because it helps me find the identifiers faster for figuring out where the parameters need to go once I port it to the server code. Very lo-fi way of coding but whatever 
lowercase if I'm just typing ad hoc one off queries, but always uppercase if it's something anyone will have to read later, including myself in six months
Lowercase because if I do uppercase I feel like a crusty old COBOL dude patching a 50 year old financial system.
I do lowercase, too lazy to switch casing for the commands and most editors do syntax highlighting for sql so I don't think there's really much readibility loss.
Generally if a gray beard does it I will as well. While I dont follow their advice blindly there is a reason why boomer programmers stick around in some spaces.
Upper. Just convention.
Better question: "Ess Queue Elle" , or "Sequel"?
UPPER, because usually when I'm writing SQL it's because I'm working on someone else's code. Usually when it's fresh code I abstract, so the actual DB used can change.
just use the formatter and go with whatever it does
Honestly, whatever I feel like.
Lower case, easier to type and just run it through a formatter. And no implicit joins.
Uppercase keywords so you can actually read your code
Use a formatter and free up your brain space.