Reasons & Ways to Improve Code Quality • Venkat Subramaniam • GOTO 2021

The function length it does matter but its by use case and responsibility. Game programming and embedded systems, its very common to see long functions because they are trying to avoid adding to the stack and increasing performance. This is the minority though but an example use case. Another example is writing a function which has a long body, abstracting out the parts doesn't provide any additional readability, doesn't reduce complexity and doesn't provoke DRY. To me 100% its use case dependent....

Cvdcxxx

GTÞN
L0I678l

Q2⅗

No

yes

no

Tomorrow usp

Nice to see Venkat doing some Vim!

awesome presentation! thanks

When I see Venkat, I just like the video because I know it going to be awesome.

Perfect it was! _

This is absolute amazing session
Loved it ❤🙌

This was the presentation he made in the year 2009, but published after 12 years!? Slide for Avoid primitive obsession shows the date as 09/30/2009 at the bottom right!

very good

Venkat is a brilliant presenter, as always!

I really enjoyed the example of the "Avoid primitive obsession". Even though streams and functional programming is not new in Java, still it's not the first natural approach to solve a problem for me. Sometimes I know a code can be improved in this fashion but that requires to slow down and revisit the available methods. I'm learning little by little that is the best. Instead of priding myself for ending something fast, it's better to feel well because I know the code looks better.

Venkat great as always!

"Class Names" - I hate when presentations like this assume modern class-based object-oriented programming. My first law of programming is avoiding class-based OOP or you'll have to start by implementing the "Atom" class to avoid duplication. Save yourself the trouble and reach for the functional approach from the start.