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

[@GOTO-]

Looking for books & other references mentioned in this video? Check out the video description for all the links! Want early access to videos & exclusive perks? Join our channel membership today: kzbin.info/door/s_tLP3AiwYKwdUHpltJPuAjoin Question for you: What’s your biggest takeaway from this video? Let us know in the comments! ⬇

[@fatihunal5514]

>> 21:30 --> :) :) "I wrote a code and nobody understood" normally not a reason to proud of but personally most of the developers feel like that

[@VolodymyrFrolov]

Venkat is a brilliant presenter, as always!

[@gabosol777]

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.

[@csexton07]

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....

[@roaba3581]

awesome presentation! thanks

[@ruamsawaqas935]

Pool pop pop pppp0pop pop pop Pool pop pop pop pop pop pop pop popo apapo apap April Tara's000pppppppppppppppppppppppp rapidlyppapaa bzy kayaker post 0 post post ppost posts post post post

[@kitkarson4226]

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

[@raghavanaliassaravananm1546]

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!

[@kingscrusher]

There is a 2hour + video here which is also worth checking out for core principles : kzbin.info/www/bejne/op2qmIJtadqLg6s

[@frogery]

that's just the date on the background photo.

[@mahdisalmanzadeh5377]

Perfect it was! *___*

[@saidiann]

very good

[@n1gr082]

Venkat great as always!

[@NisarKhan-kk2vj]

Tomorrow usp

[@rodelias9378]

Nice to see Venkat doing some Vim!

[@web_shivam]

This is absolute amazing session Loved it ❤🙌

[@AmedeeVanGasse]

yes

[@AmedeeVanGasse]

no

[@andrueanderson8637]

"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.

[@wesselbindt]

You sound very smart and experienced

[@360undead]

I do OOP. I have no problem with the paradigm. Maybe you are bad at following the core principles

[@chewbaccarampage]

I recommend watching Anjana Vakil's Coding Across Paradigm's talk on Goto. As long as the OOP is stateless, the difference between FP and OOP are actually quite minimal. At the end of the day, OOP and FP are just tools and they are applicable in the right use cases. Brooklyn Zelenka's The Tyranny of Structurelessness talk advocates for wrapping a FP core with an OOP shell. I think there's some merit to that as well, although I have yet to experience that with a code base.

[@metaltyphoon]

No