Refactoring in Domain-Driven Design: Embracing Change as Knowledge Evolves
| |

Refactoring in Domain-Driven Design: Embracing Change as Knowledge Evolves

ByJurgen Stillaert

Refactoring is a crucial aspect of Domain-Driven Design, allowing teams to adapt their domain models and code as knowledge evolves, ensuring maintainability, flexibility, and alignment with the domain. Embrace refactoring as a natural part of DDD to develop accurate and adaptable software solutions.

The Power of EventStorming: A Real-World Example of Collaborative Domain Modeling

The Power of EventStorming: A Real-World Example of Collaborative Domain Modeling

ByJurgen Stillaert

EventStorming is a powerful collaborative process that fosters a shared understanding of the domain between domain experts and developers, leading to refined and accurate models. By focusing on developing a ubiquitous language and engaging in iterative design, teams can drive effective software development.

Standing on the Shoulders of Giants: The Importance of Relying on Widely Known Principles in Software Development

Standing on the Shoulders of Giants: The Importance of Relying on Widely Known Principles in Software Development

ByJurgen Stillaert

By adhering to widely known principles like Object-Oriented Programming (OOP) and SOLID, software development teams can leverage the collective wisdom of the industry, resulting in improved code quality and maintainability. Embracing these established practices promotes greater efficiency, easier onboarding, and enhanced collaboration among team members.

Revolutionize Your Software Development: The Benefits of Engaging an Experienced External Software Architect
|

Revolutionize Your Software Development: The Benefits of Engaging an Experienced External Software Architect

ByJurgen Stillaert

Engaging an experienced external software architect can revolutionize your software development process by restructuring teams, introducing new techniques, and fostering continuous improvement. Leveraging their expertise can lead to improved software quality, faster time to market, increased innovation, and enhanced team morale.

Leverage Team Topologies to Build Better Software: A Guide to Enhancing Collaboration and Efficiency

ByJurgen Stillaert

Team Topologies offers a framework for organizing software development teams, fostering collaboration, streamlining communication, and promoting continuous improvement. By applying its principles, organizations can build better software, improve development processes, and create well-defined team structures that align with business domains and optimize for scalability.

Rethinking the Single Responsibility Principle: Understanding the Modern Interpretation
|

Rethinking the Single Responsibility Principle: Understanding the Modern Interpretation

ByJurgen Stillaert

The modern interpretation of the Single Responsibility Principle (SRP) focuses on aligning modules with specific actors, emphasizing that “a module should be responsible to one, and only one, actor.” By adopting this actor-based approach, developers can create software systems that are more maintainable, modular, and easier to understand.

EventStorming: A Versatile Approach to Collaboration Beyond Development Teams
|

EventStorming: A Versatile Approach to Collaboration Beyond Development Teams

ByJurgen Stillaert

EventStorming’s versatility extends beyond software development teams, offering valuable benefits to diverse stakeholders within an organization, such as business analysts, product owners, UX designers, QA teams, and organizational leadership. By promoting collaboration, improving understanding of the business domain, and supporting efficient decision-making, EventStorming has the potential to drive innovation and positive change at all levels of an organization.

|

Debunking the Myth: Why a Software Architect Doesn’t Need the Deepest Technological Knowledge

ByJurgen Stillaert

A software architect’s success relies not only on in-depth technological knowledge but also on strong communication, collaboration, and decision-making skills. Embracing a generalist approach allows architects to create robust software solutions that align with the organization’s goals and leverage the development team’s collective expertise.

Software Architecture: The Intersection of Code, Collaboration, and Team Building

Software Architecture: The Intersection of Code, Collaboration, and Team Building

ByJurgen Stillaert

Software architecture involves not only the technical design of software systems but also building and nurturing a collaborative team that can effectively execute the architectural vision. Recognizing the importance of both code and team building is crucial to creating successful, maintainable, scalable, and reliable software solutions.

EventStorming: Exploring the Socio-Technical Dimensions of Collaborative Software Development
|

EventStorming: Exploring the Socio-Technical Dimensions of Collaborative Software Development

ByJurgen Stillaert

EventStorming’s socio-technical aspects foster a positive work culture within software development teams by promoting collaboration, innovation, and shared ownership. By focusing on the human side of the process, EventStorming enables more effective and efficient software development through improved communication, knowledge exchange, and team dynamics.