DevOps Finland September Meetup

Hosted by Gofore

Agenda

17:00 Doors Open

17:30 Welcome / DevOps Finland & Gofore

17:45 From DevOps Teams to Platform Teams, and what did we solve? / Jacob Lärfors, Consultant @ Verifa

18:30 *** break ***

18:45 Key Elements of Disaster Recovery Plan / Rajasekar Mohan, Principal Software Architect @ Ekahau

19:30 *** break***

19:45 How Haskell Gets Delivered: An Overview of the GHC Value Chain / Bryan Richter @ Haskell Foundation

20:30 Free Discussion

21:00 Closing-up

From DevOps Teams to Platform Teams, and what did we solve?

DevOps was never intended to be a role, and certainly not the function of a team. However, many organisations looking to implement DevOps did what they do best: create a function around it and start a team. One can argue, however, that DevOps teams did ultimately have a positive impact. Since Platform Engineering became the latest hype, many teams are being rebranded from “DevOps” to “Platform” with an apparent focus on Developer Experience. With this new buzzword, can we finally figure out what DevOps teams were supposed to do?

Jacob is a pragmatic engineer who enjoys helping teams with all things continuous and cloud.

Key Elements of Disaster Recovery Plan

Disaster recovery (DR) is the process of restoring an organisation’s IT systems and data after a disaster. A disaster can be any event that disrupts business operations, such as a natural disaster, a cyberattack, or a hardware failure. A disaster recovery plan (DRP) is a document that outlines the steps that an organisation will take to recover from a disaster.

A disaster recovery plan is an essential part of any organization’s risk management strategy. By having a DRP in place, an organisation can minimise the financial and operational losses that can result from a disaster.

Rajasekar Mohan, Principal Software Architect, Ekahau
linkedin.com/in/rajasekar-mohan-8076726a
https://cloudsneakpeekbyraj.blogspot.com/p/essentials-of-cloud-architecture-cloud.html

How Haskell Gets Delivered: An Overview of the GHC Value Chain

Like all active programming languages, Haskell continually gets new core features, bug fixes, and performance improvements. But how do these benefits get into the hands of users? I'll explore the GHC value chain, describing the steps involved in making Haskell dreams become a reality. I'll point out some of the existing pain points and steps I have taken to alleviate them. We'll also see how even though DevOps is usually applied to continuous services, it works equally well delivering software artifacts like a compiler. And maybe Haskell should be considered more of a continuous service, anyway?

Bryan started programming mobile apps on an HP-48 graphing calculator in 1998. Since then, he studied some physics, did some traveling on a bicycle, wrote some web apps, and moved halfway around the world. He has programmed professionally with Haskell since 2014 and focused on DevOps since coming to Finland in 2018. As DevOps Engineer for the Haskell Foundation, his mission has been improving the GHC CI experience for maintainers and contributors.

Streaming: No streaming nor recording this time

Join our slack: http://www.devopsfinland.org/