Why Principles Matter?

One Function, One Job

Each function should do a single thing -- it keeps code testable, debuggable, and extendable.

Name things clearly.

Variables, functions, and classes should reflect what they are or do -- your future teammates (and self) will thank you.

Duplicate logic is a liability.

If you're writing the same logic a second time, pause and think DRY.

Readable code > clever code.

Write for the next person, reading it not to impress, but to communicate. Clarity beats cleverness every time.

AI is confident, but not necessarily correct.

Code suggested by AI must be tested, validated, and reviewed like any junior engineer's work.

Design the API before you code

Finalize and align on the API structure with all dependent teams before writing any business logic

Quality isn't someone else's job.

If you write the code, you're responsible for making sure it works.

Focus on the root cause, not blame.

When things break, stay calm, learn deeply, and fix forward -- blame doesn't solve anything.

Reproduce the bug before you fix it

Until you can trigger it reliably, you're not ready to fix it.

Every bug deserves a test

Write one before or after -- but don't leave a bug fix unguarded. That's how we prevent reruns.

When the logic gets tricky, lead with a test.

Use tests to guide complex logic and edge cases -- TDD brings clarity before code.

Minimal permissions, maximum safety

Grant access only when necessary -- and only as much as needed.

All external data is untrusted

Validate and sanitize everything -- forms, APIs, query params -- before using it.

Never share secrets over insecure channels.

Use end-to-end encrypted methods -- not email, not Slack.