Tier 1
Series 7
7B: The Camel Case Protocol
"In a cockpit, every switch and dial follows a universal labeling standard. If your AI names its variables like drone_speed in one script and DroneVelocity in another, you've created **Cognitive Friction**. A skilled Engineer audits for **Universal Naming Protocols**."
The Concept: C# Standards
Programming languages have "Style Guides" that help our brains process code faster. In Unity C#, we use two primary styles to tell the difference between "Things" (Variables) and "Actions" (Methods).
* **camelCase:** Used for **variables** (e.g., currentFuel). Start with a lowercase letter. Words are joined with no spaces, and each subsequent word starts with a capital.
* **PascalCase:** Used for **Methods and Classes** (e.g., TakeDamage()). Every word, including the first, starts with a capital.
* **Descriptive Names:** Avoid x, y, or temp. If it stores engine heat, name it engineHeat.
* **camelCase:** Used for **variables** (e.g., currentFuel). Start with a lowercase letter. Words are joined with no spaces, and each subsequent word starts with a capital.
* **PascalCase:** Used for **Methods and Classes** (e.g., TakeDamage()). Every word, including the first, starts with a capital.
* **Descriptive Names:** Avoid x, y, or temp. If it stores engine heat, name it engineHeat.
Red Flag Detected
The AI Trap: "The Naming Soup"
You ask the AI: "Calculate the distance between the drone and the hangar."
// AI-Generated Code: Messy and Inconsistent
void calc_dist() {
// Audit Fail: 'd' and 'h' are meaningless names.
// 'calc_dist' uses underscores, which isn't standard C#.
float d = Vector3.Distance(transform.position, h.position);
}
This is "Visual Static." When you have 400,000 files, you cannot afford to guess what d stands for. A professional pilot demands "Self-Documenting Code" where the names explain the logic.
Elite Telemetry
Research shows "Elite" teams achieve 15% faster lead times by keeping AI on a "very tight leash."
- Small Batches Solving one problem at a time prevents logic drift.
- Modular Design Localizing the "blast radius" of AI changes.
- Tight Loops Rapid iteration with constant code review.
The Mechanic's Correction
Corrective Protocol
// Corrected: Professional and Auditable.
void CalculateDistanceToHangar() {
// Audit Pass: Names are clear. Variables are camelCase.
float distanceToHangar = Vector3.Distance(transform.position, hangarTarget.position);
}
Your Pilot Command
> A skilled Mechanic directs the AI to **Follow the Protocol**. You command: "Rename the variables using descriptive camelCase and the method using PascalCase."