Episode

Discussing different ways to model data

Podcast
No Compromises
Published
Nov 22, 2025
Duration seconds
710
Processing state
not_requested
Canonical source
https://share.transistor.fm/s/b5e7da9b
Audio
https://media.transistor.fm/b5e7da9b/5e305b68.mp3
JSON
/v1/public/podcasts/no-compromises-1309932/episodes/discussing-different-ways-to-model-data
Markdown
/podcast/no-compromises-1309932/discussing-different-ways-to-model-data.md

Actions

  • POST https://stenobird.com/v1/public/podcasts/no-compromises-1309932/episodes/discussing-different-ways-to-model-data/transcription-requests
    Idempotently request low-priority transcript generation for this episode.
  • GET https://stenobird.com/podcast/no-compromises-1309932/discussing-different-ways-to-model-data.md
    Read the agent-friendly Markdown representation of this episode resource.

Summary

It's easy to overcomplicate data modeling, especially when enums, relationships, and future requirements are in play. In the latest episode of the No Compromises podcast, Joel brings Aaron a real-world technical dilemma: how to model a relationship between two models when types are stored as enums, not models. We discuss the pros and cons of pivot tables versus JSON columns, the importance of context before jumping to solutions, and how developer instincts can sometimes get in the way of clarity. (00:00) - Setting up the technical problem (02:00) - Pivot tables vs JSON columns (05:15) - Filtering and validation considerations (07:15) - Deciding on the best approach (09:50) - Silly bit Would you like us to review your code or application architecture ?