Комментарии:
I can't find Kent's definition of coupling and cohesion in structured design.
ОтветитьI can't find this definition of coupling in structured design
ОтветитьGreat talk. Looking forward to the books. Loved the Powell's Book store shoutout!!
ОтветитьOne of the best talks I've ever listened to. The description of coupling and cohesion was Correct, Understandable, and Terse. Sometimes you can get all three 😄
ОтветитьEasily watched at 1.25 speed :)
ОтветитьGreat talk, thanks
ОтветитьBoring. Lifecoaching becomes a valid excuse when there is no engineering.
ОтветитьAnother brilliant talk from the legend.
ОтветитьGreat talk, looking forward to the books! Separating the behavioural and structural changes feels like another way to look at TDD in the green and refactor cycles, or possibly even an iteration on the TDD flow with red - refactor (tidying first) - green - refactor?
Ответить"Im glad I made it" lol...
ОтветитьHe should be writing the 3rd book first because that is what helps in identifying what changes come in.
ОтветитьWhat a wonderful talk! Thanks Kent Beck! 🤩
Ответить"Why are we still putting source code in files?"
"Compared to what?"
I liked the highlight that coupling/cohesion are respective to changes.
ОтветитьA beautiful talk.
I have one question (nitpick?). Since coupling is defined wrt a delta, and cohesion is defined as an entity A whose components are coupled, it seems to me no easy thing to determine if A is cohesive since the space of possible changes is so large. Maybe this doesn’t matter in practice since the idea is to reduce cost of coupling by moving coupled components closer together (increasing cohesion)?
Also you ask why we keep code in files - what is better alternative?
Best talk on software design I’ve seen
Ответить