• Home
  • Consultancy
  • Training
  • Talks
  • Blog
  • Contact

How Domain-Driven Design enabled scaling a big ball of mud product

by Kenny Baas-Schwegler | Sep 14, 2023 | Talks

Many products start out with a simple, naive model able to prove market fit. And most of the time that one model grows, because more features need to be put in at a fast pace. This can have a huge impact once the product needs to scale. Because that fast pace can turn...
Collaborative Software Design: How to facilitate domain modeling decisions

Collaborative Software Design: How to facilitate domain modeling decisions

by Kenny Baas-Schwegler | Mar 1, 2023 | Talks

This talk delves into the challenges of collaborative software design, where developers and stakeholders work together to make sustainable design decisions that bridge the gap, align business needs with IT solutions, and create adaptable software systems. While...
Collaborative Software Design: How to facilitate domain modeling decisions

Deep Dive into Model-Driven Design: Refining Domain Models in Code

by Kenny Baas-Schwegler | Oct 18, 2022 | Talks

Most software products begin with an initial software model, one that is typically naive and superficial, grounded in basic understanding. This initial phase is natural, as it aligns with the early stages of discovering and exploring a new product with stakeholders....
Collaborative Software Design: How to facilitate domain modeling decisions

How cognitive biases and ranking fosters an ineffective architecture and design

by Kenny Baas-Schwegler | Nov 23, 2020 | Talks

The power of collaborative modelling comes from having a diverse group of people who, together, have a lot of wisdom and knowledge. You would expect that all this knowledge will be put to use, co-creating and designing a model. In reality, we don’t actually listen to...

EventStorming; Continuous discovery beyond software modelling

by Kenny Baas-Schwegler | Nov 26, 2018 | Blog

Moving towards a microservices architecture We see a lot of companies are moving towards a microservice architecture. The big pitfall of microservices architecture is to focus on the technology, how big the microservice needs to be, how many lines of codes, what...
Next Entries »

Recent news

  • How the bias towards additive can lead us to a suboptimal and costly software design
  • Resilient Bounded Contexts: A Pragmatic Approach with Residuality Theory
  • Coach your Architects in Agile Architecture!
  • Remote collaborative modelling part 1: Check-in
  • EventStorming; Core concepts, glossary and legend

Home   |  Consultancy  |   Training   |   Talks   |   Blog   |   Contact

©WeaveIT | Brand & webdesign by Art of Design