a day ago
- A list of articles recommended by an engineering leader for their team, covering coding practices, platform design, frontend development, databases, async programming, encoding, and books.
- Key coding principles include avoiding complexity, being cautious with abstractions, understanding complexity budgets, valuing locality of behavior, avoiding speculative features (YAGNI), and using parse-don't-validate techniques.
- For platforms, the recommendation is to think about exposing services programmatically to other teams, as highlighted in Steve Yegge's Google Platforms Rant.
- Frontend advice emphasizes declarative over imperative coding, purity of components and hooks, proper use of useMemo and useCallback, and understanding hypermedia systems for better HTML usage.