We all have heard the term - technical debt. While the semi-official definition seems clear (“It represents the accumulated shortcuts, quick fixes, and hasty solutions taken during the software development process to meet deadlines or immediate needs“), dealing with it is unclear.
Sometimes, it’s about “you cannot improve what you cannot measure” that stops us from dealing with it well; sometimes, it’s a lack of clarity on how to prioritize it against product/business deliveries, and sometimes, it’s just not enough people wanting to do the dirty work - because it is precisely that: fixing something to go from bad to average, and only sometimes - from average to good.
Much like financial debt, tech debt accrues interest over time. It manifests as increased complexity, decreased productivity, and heightened risk of system failures. Unaddressed tech debt can stifle innovation, limit scalability, and impede the ability to respond nimbly to market demands.
During the event, we will not only discuss different aspects of technical debt (identifying, measuring, solving, prioritizing, preventing, etc.) but also will go through concrete stories and experiences from:
- Vytautas Ašeris (Director of Engineering, Transactional Experience @Vinted), Dejan Menges (Senior Staff Engineer, Marketplace @Vinted)
- Aivaras Vencevičius (Head of Product @NordLocker), Linas Šlepikas (Head of Engineering @NordLocker)
- Tomas Miliauskas Software Architect & Senior Engineering Manager @wix)
- Jonas Minelga (Cluster Lead @DanskeBank)
