The Psychology of Bad Naming
Stop Naming Things "Data"
Code is read ten times more frequently than it is written. When you are rushing to close a Jira ticket, naming an array data2 makes perfect sense to you in that exact microsecond of context. Six months later, when the onboarding junior developer looks at your code, they will have absolutely no idea what data2 contains, why it exists, or why it differs from data1.
The Variable Name Critic exists to enforce semantic meaning. A variable should describe exactly what it holds—no more, no less. It should not contain data types in the name (Hungarian notation died for a reason), and it should certainly not be a single letter unless it is a standard loop index.
By passing your identifiers through the SnarkLintProtocol, you receive immediate feedback on whether your naming conventions are communicative, or if they are actively detrimental to the cognitive load of your engineering team.
The Anatomy of a Terrible Identifier
Context Bankruptcy
Calling an object obj or an array arr tells your team zero information about the business domain logic. Is it a user payload? A product config? Be explicit.
Single Character Laziness
Unless you are writing a standard iteration index (like i or j) inside a 3-line loop, single-character names (like x, p, or v) are a massive red flag.
The Number Suffix
If you name something user2, you have failed at data structures. If you have multiple users, you need a List, an Array, or a Map. Do not increment variables like a caveman.
Case Studies in Cognitive Load
The "Temp" Variable That Stayed
The Reality: A developer named a variable tempAuthToken while testing a login flow. They forgot to refactor it.
The Impact: Three years later, the entire microservice architecture depends on a core entity officially documented as `tempAuthToken`.
The Lesson: Nothing is more permanent than a temporary variable.
The Global "x"
The Reality: A data scientist pushed a Python script where the core dataframe was named x.
The Impact: 800 lines of code manipulating `x`. Reviewers spent a week trying to figure out what `x` represented at any given point in the lifecycle.
The Lesson: Memory is cheap. Use your keyboard.
The Wall of Tears
Developers roasted for their linguistic failures.
The Complete Partner Toolkit
The Sassy Roaster
Paste code, receive pain. The primary syntax evaluator powered by SnarkLintProtocol.
Git Excuse Generator
Generate highly technical, passive-aggressive commit messages to blame DevOps or cosmic rays.
Regex Destructor
Test your regex while discovering why your complex pattern should just be an if-statement.
Div Centering Lab
A safe interactive playground to test flexbox and grid alignment techniques visually.
Variable Name Critic
Audit variable identifiers like 'temp2' and receive strict algorithmic critiques.
"Works on My Machine" Cert
Generate an official compliance certificate to deny production culpability to your team.
Naming Conventions FAQ
Why does the SnarkLintProtocol flag words like 'data' or 'info'?
Because all computer variables hold data. Calling a variable userDataObject is redundant noise. Name it user or userProfile instead.
Does this critic handle camelCase and snake_case?
Yes. The audit engine parses the text string to inspect casing conventions, token lengths, included integers, and semantic meaning regardless of your preferred language casing rules.
Why shouldn't I use numbers in my variables?
Appending numbers (e.g., user2, finalResult3) usually indicates you failed to design a proper data structure (like an array or a mapped object) to handle multiple instances of a variable type.