Chapter 40 — Further Reading

Career paths (everyone)

  • Job-board research (LinkedIn, Indeed, Levels.fyi) — read current postings for DBA, database developer, data engineer, and data architect; note recurring skills and compensation in your region (don't trust fixed numbers — research live data).
  • "Data engineering roadmap" guides — the skills and tools for the fastest-growing database-adjacent role (Case Study 2).
  • "What does a DBA do in the cloud era?" articles — how the role evolved.

Keep learning (everyone)

  • PostgreSQL release notes & documentation — read the yearly release notes; the docs are a career-long reference.
  • Martin Kleppmann, Designing Data-Intensive Applications — the book to grow into after this one; deepens distributed systems, consistency, and data architecture.
  • The PostgreSQL community — mailing lists, Planet PostgreSQL (blog aggregator), PGConf conferences, local user groups.
  • Markus Winand (use-the-index-luke.com), Bruce Momjian's talks, the "Internals of PostgreSQL" site — to go deep on performance and internals.

Interview prep (💻 📊 🏗️)

  • SQL practice sites (pgexercises, LeetCode database, StrataScratch, DataLemur) — drill the query questions.
  • System-design / database-design interview guides — the "model this domain" and "which database" questions (Parts III, VI).
  • "How to talk about your projects in interviews" — framing trade-offs and decisions (Case Study 1).

Going deeper by path

  • Data engineering: dbt, Airflow/Dagster, Spark, cloud warehouses (Chapters 31, 34).
  • DBA/operations: pgBackRest, Patroni, monitoring stacks, performance tuning (Chapter 38).
  • Architecture: distributed systems, NewSQL, the decision framework at scale (Chapters 35, 37).
  • AI/data: embeddings, pgvector, RAG (Chapter 36).

Reference (this book — your lifelong companions)

  • The appendices — glossary, SQL quick reference, data types, EXPLAIN/tuning, normalization, the SQL cookbook, dialect differences. Keep them next to your keyboard.
  • Your capstone (Chapter 39) — your proof and your portfolio.
  • The whole book — revisit any part as your work demands it.

Do, don't just read

  • Polish and publish your capstone; link it from your résumé and profiles.
  • Schedule recurring learning time for one source above.
  • Apply for the role you want — you have the foundation. The data is waiting; the work is yours.

This is the end of the chapters. Continue to the Appendices — your lifelong references — and go build databases that last.