SPA-311: Failure Patterns in Java

BCS Software Practice Advancement

<P>Refreshments and sandwiches from 18:00.</P>
<H2><SPAN>Synopsis</SPAN></H2>
<P>As developers, we have a tendency to focus on what our code is supposed to do, the happy path. Unfortunately, the real world is rarely that simple. Our code fails: it fails frequently, in many different ways. Code that is simple when expressing the happy path very quickly becomes complex and cumbersome when expressing the reality of the situation.</P>
<P>One approach to this rising complexity which has proven attractive in functional languages is railway-oriented programming: a way of representing two parallel paths through the code, one for success and one for failure. I'll be discussing a way to do this in Java, why it's desirable over more traditional approaches, and how it solves some Java-specific issues like exception-handling when using Streams.</P>
<P>Once you have this concept of railway-oriented programming, you start to see common patterns of failure that crop up time and again. I call these failure patterns, and taking a functional approach to Java makes it much easier to abstract over these, creating reusable solutions. I'll talk through a couple of examples, showing how you can easily build good DSLs that are highly specific to the use case, while still integrating well with basic constructs.</P>
<H2>About the Presenter</H2>
<P>TOM JOHNSON is a born-again software developer: having left insurance to study computer science, he has since worked in pensions administration, then at LMAX exchange, and now at <A HREF="https://unruly.co" TARGET="_blank" DATA-MSYS-CLICKTRACK="0" REL="nofollow noopener noreferrer">Unruly</A>, where he tries to balance his interest in functional programming with the fact that we're working in Java by building and evangelising as much of a functional approach as Java allows.<BR></P>

BCS London

Our {communityGuidelinesLink} describe the sort of content we prohibit on Eventbrite. If you suspect an event may be in violation, you can report it to us so we can investigate.

To report other categories of prohibited or illegal content, submit {link}

SPA-311: Failure Patterns in Java

More events from BCS Software Practice Advancement

Discover more events from BCS Software Practice Advancement, from Science & Tech to other experiences you might love.

SPA-311: Failure Patterns in Java

More events from BCS Software Practice Advancement

Discover more events from BCS Software Practice Advancement, from Science & Tech to other experiences you might love.

You might also like...

Browse more events with different dates, prices, and formats to find your next great experience.