• Unnecessary abstractions - I have seen this happen when companies try to customise a standard product like Kubernetes to make the configuration easier to work with. However, what ends up happening is them defining their own standard or DSL but not keeping docs up-to-date. This makes it hard for new joiners as they have to learn this bespoke standard. If they had not added an abstraction, people who had already worked with the product would be able to jump straight into using it.
  • Definition of done — shared team checklist (tests, code review, docs, observability, deployment) defining when a piece of work is genuinely complete
  • PR bot — automate repetitive pull request hygiene (reviewer assignment, CI/lint summaries, stale PR reminders, and dependency updates)

API

  • propagate a request ID on every request and attach contextual metadata for tracing and debugging (see structured logging below)
  • set body size limits
  • validate incoming requests at the boundary
  • embed build version / commit SHA at compile time
  • use plural nouns for collection/array fields and endpoints

Code Quality

  • avoid down database migrations in production — they are rarely tested against real production data, risk destructive data loss (such as dropping columns or tables), and can leave database state out of sync with version control; prefer forward-only (expand-and-contract) migrations
  • use CI/CD to maintain code quality
  • keep PRs small and focused — easier to review, less risk
  • write tests for behaviour, not implementation details
  • delete dead code — version control remembers it
  • avoid premature optimisation — measure first

Code Review

  • review for correctness, readability, and maintainability
  • automate style checks with linters — don’t argue about formatting in reviews
  • the reviewer should understand the change, not just approve it

Error Handling

  • fail fast — surface errors early rather than hiding them
  • use structured logging with context (request ID, user, operation)
  • distinguish between recoverable and unrecoverable errors
  • don’t swallow errors silently

Documentation

  • document the why, not the what — code already shows the what
  • keep READMEs up-to-date with setup instructions
  • use Architectural Decision Records for significant decisions