With such a tool, everybody could solve most of their own problems themselves. My personal hope is that it is possible to build a software development tool that avoids all unessential complexities. More about Testing & Quality Defeating unessential complexity → Application Load Testing with Open Source and the Cloud Visit our IPC ’17 Sessions with a focus on Testing & Quality This is why in my talk Rapid Prototyping with Domain-Driven Design I claim that complexity is essentially in the domain. Whatever kind of software you write, you will have to deal with the domain and its complexity.

If you write a restaurant management system, your domain consists of tables, orders and bills. If you are creating a jump-n-run game, your domain includes physics, didactics and game design. Outside the technology lies the conceptual space of the problem you are trying to solve with your piece of software: the domain. Think outside of technology, think in terms of domain Each with their own benefits but also own drawbacks, like added complexity. Many different languages and frameworks to use. There are many ways to solve a certain problem with software. But these are all solutions to technical problems and while they receive a lot of attention, I consider them unessential. One could think that if this trend continues, writing software might one day be as easy as 123. Every other week there is a new programming language claiming to reduce it, every other day a new framework to make storage, networking, rendering or communication easier than ever before.

Software Architecture (Frameworks & Co.)īut what about complexity? Can it be defeated? We sure are trying.

Domain driven design cheat sheet