veyepar: Error handling without fear

Author(s):	Martin Matusiak
Location	Room 106
Date	aug Sat 13	Days Raw Files
Start	15:00	First Raw Start	error-in-template
Duration	0:30:00	Offset	None
End	15:30	Last Raw End
Chapters
Total cuts_time	None min.

https://2016.pycon-au.org/schedule/80/view_talk
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Error_handling_without_fear.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

If you're like most developers you have a difficult relationship with error handling. You try to do "enough of it" to make your code work, but fundamentally errors make you uncomfortable and you want to avoid them as much as possible.

This is a logical reaction to errors when we first started programming - most errors were mistakes in our programs. But as you mature as a programmer errors are increasingly circumstances outside your control, and good error handling is essential to writing good code. It is the part of the iceberg under water.

This talk will teach you how to accept errors as something that is natural in any program and how to start thinking about error handling as part of "what your program really is about", rather than being a chore.

We will look at common classes of errors in domains like input validation, using libraries, and managing disk and network io operations, and discuss appropriate error handling strategies in each case. We will also discuss what kinds of errors we shouldn't try to handle at all, and why.

Finally, we will talk about how to approach testing error handling code and the pitfalls of overly clever error handling.

Comment:

production notes