Forget Flags and Scripts: Just Rename the File
Uptrenda
12 points
10 comments
March 18, 2026
Related Discussions
Found 5 related stories in 1069.5ms across 14,015 title embeddings via pgvector HNSW
- Stop Naming Your Variables "Flag": The Art of Boolean Prefixes (2025) mooreds · 12 pts · June 19, 2026 · 57% similar
- Go Naming Conventions: A Practical Guide begoon · 20 pts · March 27, 2026 · 42% similar
- Show HN: Skillscript – A declarative, sandboxed language for tool orchestration sshwarts · 14 pts · July 12, 2026 · 39% similar
- Launch HN: Captain (YC W26) – Automated RAG for Files CMLewis · 49 pts · March 13, 2026 · 39% similar
- Most rewrites serve the engineer, not the business bbsnly · 60 pts · July 01, 2026 · 39% similar
Discussion Highlights (4 comments)
Quarrelsome
this is satire, right?
castral
It feels wrong but I can't quite put my finger on the reason why... It will make version control more hectic, for sure. It also seems to be conflating identification with configuration which seems non-ideal. What about versioning and upgrading? How do I find a "well-known" entry point with a file name of flags? Every read now becomes an expensive find and grep lesson... Yeah, I don't like it.
csb6
Seems a lot easier to have a --help flag that lists all of the options and their function. That is self-documenting (assuming the descriptions are useful) and helps with discovery. Changing the name of the file to foo--bar.exe doesn't seem any easier than writing foo.exe --bar
abrookewood
You could skip the underlying mechanism by renaming Claude.exe and then it just passes the name as a new chat.