Naming and Findability
Unscored tasks with hints and instant feedback. Practice results never become credentials.
Short lesson
YYYY-MM-DD_client_subject_vNN.ext — lowercase, hyphens inside words, underscores between parts, no final/new/copy. Names are search keys.
Which file name follows the convention date_client_subject_version?
Sign up to practiseWrite a Git branch name and a one-line commit message for this change: “fix the login button that does nothing on Safari when the email contains a plus sign”. Format: first line branch, second line commit message.
Sign up to practiseRename every file so colleagues can find it by searching. Use: date first (YYYY-MM-DD), then client or “internal”, then subject, then version (v01, v02…) where a version is given; lowercase; hyphens inside words, underscores between parts; no spaces, special characters, or “final/new/copy”. Open a file to read what it is. You may also sort files into folders.
Sign up to practiseWrite the team naming standard in /standards/naming.md: a pattern line, the rules (date format, case, separators, versions, forbidden markers), and three examples. Then rename the two sample files in /samples to follow it.
Sign up to practise