Technical Lead at Bankwest, Java Developer
Alan is a Technical Lead for Bankwest where he has worked for the last six years. He has been professionally solving, and teaching others to solve, business problems around the world for 20 years, using a variety of languages, but is reasonably happy and vaguely proficient with Java at present. Alan enjoys puzzles and games of all sorts, physics, drum patterns, and is currently trying to solve being a dad.
YOW! West 2014 Perth
Fourteen shades of failure – Exceptions and Exception handling
Exceptions are part of API and system design, but often very little thought is given to the Exceptions that are raised, how they are named, and most importantly how the clients of your API or system are supposed to react.
- The typical developer approach to exceptions, and why developers act that way.
- Checked and unchecked exceptions – enforcing the API or just getting in the way
- Fourteen different exceptions that will pretty much cover anything any system or component will need to communicate.
- Making an exception useful, what does a client want to know when an exception is raised?
- The resurgence of HTTP response codes in the wake of REST,
- the ones you should know
- a couple of interesting thoughts on API versioning and health checks
- exceptions in asynchonous processing