11 years later this presentation still holds up! Great delivery of some very interesting and informative material!

I'm not gonna lie, I have 3 years of OO experience with Ruby, that's the third time I'm watching this video and I'm still learning.

Open HiHat 4 Real!!

The B1G Man!! Respekt

"Try catch was a mistake" exactly what I needed to hear

Hey it's the tau guy!

Very good talk on Go

Great talk, worthy of every Rails dev time. 9:30 The liberating realization that resources need not map 1-to-1 to models. You can have actor-specific "window" resurces into underlying data, or PORO-backed resources (SessionsController). 18:11 Derek touches on DDD's Ubiquitous Language idea as a rule to help disambiguate what #process action might be doing. An alternative approach could be to use another powerful tool from DDD - actor analysis, i.e OrdersController is probably too generic and then the ShipmentsController also. Shipping where, between warehouses, to customer? An actor-identifying namespace might be missing - Inventory::OrdersController etc. 18:58 Welcome to controller hook hell. Derek touches on this being bad, but does not go into how to make things better. I do dev.to/epigene/stop-abusing-beforeaction-48di 34:20 ""There's no reason a collection of objects can't be a resource". Yup, in DDD they're called Aggregates.

spitting fax fr fr

Its wild how every time he gived a talk he works somewhere else

Connascence

There are so many weird symbols in this talk, not as other persons used.

sharp presenter

With the recent advancements in deep learning the state of the art for this topic has hugely changed. Unfortunately or not, Ruby is nowhere near to where the interesting things are happening.

Love this kind of talks

this gives me the chills everytime I watch it

where can be found useActions source?

Bump the viewssss

I come from Theo's video about react native new arch :)

This is the only resource I have found that tries to re-create Angular in a simplified way. Sadly is not the current version of Angular

She swallowed the spider to catch the fly.

Sandy Metz🥰 i'm in love!! since i read his book Practical Object-Oriented Design. I still think about her whenever i heard the term Ruby or smalltalk. Really 😁

Seems like a lot of complication. I never really went for it. The only selling point to me was replay ability. However the extra complication isn't worth it.

This is a great talk and give me insight of object oriented programming design.

Goodlord! I got like 5 ads on this video.

It is HTTPoison not HTTPotion!

I was at this talk. It always felt like magic when Jim Weirich explained something to you, seemingly Gandalf had just whispered a spell in your ear that let you understand things beyond your own comprehension. What a teacher!

Amazing talk! Thank you for sharing the experience

Thanks for posting this

Btw, parent_of has been deprecated and returns an empty array until they remove it.

The Patrick meme is what finally made it all click. I finally get it.

I keep coming back to this.

Growing up in Madison I was lucky enough to be there when CS resettled in MadTown. As a young kid drumming, I took several lessons with the man. Still working on getting it down Boss. Miss you.

The question I needed more answers on was the processor to worker count, and you gave very little. Thanks for the memory information though. It confirmed that I our application setup correctly. Chugging along serving about 150k users. Almost zero maintenance required.

Thanks for the video. I have been learning a lot with it.

🔥🔥🔥

RIP friend

Nice topic, well explained

Interesting talk, but I have one question. Whyyyyy???

Much love to Sandi Metz work ! A really great talk !

Cool speech and presentation. It helped me to manage memory leak in my project, thank you

nice talk thanks for the knowledge.

Similar path but started later. It's been a fun ride so far.

I've been on the fence about whether to invest the time to learn Scala. Glad I can mark that one off now.

funny talk, really interesting to listen

i prefer "virtual mocks", which simply assert the expected behavior happened. e.g. if a file is deleted, don't say expect(File).toReceive('rm').with('myFilePath.txt'), but instead just say expectFileToBeDeleted('myFilePath.txt') -- it's no more verbose to write but it completely decouples you from implementation details.

you shoulddn't test "within delta". your tests should be deterministic so you know _exactly_ what value to expect.