36:18 Would be fantastic if these null checks were unnecessary but in huge, complicated, legacy system developed over almost 20 years (2005 are first commits to repository I'm thinking about), I never know where from null can come about. It's not only a thing of direct method calls which may be only in one, two or three other places. The null may be passed through several calls, from method to method. I've seen too many cases of NPE happening in production environment to leave possible null unattended. Clean code is fine but I prefer client who isn't screaming into his phone because users can't do something essential to their work all day (until hotfix comes up).
I always learn something from Martin's talks.
What an amazing talk! I wish there were a great load of recent ones from Martin.
Great talk. I really liked the energy introduction. It's great to see software engineer understand that their code exist in the real world.
36:18 Would be fantastic if these null checks were unnecessary but in huge, complicated, legacy system developed over almost 20 years (2005 are first commits to repository I'm thinking about), I never know where from null can come about. It's not only a thing of direct method calls which may be only in one, two or three other places. The null may be passed through several calls, from method to method. I've seen too many cases of NPE happening in production environment to leave possible null unattended. Clean code is fine but I prefer client who isn't screaming into his phone because users can't do something essential to their work all day (until hotfix comes up).
I'm with you on that one. Assert (design by contract) are a live saver
Fantastic Talk
fantastic talk!
InstaBlaster...