With engineers moving from project to project and company to company, how do we ensure the systems we are building can survive constant organisational & personnel change? Why do some systems outlive others? And if we are honest with ourselves, are we guilty of thinking much too short-term about our software systems?
Drawing from real world examples, I will discuss the Scala projects that succeeded long-term (5+ years) and those that quickly became obsolete. I will further characterise some of the unique obsolescence pitfalls that Scala and its ecosystem bring and how to avoid them.
We’ll touch on the lesser known aspects of the API and the importance of choosing the right execution context.