Chapter 39 — Further Reading

Putting it together (everyone)

  • The whole of this book — the capstone draws on every part. Revisit the part you leaned on least; the capstone is where gaps show.
  • Mercado (sql/schema.sql, Appendix B) — your model for a clean, idempotent, fully-constrained schema and clear data dictionary. Mirror its quality in your own project.

Building a portfolio (💻 📊 🏗️ — career-oriented)

  • "How to build a data/database portfolio project" articles — what reviewers and interviewers look for: realistic scope, clear docs, reasoning.
  • README and documentation best practices — a great README is the difference between an impressive project and an ignored one.
  • Public dataset sources (data.gov, Kaggle, government open data) — if you want a richer/real dataset to build your capstone on (ties to the data-sources appendix idea).

Design rationale & communication (everyone)

  • Architecture Decision Records (ADRs) — a lightweight format for documenting why you made each decision. Perfect for the design-decisions document; widely used in industry.
  • "How to explain technical decisions in interviews" — framing trade-offs, not just listing what you did.

Going deeper on the domains (optional)

  • Domain modeling references (library/ILS schemas, FHIR for healthcare, student-information-system models, e-commerce schemas) — real-world schema inspiration if you want to deepen your chosen domain.

Reference (this book)

  • Every chapter — the capstone is their synthesis.
  • Chapter 37 — The Database Decision: the rationale for choosing PostgreSQL, to include in your design doc.
  • Chapter 40 — The Database Career: how to present this capstone to employers (next).
  • Appendices — the references (SQL, data types, EXPLAIN, normalization) you'll consult while building.

Do, don't just read

  • Finish your capstone — work the Chapter 39 exercises end to end. The reading is done; the doing is the point.
  • Get feedback — have a peer set it up from your README and critique your design-decisions doc.
  • Publish it — a public repo you can point an employer to.

Next: Chapter 40 — The Database Career: where this all leads.