Видео

Thank you for this inspiring lecture professor Milano.

Amazing talk, Im currently starting with TDD in elixir I read "TDD with Phoenix" from German Velazco, and I was amazed with how he was capable of develop a chat in real time with auth, room creations and some more, without open the browser, that's the thing which convinced me to start doing TDD in Elixir.

Why has it taken 11 months to get this talk online? How is that possible?

Fantastic talk!

I'm at minute one and totally excited: An Erlang IDE and ELP made by WhatsApp. That's it! Erlang and its Documentation has improved so much over the last couple of years due WhatsApp's contribution. Long live Erlang/OTP on FreeBSD! Long live Joe Armstrong!

At last, an Erlang presentation at code beam. I am actually so done with the Elixir community. These guys gather in a slack instance nowadays… Such a cultural gap. I have no nostalgia for old erlang, but I really prefer the older erlanger…

Now praying to Elixir gods to bring us something like this

link to the presentation, please ?

Flyweight example (ruclips.net/video/agkXUp0hCW8/видео.htmlsi=3dgU7oj2BqaR4I9N&t=2162) misses the point. Flyweight is used for run-time data, not fixed data as is shown in this video.

// z^3 (1..5) ⑂ ISODD

Thanks for this talk and thank for miro board!

This is amazing!

@2:17 that joke was not appreciated enough by the audience :D

Headache! Why not skip Kafka all together?

i was here

Can this be used with sveltekit?

my god. a perfect example of serious play. if only more kids met him, he could spark a revolution in the sciences. we need more joyful and playful academics like him and we need more and more kids to meet this wonderful man.

Very informative to hear about real use-cases, thanks for the talk!

Sasa Juric AND Jose Valim? Two BEAM legends.

That’s my father

I love Quinn’s talks. She is in another level.

Dmitry, thanks for the content.

me after 20 years: DRY matters little, code readability drops, does it actually work goes way, way higher than before. nothing is more important than that, the entire purpose of programming is making things work. you're back at the start, but now you know what rules about readability/dry/whatever rule to ignore and when, so you can always get things that work.

IMO, the ability to co-locate state and logic is one of the main benefits of OOP as it helps to design modules that are cohesive and loosely coupled. The main anti-patterns of OOP are inheritance and pass-by-reference. This is because of 'spooky action at a distance' whereby the state mutation is difficult to trace because the same object reference was held in many different parts of the code. These issues are easily avoided. Ideally, you should aim to pass around information/messages by value instead of passing objects/instances to each other. My main problem with pure FP is that interactions between functions often involve passing around a large amount of state. A lot of unrelated state ends up traversing through unrelated functions. You end up having to invent technical abstractions to manage, split, group and otherwise distribute your state efficiently to where it's needed but this makes logic chains long and difficult to follow. If you want to catch a taxi from A to B, you don't need to bring your own car seat, petrol or steering wheel; the taxi driver is responsible for that. You just give them the message of where you want to go and you trust that they have all the tools and materials (the state) to do their job properly. The taxi driver controls the state. If you don't like the way the taxi does its job, you can substitute it for an Uber or a Bus or a Train... You don't have to worry about whether or not your steering wheel will also fit the Bus. Why do you want to force the taxi to use a particular steering wheel? As a user, shouldn't your primary concern be to reach your destination within a reasonable time? Why concern yourself with the taxi's implementation details/state? Do you need to know what kind of fuel it requires? No. Those things are not relevant to your goal. If you have to bring your own chair, steering wheel and petrol to catch a taxi, it causes tight coupling because you need to know what brands and sizes of steering wheels, chairs and petrol are allowed for that particular taxi... You want to replace the taxi with a bus? Too bad, your steering wheel is too small for the bus... Time for a complete refactoring. Tight coupling. Now you need to call a factory in a different part of the country to manufacture a steering wheel of the right size. The bus' responsibilities are not well defined because a lot of coordination must happen on the outside to supply it with the state it needs to do its job; low cohesion.

Wow. Just. Wow. Cool project, good message :)

I really enjoy the talk, very good and advanced!

Great talk

Awesome work as always Chris! 😍 Doing this in any other language/ecosystem would be 10-100x more code/complexity! 🤯

Hi. I did not get the point. :(

Can't wait for Elextric-next

Actually when the timeout is exceeded for call, johnny is supposed to drop *his* cards on the floor

"I have two cats, called Haskell and Ada". What a legend!

what I got from this is that she learned why formalism doesn't work, modelling is better, specially when its less formal.

I still have no idea what this talk was about.

Wow

This would be so much cooler if my DAU wasn't a Bool....

This was very interesting and inspiring!

18:30 Science and raw data should be free, for the benefit of humanity. Otherwise it turns into religion and ideology.

Fantastic video!! thx for sharing

Should I add small amounts of relevant refactors in my tickets?

FLAME vs AWS lambda bills

thank you! very cool!

This is great but, who the hell is talking in the background?

Objects are modern day types.

Always good to see people do talks on subjects like this. Super important.

Great talk! Is the code for this demo available somewhere?

Awesome!

Thank you very much for this talk Xiang Ji. Very instructive.

26:05

I like this guy's thinking. "We can ask Skynet". LOL