aizatto.com
aizatto.com
Build.my
GitHub
Linkedin
aizatto.com
Table of Contents
Portfolio, Projects, Tools, Toys
Interview Guide
Engineering Code
Communication
Different Types of Coding
Commit Messages
Reviewing Code
Writing Code
Consistency
Writing for a code base of 1,000,000+ Lines
Write Code Knowing It Will Be Refactored
Naming
Versioning
Create Searchable Names
Commenting
Make It Easy To Reproduce
Scripts
80 character limit
Exit Early
Be careful of enum in switch statements
Be careful about chaining conditions
Be careful of chaining ternary operators
Write Code Knowing You Will be Blamed
Hacks
Bad Practices
Logs
Time
Other rules
Engineering Code
Engineering Data
Pipelines
Configuration Files
Site Reliability Engineering (SRE)
Best Engineers
Engineering Management
Why GitBook?
Getting into Tech
Personal Goals
Daily Drivers
Notes
AWS
Digital Ocean
GraphQL
JavaScript
Life
Node.js
Prototyping
Raspberry Pi
Serverless
Software Engineering
Technical Due Diligence
Web Development
Archive
Powered by GitBook

Naming

There are only two hard things in Computer Science: cache invalidation, naming things, and off by one errors.

Naming is hard. The goal of this document is to help with naming.

Dates

Year Month Day

Allows to sort way easier

​https://timestamps.aizatto.com/​

Common Names

content

Used for user stuff like user generated content, or the content of blog posts

title

Used for documents, or posts.

Previous
Write Code Knowing It Will Be Refactored
Next
Versioning
Last updated 1 year ago
Contents
Dates
Year Month Day
Common Names