Why on earth would you create a directory named "files"?
Why on earth would you create a directory named "files"?
When we say "struct" we generally are referring to C structs. Now that Go, Rust, etc, implement structs that sort of act like classes, should we start explicitly calling them C structs to differentiate from Go/Rust structs?
Naming things in software is hard (just like cache invalidation).
Renaming things can even be harder.
I wonder what the best strategy is if the entire company/brand is renamed, but the name has inevitably leaked deeply into code. Namespaces, package prefixes, S3 bucket names, you name it.
Keep the old name forever, even for new stuff for consistency?
Rename as much as realistic, leave the rest as "legacy"?
Use the new name for new stuff, keep the old one for existing?
Speichertest war erfolgreich, #Fedora 43 ist installiert und aktualisiert. Bevor ich jetzt aber weitermache: wie nenne ich ihn bloß?
What is it with people naming things without thinking?
There is a daycare / early childhood education business in a strip mall in my city, with a big sign out front advertising itself.
The business name on that sign? "ONCE UPON A CHILD".
Scout's honour. Sheesh!
#name #naming #NamingThings #business #inappropriate #WTF #wat #sheesh
#AutoTune software adjusts the frequency - the pitch - of musical elements like a singer's voice, musical instruments, or what have you, to fix them being off-key or out-of-tune. Whether autotune is an excellent tool for musicians and producers, or a blight on the listener's ear is out of scope for the discussion here 😉 .
The pitch gets adjusted up and down automatically to ensure it stays at the correct note, rather than drifting into the no-man's land between semitones. Up and down to just the right discrete values, like a certain people conveyance device common in tall buildings.
I just wanted to say that if there isn't already autotune software named "Elevator Pitch", there should be.
#idea #name #NamingThings #ElevatorPitch #pitch #software #elevator #music #producer #production #audio
In a stunning display of product management, Microsoft Power Automate has launched two entirely different features called "process map".
How would you prefer to name macros that generate syscalls in assembly?
Is there a canonical Assembly term for instructions or operands that are dependent on the byte offset of the instruction within the assembled/encoded output (ex: jmps to labels or RIP-relative operands)? Is Position-Dependent-Instruction a thing?