HackerTube 中文?

Maybe Not - Rich Hickey

ClojureTVYouTube ↗

Further reading 1

Does splitting code actually split its dependencies? →Start with a rule that sends an email. Separate deciding from doing, then inspect layers, objects and abstractions: which parts must still change together when the rule changes?This video helps answer · Do separate layers really separate concerns?

Caption notes

Whether information is required depends on a use case. Describe the extensible shape of data separately from the demands of a particular caller.

Original passages · 6
an easing of requirements should be a compatible change
Maybe Not - Rich Hickey · ▶ 8:40–9:21
it's a mistake to put optionality in aggregate definitions
Maybe Not - Rich Hickey · ▶ 30:36–31:48
addresses are optional but if you give me an address you have to give me a whole address
Maybe Not - Rich Hickey · ▶ 44:29–44:39
this is just minimal requirements you can always have more stuff
Maybe Not - Rich Hickey · ▶ 47:13–48:07
information in a certain context so when
Maybe Not - Rich Hickey · ▶ 4:03–4:11
schemas just because the contexts are
Maybe Not - Rich Hickey · ▶ 33:32–33:38

Hacker News comments

View original on HN ↗