I had a interview test about 2018. Their solution was classic strategy mine was a 1 line lambda...Patterns were often countering limitations in the old java. Unfortunately, devs often still write this old style java as they do not know about latest function support.
The individual is encouraged to adopt a practice of sincere empathy towards both their RAM and the GC. Such consideration has the potential to significantly improve the system's performance and overall efficiency. The notion of embracing this approach is highly appreciated.
Oh, the statement above is not solely focused on the GC, rather, it encompasses the entire virtual machine of this particular computer programming language.
The purpose of decorator pattern is to add new behavior to existing object dynamically, but refactored solution with Function(s) look more like chain of responsibility/strategy, not decorator.
The funny thing is that, he had to prepare all of these specifically for the presentation, he probably never used any of this in his projects LMAO, because most devs would not understand it and the maintainability of the application goes down. Can confirm i've been developing production grade software for 7 years and never used any of these lambda shenanigans. You will mostly only use lambdas in streams and api methods that take lambdas as arguments, you will pretty much never be abstracting away stuff by creating your own predicates and functions.
Congrats, you just realized that talks like this have examples. Everything he said has been an irl problem before ... That's why design partners are a thing. Most design patterns won't even exist if java has a proper type system. Idk why java devs hate change. My OOP prof that taught java docked marks for using records that have been out since java 14 or so. Y'all need to get with the times lmao
"code should reflect empathy" - the best take ever!
I had a interview test about 2018. Their solution was classic strategy mine was a 1 line lambda...Patterns were often countering limitations in the old java. Unfortunately, devs often still write this old style java as they do not know about latest function support.
this so true
The individual is encouraged to adopt a practice of sincere empathy towards both their RAM and the GC. Such consideration has the potential to significantly improve the system's performance and overall efficiency. The notion of embracing this approach is highly appreciated.
Oh, the statement above is not solely focused on the GC, rather, it encompasses the entire virtual machine of this particular computer programming language.
If you want to learn the art of teaching, follow sir "Venkat Subramaniam"
I Thoroughly enjoyed the entire talk, thank you for sharing!
This was a great talk. Thanks for sharing!
The last pattern also called Facade Pattern
So cool! Thx!
The purpose of decorator pattern is to add new behavior to existing object dynamically, but refactored solution with Function(s) look more like chain of responsibility/strategy, not decorator.
Venkat has no shoes on? 😲
No. He's a guru 😆
11:57 this guy does copy and paste in vim using ctrl+c and ctrl+v? mapped?
you can only do this if you have no shoes ;-D
The funny thing is that, he had to prepare all of these specifically for the presentation, he probably never used any of this in his projects LMAO, because most devs would not understand it and the maintainability of the application goes down. Can confirm i've been developing production grade software for 7 years and never used any of these lambda shenanigans. You will mostly only use lambdas in streams and api methods that take lambdas as arguments, you will pretty much never be abstracting away stuff by creating your own predicates and functions.
Well if you don't, you should, as long as developers understand it, maintenability actually goes up.
Congrats, you just realized that talks like this have examples.
Everything he said has been an irl problem before ... That's why design partners are a thing. Most design patterns won't even exist if java has a proper type system.
Idk why java devs hate change. My OOP prof that taught java docked marks for using records that have been out since java 14 or so.
Y'all need to get with the times lmao
”not to ever trust a feature with the word 'management' in its name"
the intro is so loud and want to breaks my ear as well. please decrease it tho.