Please log in to watch this conference skillscast.
Naming is hard. Teams who write software often give rather technological names to the components they write. This is a problem because it makes the system less understandable and more difficult to extend. I propose to show more respect to the language that the users and other domain experts speak because it will allow us to think as they think which will make our software more compatible with the users’ mental models. Let’s call the modules, components, interfaces, services and entities as business-friendly and technology-neutral as possible and use some patterns from Domain-Driven Design to achieve an architecture that is well-structured, easy to explain and maintain over the years. It’s a matter of attitude and attention, folks!
YOU MAY ALSO LIKE:
- Domain Models in Practice with Marco Heimeshoff (Online Workshop on 6th - 10th June 2022)
- Domain-Driven Design in Practice with Michael Plöd (Online Workshop on 20th - 22nd September 2022)
- Product Elevation Conference 2022: Online (Online Conference on 9th - 10th November 2022)
- Product Elevation Conference 2022: In-Person (in Dublin on 9th - 10th November 2022)
- LDN Talks May 2022 - Quickwit Takeover (in London on 30th May 2022)
- Software Architecture in a DevOps World (SkillsCast recorded in February 2022)
- Understanding Microservices: A Guide for the Monolithic Developer (SkillsCast recorded in October 2021)