{"version":"1","chapters":[{"title":"Teaser","startTime":0,"endTime":58},{"title":"Episode 04 Intro","startTime":58,"endTime":120},{"title":"James path in software development","startTime":120,"endTime":240},{"title":"Discovery of Clojure","startTime":240,"endTime":364},{"title":"Clojure in Griffin. AWS for banking","startTime":364,"endTime":471},{"title":"Rationale for choosing Clojure","startTime":471,"endTime":680},{"title":"Stepping into leadership in Clojure Company","startTime":680,"endTime":780},{"title":"Banking on Clojure","startTime":780,"endTime":1163},{"title":"Culture of Clojure: Innovation vs Overengineering","startTime":1163,"endTime":1313},{"title":"VP of Engineering role in a company","startTime":1313,"endTime":1509},{"title":"Challenges in finding Clojure talent","startTime":1509,"endTime":1738},{"title":"What attracts people to Clojure","startTime":1738,"endTime":2010},{"title":"Culture of architectural decisions","startTime":2010,"endTime":2208},{"title":"Overengineering in Clojure","startTime":2208,"endTime":2518},{"title":"Clojure's competitive advantage in business","startTime":2518,"endTime":2643},{"title":"REPL-based development","startTime":2643,"endTime":2948},{"title":"Testing in Clojure","startTime":2948,"endTime":3073},{"title":"When Clojure saved the day","startTime":3073,"endTime":3280},{"title":"Clojure in 2024","startTime":3280,"endTime":3304},{"title":"Advice for Clojure Tech Leadership","startTime":3304,"endTime":3478},{"title":"Question from the guest","startTime":3478,"endTime":3584},{"title":"Question to the next guest","startTime":3584,"endTime":3727}]}