Getting started with DevOps practices should not be that difficult or overwhelming. I hope to show a few ways that you can get started with the automation of some of your legacy applications to start following some DevOps practices.

1. AUTOMATINGAUTOMATING
LEGACYLEGACY
David Tank

2. Legacy

3. Not a bad word. Lots can be learned from legacy. It's probably been working in production for a long time. Business
knowledge, critical systems. What happens if they fell over?
Speaker notes

4. ~ Donovan Brown
"Start with what hurts the most."
"You don't have to go ask permission to
spend 10 minutes to make your life
better."

5. If your legacy applications haven't been attended to they're probably painful. These things add value, and no body was
ever fired for brining value to their organization.
Speaker notes

6. Source Control

7. So where to start? If it's not source controlled, lives on a server, and people use it, it's going to fall over one day. What if
you don't have code to compile, do you put compiled dll's and packages in Source Control? We had a scenario where
another team was making changes directly in production Story about NAT tool.
Speaker notes

8. Testing

9. I understand, I've lived it, they're the first to go, but do what you can to get tests in. We shouldn't have to ask permission
to write tests. If they're asking for estimates consider your estimates with tests. At a minimum it's good to understand
what your code coverage is now, and never let it drop below that.
Speaker notes

10. Builds

11. Confidence in what you are building. Consistent packaging and imutable artifacts. Many tools available for this, for both
in-house and cloud applications. Jenkins, Azure DevOps, Travis CI, CircleCI, TeamCity. List goes on and on. What
about CI. Well, can be noisy if you're not ready for it. Do you have a build is it daily, does true CI make sense
Speaker notes

12. Deployment

13. If you've done it the same way more then once it can be automated in some way. Even if it's not a full blown CD
pipeline, using some sort of scripting to consistently run a process. Again, lots of options out there. Octopus Deploy,
Jenkins, TeamCity, CircleCI, Codeship, Azure DevOps Even if you can't automate deployment, have a build that creates
artifacts (versions, etc) consistently, or maybe you take small steps. Tell Bluesun path
Speaker notes

14. "You don't have to go ask permission to
spend 10 minutes to make your life
better."