Writing The Next Great Kotlin Novel
summary
Compares concrete Kotlin patterns to English-writing rules and gives actionable guidance: use infix functions for readable tests, avoid sprinkling them everywhere because of precedence and tense confusion, prefer sealed classes to encode state plus cause (example: Vader dead → include killer), treat scope functions as conjunctions not magic (watch nullable safe calls and chaining pitfalls), favor constructors or simple chaining over custom DSLs unless maintenance cost is justified.
AI-written summary · about
chapters (19)
- 0:00Start
- 0:25My vision: I'll read books about writing
- 2:12Natural language depends on context
- 2:52Natural language is ambiguous
- 6:05Kotlin falls in the middle
- 6:47This is not a programming talk
- 7:16The official Kotlin style guide
- 8:08Naming
- 8:32Choosing good names
- 9:18The optional feature
- 10:54Infix functions
- 11:34Infix: custom
- 13:03Why not infix everywhere?
- 14:11Great use: testing
- 14:42The passive voice
- 16:07The evasive voice
- 25:34Custom DSL (Domain Specific Language)
- 26:27Can you have too many custom DSLS?
- 27:44Beyond the style guide
