One thing about 22:50 that I have problem with, and I see it a lot in my production code, is naming function based on single context. In this case function is named hasDeliveryDateBeforeWarning and date which is passed is named warningDate. But if variable would be named f.e. discountDate, it would look ridiculous if reused anywhere, because that implies that only warning date can be passed to it, just in this context. To make it more reusable and not wonder about what function does on the inside (what is warning date in different context?) just name it hasDeliveryDateBefore(LocalDate targetDate) which would make predicate more reusable in arbitrary contexts. Thats all for clean code nazi, great presentation as always :)
Aside from the awesome content, can we please talk about how Victor did an absolut excellent job of actually delivering the information? This is some serious skill in teaching, great job!
Very nycc stuff, following from quite a time jst one doubt in last Template Pattern. What we have multiple methods to fill in Email in future ? Were we passing all those methods reference in parameter ?? (Same doubt with passing Runnable in previous example)
Any advices to a junior? Who's seniors and colleges are writing legacy code and "clean code" is considered as "the code which presents no bugs at the time it is written". I will appreciate any suggestions.
One thing about 22:50 that I have problem with, and I see it a lot in my production code, is naming function based on single context.
In this case function is named hasDeliveryDateBeforeWarning and date which is passed is named warningDate.
But if variable would be named f.e. discountDate, it would look ridiculous if reused anywhere, because that implies that only warning date can be passed to it, just in this context.
To make it more reusable and not wonder about what function does on the inside (what is warning date in different context?) just name it hasDeliveryDateBefore(LocalDate targetDate) which would make predicate more reusable in arbitrary contexts.
Thats all for clean code nazi, great presentation as always :)
clean Lambdas!.why so less view? ..its best video!..
Aside from the awesome content, can we please talk about how Victor did an absolut excellent job of actually delivering the information? This is some serious skill in teaching, great job!
Excellent video on writing clean code using Lambdas. Thanks Victor.
Best!!
Very nycc stuff, following from quite a time jst one doubt in last Template Pattern. What we have multiple methods to fill in Email in future ?
Were we passing all those methods reference in parameter ?? (Same doubt with passing Runnable in previous example)
Any advices to a junior? Who's seniors and colleges are writing legacy code and "clean code" is considered as "the code which presents no bugs at the time it is written". I will appreciate any suggestions.
there is no no bugs code! that is why we write test and we have continuous integration....no bugs... hilarious!
Just in case you are searching for github repo here it is. :)
github.com/victorrentea/clean-lambdas-jbcnconf
Thank you very much