“In this world nothing can be said to be certain, except death and taxes.” Software developers have a third certainty. Bugs.

Regardless of experience and skill level, all developers introduce bugs into their code. The longer these bugs fester, the more expensive the consequences of them become. So to improve the quality of our software we need to find bugs fast, ideally before they even end up entering the codebase.

This talk is aimed at beginner to intermediate level software developers. It introduces the concepts: type hints, assertions, and value objects. We'll then look at how these techniques can be combined with modern IDEs to:

* reduce the chance of introducing bugs
* minimize the cost associated with any bugs that do slip through the net
* safely refactor code so we can rename classes, methods, and variables to be more explicit

This talk will leave you with plenty of tips on how to write cleaner code with fewer bugs. And best of all you can apply them the next time you write code.


Comments are closed.

I liked how he started with poor code examples and worked through them to make them more explicit/fail safe. I also really liked the format of Dave’s talk in that he reiterated the takeaway after each module.

Matt H. at 15:26 on 1 Jun 2018

Another good talk by Dave. Lots of good, solid advice for making it easier to see bugs in your code by following general best practices.