Anil Wadghule explains why applying SOLID OO design principles to their extreme leads to Functional Programming.
Colin Garlick presents a foundation of value for the practice of architecture, starting with the values that architecture is established on, showing what's important for an architecture.
Mike Barker shares lessons learned at LMAX Exchange: starting from a clean domain model is imperative and understanding the trade-offs between performance and safety/generality/functionality.
Kevlin Henney revisits the original premise and definition of “Worse is Better”, and looks at how this approach to development can still teach something surprising and new.
David Tanzer, Oliver Zymanski explain with examples how to apply the rules and principles of object-oriented software design to create simple architectural designs.
How Can We Use Our Creative Power and Technological Opportunity to Address the Challenges of the 21st Century?
Gyorgyi Galik discusses our urban future and explores new possibilities to create projects and materials that change the environmental effects of art and design practices.
David Joyce discusses how organizations can solve their super-ordinate problems through the use of the Vanguard Method.
Leslie Lamport makes the case for separating the design details of what a program should do and how it should work from the business of writing code, and discusses how the design process should work.
Pawel Brodzinski focuses on the importance of having a correct mindset and understanding the context rather than blindly following some methods.
Jessica Kerr explains through Java and C# code samples six principles of the functional programming style.
Josh Wexler takes participants through the Idea Stack exercises and use case studies, illustrating how to build a vision for a product before developing it.
Eric Evans shares approaches that have helped him with issues in architecture, with a focus on establishing boundaries between software with different conceptual approaches and discipline levels.