Naming Things

Just a Spec

Ah yes, that notorious hard problem in computer science. Time to name some things as we talk abut the philosophy undergirding software development, why “naming things” is hard but also a core aspect of the job, the sometimes reluctance to name things in as disciplined a fashion on the frontend as on the backend, how to communicate across teams and stakeholders via Ubiquitous Language, the importance of embracing modern HTML & CSS semantics when naming things, and so much more.
Hosted by Jared White & Ayush
Links:

• Follow up: Playwright E2E testing
• TwoHardThings
• UbiquitousLanguage
• Classnames (Naming things needn’t be hard)
• How to Think Like a Framework Developer
• Adam Wathan on "vanilla" CSS
• Vanilla Breeze
• The Design System Ecosystem

챕터

1. A Brief Message (00:00:00)

2. Introduction (00:00:45)

3. Follow Up (00:04:44)

4. Two hard problems of computer science (00:06:29)

5. Naming things…sometimes it feels like that's all we do! (00:07:34)

6. Ubiquitous Language (00:12:48)

7. Domain modelling for the frontend (00:17:47)

8. Tech works like fashion? (00:21:56)

9. Readability of code more important than ease of writing it (00:23:20)

10. Productivity != Good Quality (00:24:55)

11. You can get help with naming things! (00:26:16)

12. A thesaurus is your friend (00:28:56)

13. Bad ideas lead to good ideas (00:32:28)

14. Thinking like a framework developer (00:35:03)

15. Runes (00:36:02)

16. Bad faith examples of (bad) vanilla CSS (00:37:29)

17. Sensible use of utility classes (00:42:05)

18. Pour one out for BEM (00:47:13)

19. A CSS Architecture course is imminent! (00:50:17)