Naming Files and Directories the Right Way | COFYT

Home

Library

Sign In

Naming Files and Directories the Right Way | COFYT

About this video

Video Title: Naming Files and Directories the Right Way
Channel: Skill Foundry
Speakers: Eric
Duration: 00:07:27

Overview

This video explains the top five mistakes beginners make when naming files and directories and provides best practices for professional IT work. The speaker emphasizes the importance of establishing good habits from day one to avoid future problems, particularly when working with command lines, web development, and in professional software development environments.

Key takeaways

Rule 1: No Spaces: Spaces in file and directory names can cause significant issues with command-line tools and web development, requiring extra characters or quotation marks for them to function correctly. Professionals use underscores, hyphens, camelCase, or PascalCase instead.
Rule 2: Avoid Special Characters: Only letters (A-Z), numbers (0-9), and underscores are generally safe. Special characters like exclamation points or dollar signs are risky and can cause problems with different tools. The dot character is an exception for hidden files and extensions.
Rule 3: Be Descriptively Concise: Names should be clear enough to understand the content but not so long that they become difficult to type or manage. Good naming saves time and frustration for both yourself and your colleagues.
Rule 4: Case Sensitivity: In many systems and tools, letter casing matters (e.g., "Hello" is different from "hello"). It's recommended to consistently use lowercase characters to avoid potential issues and ensure compatibility, especially on servers.
Rule 5: Dates and Sorting: When including dates in file or directory names for sorting purposes, always use the YYYY-MM-DD format. This ensures chronological sorting, unlike other date formats where leading characters can disrupt the order.
Bonus Rule: Be Consistent: Once a naming pattern is established within a project, stick to it. Consistency is crucial for teamwork and adhering to project style guides, preventing annoyance among peers.