14.43 method ending with a c :) looks like a typo. would prob rename it to customer and type a return customer even though it is not needed make the code clear to understand?
Yes, you do it for the first few days or weeks, until you're used to it. I preferred to write explicit EventListeners in Java, until it was so familiar, that I preferred the anonymous ad hoc style.
15:07 ha has been using c for Customer and p for Person then in the trait CustomerRepo he uses p for Customer :p that is why we should always name variables properly
registerCustomer also violates command / query separation ? and it is interesting how the method is called register customer then calls save customer inside :)
Countless times he avoided "spring framework " Annotation based framework, framework using reflections, rest controller and service , dependency injection, DI based framework 😂😂😂
I will be very happy when next fashion communication visual idea will be more efficient by just use 100% of screen to target the interest of subject (the code), instead of use less than 20% for targeted subject and 80% for decoration and kind of human chatterbox. This world actually is more like appearances more then reality and efficiency.
Oh yes. Higher kinded types. We learnt all about them in kindergarten. It was just after we started learning category theory, but before the algebraic geometry.
Amazing talk, puts everything in order. Thank you!
Fantastic talk! I am a junior in scala and this was illuminating, thank you.
One of the best talk i have seen!
Brilliant. This is exactly what I was missing.
Great explanation, best I’ve heard! Cheers 👍🏻
this guy is a genius
Wow all of those forms of futures... Really glad JS has basically switched everything to native promises for all new things
Excellent distillation, Christopher! Up there with Torreborre and Spiewak. Could you become the next Odersky or Milewski or Martin (presenter wise)?
Nice talk! 👍
Excellent presentation
Amazing talk!!
Such a good talk - thanks.
Brilliant, finally made higher kinded types click for me
Great talk
14.43 method ending with a c :) looks like a typo. would prob rename it to customer and type a return customer even though it is not needed make the code clear to understand?
Yes, you do it for the first few days or weeks, until you're used to it.
I preferred to write explicit EventListeners in Java, until it was so familiar, that I preferred the anonymous ad hoc style.
15:07 ha has been using c for Customer and p for Person then in the trait CustomerRepo he uses p for Customer :p that is why we should always name variables properly
registerCustomer also violates command / query separation ? and it is interesting how the method is called register customer then calls save customer inside :)
This guy is Richard Hendricks in real life
Countless times he avoided "spring framework "
Annotation based framework, framework using reflections, rest controller and service , dependency injection, DI based framework
😂😂😂
Guess I saw a Monad.
I will be very happy when next fashion communication visual idea will be more efficient by just use 100% of screen to target the interest of subject (the code), instead of use less than 20% for targeted subject and 80% for decoration and kind of human chatterbox. This world actually is more like appearances more then reality and efficiency.
lol wut
Beyond the basics.... Proceeds to talk 48 minutes about the most basic sh*it ever.
Yes, I am confused. If someone was coding in Scala, wouldn't he already be doing that? That seems pretty basic to me...
Oh yes. Higher kinded types. We learnt all about them in kindergarten. It was just after we started learning category theory, but before the algebraic geometry.
Great presentation