Really enjoyed this tech debt panel on Weds, kindly hosted by Matt Ellis and Liam Walford. Sushi > Pizza for future tech meetups! Thanks to Ilan Brodsky Jason de Carvalho Ke Ren James Oughton Linda Holmes for a great discussion about: - Defining tech debt (it's not always code) - Identifying it (where do strong engineers fear to tread? where are the bugs clustering?) - Getting time to address tech debt (Building into estimates, using RICE score to highlight risks upwards, tying into metrics like Velocity or Change Failure rate) - Actually addressing the debt (Preventative vs remediation as approaches, subclasses of remediation: tweak vs correct vs deprecate vs do nothing at all, and when they are each appropriate)
Last night we hosted Collective Connect, where we discussed all things Technical Debt! It was a great evening, with some fantastic open dialogue and tasty Sushi 🍣 😋 A big thank you to Adam Hogge for facilitating the event, and thanks to all those who came Ilan Brodsky Jason de Carvalho Ke Ren James Oughton Linda Holmes We will be putting together a blog post to summarise the conversation, so watch out for that! If you are a CTO and would like to attend or facilitate one of our Collective Connect events, then please drop me or Liam Walford a DM #CTOevent #collectiveconnect #technicaldebt #roundtable
Shrunjal Mehta
3mo
Sounds like a fantastic event, Adam Hogge! The discussion on tech debt was incredibly insightful. Looking forward to the blog post summary and future meetups. Sushi definitely wins for the next one!
Thanks again for facilitating Adam Hogge