a
a
aizatto.com
Build.myGitHubLinkedinNotion
Search…
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
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
Contacting Me
Notes
AWS
JavaScript
Node.js
Software Engineering
Technical Due Diligence
Web Development
Archive
More on Notion
Powered By GitBook
Bad Practices
This is a list of things I look out for in a codebase.

Bad Practices

General list of bad practices. You may see the points duplicated else where.
  • Not being consistent
  • Not paying attention to commit history
  • Not isolating work into separate commits
  • Not following style guides
  • Committing commented code
  • Long functions
  • Spaghetti code
  • Bad naming
  • Magic constants
  • Skipping pre commit hooks
  • Skipping already existing tests without good reasons

Code smells

​
Previous
Hacks
Next
Logs
Last modified 2yr ago
Copy link
Contents
Bad Practices
Code smells