Elevator Pitch
Have you ever been dropped into a legacy application that had some sort of pipeline, but now you have to figure out how it works? I found myself there, so let’s talk about legacy pipelines and puzzling your way through resurrecting them based on what I learned and encountered along the way.
Description
We’ll talk about good ideas and bad ideas when handling a legacy application from a CI/CD pipeline standpoint, understanding how a system is put together from logs and other data you (hopefully) can find—and what to do when you don’t have any data at all,—and how to make that legacy application’s pipeline more usable for the next maintainer down the line. And just maybe we’ll unearth how to pull that legacy pipeline from the grave so that, while some people might still call the system legacy because it’s old, the pipeline can show them a thing or two about modern CI/CD strategies.
Notes
I thought a talk that looks at migrating a legacy application to a more modern system might catch some people’s interest since we all have legacy applications we need to mind, especially ones that get dropped on our laps without much documentation or without someone to glean information from.
My few technical talks have all been internal at a previous company (Rackspace), but I used to run the internal technical conference at Rackspace and used to be a science museum educator that gave live talks 3 times a day all week long. Speaking isn’t new for me, but the technical speaking world is. By the time this conference starts, I will have given a workshop at DeveloperWeek Austin, and I hopefully will have more Meetup talks under my belt.
This talk is a new talk for me and I’m new to developer relations (I was a software dev working on automation and pipelines), so I would love some feedback if it isn’t chosen on why it doesn’t work if you have time to share.