Configuration vs. Implementation
summary
A custom service called Quentin service takes normalized shop data, applies a templating engine to generate merchant-specific flat files, and sends them via FTP/email, replacing dozens of hard-coded exporters. Building it costs more upfront (engineers refactor work) but integration time drops from weeks to days, with a claimed seven-merchant break-even in effort. The system serves 300,000 customers, 30 engineers, and keeps one code path for export/transport while moving format differences to configuration.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 3:25Configuration vs Implementation
- 4:10The big question
- 4:46Agenda
- 5:28Definition
- 7:26Example
- 10:41Story
- 15:59New approach
- 23:37Developer happiness
- 24:59Breakeven
- 25:49Off introduced
- 26:31Automating chart
- 27:49Business purpose
- 28:09Conclusions
- 29:27Questions
related talks
17mDeveloper Experience Q&A
28mStories of Success: Merchant Panel
22mOptimization strategies for a performant, headless storefront
16mModular and Distributed IDE
39mScaling R&D to thousands of people without dedicated QA
26mUsing a custom template loader at scale
21mBeating the Iron Triangle: Trade-offs, Primitives & No Silver Bullets
31m“Good Enough” Architecture Part 1