Let’s Set the Records Straight

[@jackfrosch]

Even when I think I understand a topic well, Venkat always manages to bring me to a deeper understanding. Thanks, my friend!

[@gauravaws20]

i dont even program in java anymore but I never miss a session from Dr Venkat. Thank you sir.

[@ЮрийШотин]

100% agreed that Java record perfectly works as a tuple. We are already using this approach in our production code.

[@nasamind]

Happy to see you sir..

[@mehmoodrehman6336]

Excellent session very detailed

[@bulelanibotman]

I finally understand some of the concepts of Records but got lost in the constructors, I need to rewatch that section only

[@AtulKShrestha]

How do we handle a situation where I have, let's say, 10 or more attributes? It is error prone to use it with a constructor. Should we then create a builder inside record to help with object creation? Would that not be verbose or is that the best option? With lombok and DTO we can use @Value and @builder to achieve immutability and builder but I understand then we are depending on Lombok which we like to avoid when possible for the reason you mentioned in the video.

[@terteseamos579]

Thank you this was very details

[@avalagum7957]

Dr Venkat's mustache is bigger/thicker than before 🙂

[@brooksfire9580]

He's just happy to see you, avalagum7957 :)

[@bdeva029]

IntelliJ video where the speaker is using Vim hahahahaha

[@vijayjangid8967]

❤

[@adambickford8720]

Pragmatically, records aren't even close to lombok. Once they get pattern matching it'll be different, but right now records are mostly a subset of lombok.

[@raven8brain]

5:19 😂