Panel Discussion: Building a New Tech Stack vs. Sticking to What You Know
summary
Compares keeping an existing stack to building a new one by naming concrete practices: favoring a builder/platform approach, adding GraphQL to meet developer needs, and choosing APIs that reduce silos; describes creating a data dictionary from ~200 items then prioritizing the top ten facts, exposing them via Looker/Redash or Salesforce integrations. Emphasizes front‑loading discovery, measuring expected impact and velocity, and preferring “progress over perfection” when deciding buy versus build.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:58About Contentful
- 2:20About trey
- 5:50The builder mindset
- 8:44Focus on the end result
- 11:34Building predictability
- 12:32Meeting people where they are
- 16:02Creating impact
- 18:21Creating a data dictionary
- 21:30Product decisions
- 24:40Efficiency velocity
- 28:44Key takeaways
- 30:26Wrap up
related talks
29mApps, Stacks, and Frameworks: Avoiding “Shiny Object” Syndrome
56mData Unleashed: A Developer's Perspective on Navigating the Architecture Maze
11mLeading without committing: Managing teams outside your tech stack
41mUnpacking Technical Decisions
47mPanel - Modernization Stories - Monoliths, Migrations and Mergers
26mArchitecting for scale
46mDigital scale-up architectural patterns
30mEngineering in Overdrive: How to Thrive When Tech Evolution Goes Full Gas