In software development, we're all very much influenced by today's technologies and frameworks. There's a tendency to think about, describe and build systems in a way that's specific to the technologies in use today. However, this has a number of disadvantages wrt. complexity, longevity and maintainability.

I think it is essential that, in addition to understanding specific technologies, we also (re)consider a number of basic principles of building software and make sure those principles play a central role in day-to-day development. Over the last years I have been collecting and describing some 40 of those principles. In this session, I will provide a short overview over this collection and then describe six of those principles in more detail, including extensive examples.