I see that he has put a lot of effort into extracting methods and naming things but at the same time I do thing it is an useless exercise. Having a lot of methods means people will not know what the code actually does when it calls a method. So they have to go read the method definition to figure it out. Then reconstruct the mental image. Then proceed to read at the "main" code. I have to work with a ton of code written by other people, daily... and the more methods they defined the harder it is to actually reason about the code. My personal experience that it is far better to ONLY extract a method when you need to reuse the code in like 3+ places. Anything else is needless "obfuscation".
Very good talk, poor audio quality. Why not recording the stage feed directly instead of leaving a mic in the bookstore?
I see that he has put a lot of effort into extracting methods and naming things but at the same time I do thing it is an useless exercise. Having a lot of methods means people will not know what the code actually does when it calls a method. So they have to go read the method definition to figure it out. Then reconstruct the mental image. Then proceed to read at the "main" code. I have to work with a ton of code written by other people, daily... and the more methods they defined the harder it is to actually reason about the code. My personal experience that it is far better to ONLY extract a method when you need to reuse the code in like 3+ places. Anything else is needless "obfuscation".