Polly want a message Sandi Metz
Vložit
- čas přidán 2. 06. 2024
- Sandi Metz explains what object-oriented programming wants, using straightforward examples to indoctrinate you into object-oriented thinking. You’ll be raring to write loosely-coupled, message-centric, small-object object-oriented code that isolates conditionals and leans on polymorphism. Once you understand object-oriented programming's natural affordances, everything becomes easy.
wow did i just watched the full 40 mins. Interesting talk I guess I finally understood that polymorphism means addapting to the same api.
It's just wonderful. So clean, easy to understand, ... Congratulations!
Thanks for sharing Sandi, I love your work!
Great talk, Sandi, thank you :-) !
I enjoyed this talk and I like having these examples that clearly show what's wrong and how to fix it. These are not OO patterns, though. You can do all of this in any functional language and even in C with function pointers. And if you are choosing between just two choices then I really must wonder how much better a class/function is compared to an if condition. You can still take out the if condition from the original function and put it in its separate function/class/whatever you like. Your code will be much faster and you'll concentrate more on what actually needs to get done
This information is pearl. I regret I didn't know it in the beginning. How much terrible code wouldn't be written. Thanks
Go ahead, make my day. And you did, Sandi! I will forever more be referring OO noobs to this video, and most especially _Procedures vs OO_ (at time 6:00 ). This gem should be on StackOverflow with its own tag - "OO Zen".
People don't say "I can't write code like this" because they don't trust the objects to do the right thing. They say it because abstractions don't always remove cognitive cost, sometimes they add it. The cognitive cost is added when the roles are chosen poorly: people don't know what a justifier is, or what a subsetter is, or what a source is. These ad-hoc abstractions are a product of the programmer's mind and have to be carefully documented and explained once introduced.
I have just found out that Sandi makes a CZcams channel. Please keep posting amazing work, Sandi...
I like the idea that OO affords certain styles of programming.
Thanks for Sharing This.
Really good, thank you Sandi :)
I loved it. Thank you very much for this
I found this refreshing. Thanks Sandi, for sharing your wisdom. Where's Part 3 and 4?
I think she misspoke a little when she said "part 2". Parts 1 - 3 of her original numbering are part 1 in the misspoken numbering. Part 4 is the part 2 she misspeaks.
You need a Factory to get Parts 3 and 4. ;)
Great talk!
Fantastic talk, well researched and explained but I think one mistake on the code. At 36:32 you can see .new(...).lines -> each sub-class calls 'lines'. At 37:00 when that logic is moved to the factory the .new does NOT call lines on the sub-classes. Hence the factory will return an instance of the subclass, and not the result of calling lines as before. At 37:16 you say it will 'give you back the right thing' but actually it will give you back the class instance, and not the result of calling lines. Because Clump.lines is calling the factory lines method, not the sub-class lines method.
New calls lines of subclass, actually. So no mistake here
Welp my whole program is a death star lol
She never mentioned where do you call Listing class, in a script? in another method? in a factory?
Watched this 3x and while sometimes OO seems contrived what you've spelled out is such reprieve
Ayy my name is sandi! and why it 40 mins? why don't u play ronblox