Hacker News with Generative AI: Code Style

German Naming Convention (chrisdone.com)
This is what I consider good naming convention. I discovered this convention while working with a German colleague, who, I’d always joked, uses long variable names, and almost never abbreviates anything. However, the more I read his code, the more I realised I was able to read the story he was trying to tell, and appreciated it a lot: Using as many words as necessary to clearly name something. Everything.
Is the 80 character line limit still relevant? (2008) (richarddingwall.name)
Traditionally, it’s always been standard practice for programmers to wrap long lines of code so they don’t span more than 80 characters across the screen.
The Unreasonable Effectiveness of Naming Integers (ziglang.org)
Lately my Zig code has started to look like this in all my projects:
Why Not Comments (buttondown.com)
Code is written in a structured machine language, comments are written in an expressive human language. The "human language" bit makes comments more expressive and communicative than code. Code has a limited amount of something like human language contained in identifiers. "Comment the why, not the what" means to push as much information as possible into identifiers. Not all "what" can be embedded like this, but a lot can.
Identifiers are better off without meaning (varoa.net)
The origin and virtues of semicolons in programming languages (ntietz.com)