kyziq

HTTP status codes are three-digit numbers that provide a way for the server to inform the client about the status of their request. Below is a table listing commonly used HTTP status codes, their constant names, and reason phrases.

Informational Responses (1xx)

Code	Constant	Reason Phrase
100	CONTINUE	Continue
101	SWITCHING_PROTOCOLS	Switching Protocols
102	PROCESSING	Processing

kyziq

Commit conventions allow the team to add more semantic meaning to git history. This includes type, scope or breaking changes.

[
  'build', 'chore', 'ci', 'docs',
  'feat', 'fix', 'perf', 'refactor',
  'revert', 'style', 'test'
];

kyziq

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules