A whistle stop tour of many complex topics. I found some of them complex and hard to understand. Not many reasons why these are good ideas beyond 'because bugs'
I loved this talk - although I don't think I'm going to implement all of the practices detailed in the talk, it definitely gave me some food for thought and made me think of ways I could write better, cleaner, less ambiguous code.
I found some points I understood but I couldn't really see the advantage in doing them vs the disadvantage. Maybe if I maintain a large ojn going project in the future more of this will make sense. Still gave lots ot think about and bits that I can use straight away to improve my coding practises.
Marco is an extremist programmer (in a good way). he expounded fluently on
the importance of code path testing, type checking, immutability, optional
dependency avoidance and other subjects.
Some really far out views for coding practices, but delivered with the point that you don't have to practice all/any of them. If you want to give your code extra safety with what you write, I can not suggest this talk enough. Being an extremely defensive programmer is a great practice and he gives great examples why.
While they were mostly more extreme examples of how we can all code more defensively, there were some amazing examples of ways that day-to-day code can be hugely improved and made more resilient.
I'm already putting the things I've learned into practice and Marco presented his talk in an engaging, interesting and educational way.
Talk of the day! Really enjoyed this. Gratified to see there's a lot here I already do, and picked up several new tricks. Can't say anything bad about this talk!
Comments
Comments are closed.
Nice talk Marco, I will be reviewing your slides to see where I can improve my coding practices.
Really good talk, every developer needs to follow the practices mentioned in this talk.
A whistle stop tour of many complex topics. I found some of them complex and hard to understand. Not many reasons why these are good ideas beyond 'because bugs'
I realised I had already seen this talk, yet it's still relevant, useful and absolutely brilliant. Hurray!
I loved this talk - although I don't think I'm going to implement all of the practices detailed in the talk, it definitely gave me some food for thought and made me think of ways I could write better, cleaner, less ambiguous code.
I found some points I understood but I couldn't really see the advantage in doing them vs the disadvantage. Maybe if I maintain a large ojn going project in the future more of this will make sense. Still gave lots ot think about and bits that I can use straight away to improve my coding practises.
Marco is an extremist programmer (in a good way). he expounded fluently on
the importance of code path testing, type checking, immutability, optional
dependency avoidance and other subjects.
Some really far out views for coding practices, but delivered with the point that you don't have to practice all/any of them. If you want to give your code extra safety with what you write, I can not suggest this talk enough. Being an extremely defensive programmer is a great practice and he gives great examples why.
Some really interesting points made. Very enjoyable talk. Thanks Marco :)
While they were mostly more extreme examples of how we can all code more defensively, there were some amazing examples of ways that day-to-day code can be hugely improved and made more resilient.
I'm already putting the things I've learned into practice and Marco presented his talk in an engaging, interesting and educational way.
Bang on the nail.
Nothing to add, nothing to subtract.
Talk of the day! Really enjoyed this. Gratified to see there's a lot here I already do, and picked up several new tricks. Can't say anything bad about this talk!