Upgrade to Pro — share decks privately, control downloads, hide ads and more …

You don't need a DevOps to "be DevOps"

You don't need a DevOps to "be DevOps"

A bit of my personal experience on working in environments with:
- No DevOps people or mindset
- DevOps people
- DevOps mindset

Filipe Freire

August 03, 2017

More Decks by Filipe Freire

Other Decks in Programming


  1. You don’t need a
    DevOps to “be DevOps”
    Filipe Freire

    DevOps Porto #7 - 3 August 2017

    View Slide

  2. Quick intro
    About Me:
    Husband, Tester, Developer, Gamer, Learner,
    • <2y as Test Engineer
    • 1y as Developer
    Currently work @

    View Slide

  3. Disclaimer
    I’m no expert:
    I’ll give you a
    personal account

    View Slide

  4. Before DevOps
    You have
    to be
    like this

    View Slide

  5. Before DevOps
    Big focus on Small picture: 

    development over process
    No automation or deployment pipeline and tools:
    - Alerts & monitoring? Nope.

    - Dependency management? Maybe for vendor stuff

    View Slide

  6. Before DevOps
    Infrastructure? (examples)
    - Maintaining physical and virtual machines

    - Virtualization? Containers?

    - Going to the server room. Hard drives burning.

    View Slide

  7. Before DevOps
    Thing is… we had good tech & tools.
    We didn’t pay attention to the process itself.
    Why? Individual effort & projects.

    View Slide

  8. Having a DevOps person

    View Slide

  9. Having a DevOps person
    Things start too change.
    - Good deployment & integration pipelines

    - Containers everywhere!!

    - Infrastructure? No worries (AWS, Azure, etc)

    - Feedback! Monitoring! (& Amazing Ops people).

    View Slide

  10. Having a DevOps person
    Perfection? Nope.
    “It’s the DevOps fault/problem, not ours”

    “It’s the programmers fault”

    “Pipeline? Only the DevOps know that magic”

    “I need a release/deploy, how do I do it?”

    View Slide

  11. Having a team with DevOps

    View Slide

  12. Having a team with DevOps
    Here I had an internal clash:

    How’s it possible? No DevOps person?
    Now it’s the team’s problem.
    Everyone knows the pipelines and the process.
    Ops are transparent: Anyone can dissect issues.

    View Slide

  13. Quick Learnings
    You still need experts!

    - More stuff to handle, more stress…

    - Developers in sync & w/ mindset but…

    does “management” keep the pace?

    - You can have all the greatest tech but…

    Lack of vision and process: all is in vain.

    View Slide

  14. Future improvements
    Finding Balance. 

    Improvement is not guaranteed always.
    No matter the approach: 

    You need skilled but solid & brave team-players.
    Same applies for management people.

    View Slide

  15. filrfreire
    Follow me @

    View Slide