Marco Heimeshoff – Talk Session: Software Development Is Not About Software

video:

Explore DDD 2018 – Denver, Sept. 11-14

We build software that changes the world. From optimizing small companies to connecting humans and businesses on a global scale, our work plays a hidden but major role. Software development is not about software, it is about understanding the customers’ domain and solving their problems. We need a culture, a way of thinking about the needs of the customers first and putting an emphasis on their language and human interactions. If we let the domain drive our design, we can tackle complexity in the heart of software. The pillars of Domain-Driven Design are learning, language, and empathy. With the right mindset it becomes simple to derive good models, keep them pure and aligned with the business. Marco explores how to use Domain-Driven Design to transform everything in your organization: code, culture, agile, and architecture.

About Marco Heimeshoff

Marco Heimeshoff is a trainer, coach, and software developer from Germany. He co-organizes KanDDDinsky, a conference about the art of business software, and founded the German DDD community in 2013. Marco Heimeshoff has an unhealthy relationship with Domain-Driven Design, and won't leave any stone unturned once you lend him an ear and sticky notes.

He believes that life long learning, focus on language and empathy are the three pillars of quality development. Frustration about the same old methods of working together and developing solutions lead him to Domain Driven Design, agile software development, functional programming and CQRS with event sourcing. With ten years of experience in these topics, he helps teams to change and learn in all things from code to culture.

WEBSITE: http://exploreddd.com
TWITTER: http://twitter.com/ExploreDDD

Tags

Follow us

Read our latest news from Virtual DDD on any of these social networks!

Recent videos

Impact Mapping – The Secret Sauce

Details "Impact mapping is a lightweight, collaborative planning technique for teams that want to make a big impact with software products. It is based on user interaction design, outcome-driven planning and mind mapping. Impact maps help delivery teams and...

Pragmatic Architecture: How to Know When It’s Enough

Details Overengineering wastes time and effort, while underengineering creates future pain. How do you strike the right balance? This talk explores how you can use the balanced coupling model to achieve the just-right engineering. You’ll learn to predict volatility of...