Naming in DDD

Naming is one of the hardest things to do when coding. It helps us to make the code more readable and comprehensible. When you try to make code readable there are some existing rules but are they compatible with DDD ?

DDD and Naming share a common goal of helping communication between team members. In this Lighting Talk we will explain some concepts like Supple Design and Naming as a Process (@arlobelshee) to achieve this goal.

Transcript

1. Naming in DDD “express your intentions in your code” @SepNamdar @KhaledSouf
2. Who we are? SEPEHR NAMDAR @SepNamdar @DDD_Iran @SHODOioFR
3. Who we are? KHALED SOUF @khaledsouf @SoCraTes_CA @Livifrance/@KRYcare @ScRomandie
4. ‘There are only two hard things in Computer Science: cache invalidation and naming things.’ Phil Karlton @SepNamdar @KhaledSouf
5. What is the naming? ‘specify (a sum, time, or place) as something desired, suggested, or decided on’ Oxford languages @SepNamdar @KhaledSouf
6. Naming is @SepNamdar @KhaledSouf • A team activity • A set of rules • A tool to communicate Collaborative Modeling
8. “A specification / title / index for a thing to understand what it does without going deep inside it.” our humble definition Naming is @SepNamdar @KhaledSouf
9. Why naming? ‘Programs are meant to be read by humans and only incidentally for computers to execute.’ Donald Knuth @SepNamdar @KhaledSouf
10. Why naming? @SepNamdar @KhaledSouf
11. How to name ? @SepNamdar @KhaledSouf “Conceptual Contour”
12. What is the intent ? @SepNamdar @KhaledSouf
13. What is the intent, now ? @SepNamdar @KhaledSouf
14. What is the intent, now ? What is the intent of the system (expressed as names) What are the use cases (expressed as verbs) All technical stuff @SepNamdar @KhaledSouf
15. Repository BookRepository BookCollection 1 2 Books 3 Suffix Repository Suffix Collection Plural Library 4 Domain term @SepNamdar @KhaledSouf
16. Repository BookRepository BookCollection 1 2 Books 3 Suffix Repository Suffix Collection Plural Library 4 Domain term @SepNamdar @KhaledSouf “Intention-Revealing Interfaces”
17. Repository Implementation BookRepositoryImpl MongoBooks 1 2 BookData 3 Suffix Impl Prefix Type Plural @SepNamdar @KhaledSouf
18. Repository Implementation BookRepositoryImpl MongoBooks 1 2 BookData 3 Suffix Impl Prefix Type Plural @SepNamdar @KhaledSouf
19. Repository Implementation BookRepositoryImpl MongoBooks 1 2 BookData 3 Suffix Impl Prefix Type Plural FakeBooks InMemoryBooks HttpBooks FileBooks @SepNamdar @KhaledSouf
20. Infrastructure Service RecruiterInfra or RecruiterMapping or RecruiterXXX Recruiters 1 2 RecruitersCalendar 3 Technical Suffix Plural Domain Term @SepNamdar @KhaledSouf
21. Infrastructure Service RecruiterInfra or RecruiterMapping or RecruiterXXX Recruiters 1 2 RecruitersCalendar 3 Technical Suffix Plural Domain Term @SepNamdar @KhaledSouf “Intention-Revealing Interfaces”
22. Application Service InterviewService PlanInterview PlanInterviewAction or PlanInterviewUseCase Suffix Service Domain Term Suffix Action/UseCase 1 2 3 @SepNamdar @KhaledSouf
23. Application Service InterviewService PlanInterview PlanInterviewAction or PlanInterviewUseCase Suffix Service Domain Term 1 2 3 @SepNamdar @KhaledSouf Suffix Action/UseCase
24. Domain Service PlanInterviewService InterviewPlanifier 1 2 Suffix Service Domain Term @SepNamdar @KhaledSouf
25. Domain Service PlanInterviewService InterviewPlanifier 1 2 Suffix Service Domain Term @SepNamdar @KhaledSouf
26. Naming smells @SepNamdar @KhaledSouf
27. 1 - Make UL pronounceable @SepNamdar @KhaledSouf
28. 2 - Incoherent names - addServer() - addReceiver() - addSatellite() - putSignal() @SepNamdar @KhaledSouf
29. 3 - Technical names in Domain - class AbstractCar - List<String> carList - class PlayerImpl @SepNamdar @KhaledSouf
30. 4 - Mixing contexts Sourcing - Skills - Source of Contact Candidate @SepNamdar @KhaledSouf
31. 4 - Mixing contexts Sourcing - Skills - Source of Contact Interview - Skills - Name - Experiences - Soft Skills @SepNamdar @KhaledSouf Candidate
32. 4 - Mixing contexts Sourcing - Skills - Source of Contact Interview - Skills - Name - Experiences - Soft Skills Contracting - Name - Address - Social Number - Salary @SepNamdar @KhaledSouf Candidate
33. 4 - Mixing contexts Sourcing - Skills - Source of Contact Interview - Skills - Name - Experiences - Soft Skills Contracting - Name - Address - Social Number - Salary @SepNamdar @KhaledSouf Candidate Candidate Candidate
34. 4 - Mixing contexts Sourcing Someone found on a recruitment network with a CV that matches search criteria Interview Someone who should be evaluated by a technical recruiter Contracting Someone who passed his interview successfully and will be integrated to the company @SepNamdar @KhaledSouf Candidate Candidate Candidate
35. 4 - Mixing contexts Sourcing - Skills - Source of Contact Interview - Skills - Name - Experiences - Soft Skills Contracting - Name - Address - Social Number - Salary Prospect Candidate Employee @SepNamdar @KhaledSouf Prospect Candidate Employee
36. 7 - Translate Ubiquitous Language @SepNamdar @KhaledSouf
37. Domain Model Final word @SepNamdar @KhaledSouf Ubiquitous Language Expressed as Documentation Expressed as Conversation Expressed as Diagram Expressed as Code The Truth
38. ‘if you want me to talk for 60 minutes, give me 5 minutes to prepare; if you want me to talk for 5 minutes, give me a few hours to prepare’ Vaughn Vernon - Domain-Driven Design Distilled @SepNamdar @KhaledSouf Final word
39. @SepNamdar @KhaledSouf Any question?
40. - https://www.digdeeproots.com/articles/naming-as-a-process/ - https://opus.ch/ddd-concepts-and-patterns-supple-design/ - https://opus.ch/ddd-concepts-and-patterns-supple-design-2/ @SepNamdar @KhaledSouf Resources
41. @SepNamdar @KhaledSouf نوﻧﻣﻣ