{"version":"1","chapters":[{"title":"Watch in this episod","startTime":0,"endTime":68,"img":"https://media.rss.com/clojure-in-product/20241203_121230_77b2aa47acb9bd986f1784f4a3064124.png"},{"title":"Adam about himself and CodeScene","startTime":68,"endTime":119},{"title":"Why Clojure is efficient and fun","startTime":119,"endTime":307},{"title":"CodeScene's choice for Clojure: drawbacks","startTime":307,"endTime":470},{"title":"Clojure's Performance: more than enough","startTime":470,"endTime":549},{"title":"CodeScene's choice for Clojure: advantages","startTime":549,"endTime":729},{"title":"Scaling a team is always challenging","startTime":729,"endTime":890},{"title":"Architectural decision-making","startTime":890,"endTime":1061},{"title":"Balancing under-engineering and over-engineering","startTime":1061,"endTime":1145},{"title":"Culture of technical decisions","startTime":1145,"endTime":1317},{"title":"Technical debt and code quality","startTime":1317,"endTime":1400},{"title":"Dogfooding at CodeScene","startTime":1400,"endTime":1565},{"title":"Any push to move away from Clojure?","startTime":1565,"endTime":1686},{"title":"Clojure in different domains","startTime":1686,"endTime":1859},{"title":"Politics in technical decision-making","startTime":1859,"endTime":2012},{"title":"TypeScript in Clojure product","startTime":2012,"endTime":2329},{"title":"Clojure as the go-to tool for new projects","startTime":2329,"endTime":2475},{"title":"State of Clojure and future predictions","startTime":2475,"endTime":2619},{"title":"Coding vs. management","startTime":2619,"endTime":2725},{"title":"Favorite tasks","startTime":2725,"endTime":2784},{"title":"Questions from Kalle Korhonen","startTime":2784,"endTime":2979},{"title":"Adam's question for the next guest","startTime":2979,"endTime":3205}]}