Resistant, highly testable, safe and maintainable code: or not?

There are a thousand ways to break your code, and a lot of ways to prevent that from happening.

Let’s explore defensive programming and learn how to protect our code from invalid usage.


Comments are closed.

Iamabot at 14:40 on 28 Jan 2017

Very defensive! Always delivers amazing talks. Another dent in my self esteem as a programmer. Not a fan of mario.

Koen Cornelis at 14:49 on 28 Jan 2017

Great stuff, good presentation.

Defensive practial advice to circle the wagons before making a trainwreck

Very strong message, delivered with a lot of chuckles...

Yep, you did it again, like I didn't question enough things in life.
I might need this presentation every four weeks or so...

Really good stuff!

Great talk!
Very extreme like you said but it makes you think as a developer about what we're doing.

Marco delived again :) . 'nuff said.

Marco delivers extremely good talks. This one was not an exception. Very well brought, to the point, detailed and funny. Thank you!

Niels C at 16:05 on 29 Jan 2017

Really experienced speaker, lots of interesting thinks to take away.

Very good speaker and talk. Awesome topic and with very to the point explanations and examples. Easy concepts with which you can start implementing and improving your code right away!

Muhammed at 22:50 on 29 Jan 2017

It gave me a lot of arguments about certain practices in software development. And mostly valid I belive.

Marco, since the last time I saw a talk of you (already quite some time ago), your English has really improved, it feels natural now!

You managed to give a reasoning behind certain good software development principles, showed relevant examples and made it funny too!

Well done.

Very good content, energetic & humorous delivery. Good balance between broad concepts and practical examples.

Dries Vints at 21:20 on 1 Feb 2017

Amazing talk as always. Didn't agree with all that you said but definitely took some advice from it.

Mario Peeters at 08:04 on 2 Feb 2017

This should have been in the main room.