Failure Is Always An Option
Software runs the world. We use software to manage our calendars, talk to our friends, run our businesses - and, as our societies inevitably try to replace people and paperwork with apps and algorithms, we find ourselves facing some vital questions about the reliability of that software. If you take the time to actually read the terms and conditions, you’ll find that just about every system we rely on comes with no warranties and no safeguards - you use it at your own risk, and if it doesn’t work, that’s your problem.
But there’s more to building reliable systems than just writing good code. Reliability isn’t just about software engineering, it’s about systems engineering; about taking a holistic view of services that includes software, hardware, networks, and people. Join Dylan Beattie for an insightful look at the history of systems engineering, at some of the strategies and design patterns that we can use to build reliability into our systems, and at what happens when the software that runs the world has a bad day.
-
Failure Is Always An OptionDylan BeattieThursday Jun 29, 15:40
-
Flow. The Worst Software Development Approach in HistorySander HoogendoornKim van WilgenThursday Jun 29, 13:30
-
Programming's Greatest MistakesMark RendleWednesday Jun 28, 16:40
-
Demystifying Blockchain - From Infrastructures Via Smart Contracts to ApplicationsOlivier RikkenTuesday Jun 27, 14:20
-
SecurityBert HubertTuesday Jun 27, 14:20 & Tuesday Jun 27, 16:40
-
TBAAnita SenguptaTuesday Jun 27, 09:10
-
TBAErik ScherderWednesday Jun 28, 09:10
-
One Rule to Rule Them AllDave ThomasThursday Jun 29, 09:10
-
How The Hack?Ben SadeghipourWednesday Jun 28, 13:20