11 September 2019
Dev Ops Side Adventures
It’s no secret that I one day want to do dev ops work. Not just any dev ops work, I want to work in the mobile area of dev ops? Why? I really have no clue. As I started trying to make my dev process better, leaner, and less labor intensive I’ve started to see how it helps.
I want to dedicate this whole line to someone who got me into Dev Ops on the low, Z.
Working with Z opened my eyes to test driven (TDD) and I never really learned it for school but it kept coming back as something to look into. When I finally decided to take code seriously I started looking at processes and testing again. Fast forward and here I am interested having a furture title of dev ops engineer or something.
TO ME working in dev ops means that you are the oil that helps the machine run. You see the big pictures of what people want, you see what the devs need to do, and you help create a pipeline (insert eyebrow wiggle thing) to get from code to big picture as soothly as possible without disturbing your lovely coders.
So what all have I learned throughout this little adventure? I’m glad you asked, I’ll list the name of the programs and a brief how I use it blurb.
— Cucumber: used to test ruby code, don’t really use but can navigate
— Junit: test java/kotlin code logic
— Jenkins: Used locally (not anymore) to run continuous integration
— Travis: Used to run some code test, also used at a job for build check before reaching QA
— Chai/Mocha: Used for node testing when building apis
— Jest: Suggested use with React Native so used for testing redux
— Circle CI: Used to run some of my project continuous integration
— Robolectric: Android device testing. Can use a emulator or real device to simulate navigation flow
— Chef: server/cloud configuration management
Are any of you into/do dev ops work? Feel free to comment on this or if you are learning too let me know and maybe we can swap resources.By: Keheira
tags: dev ops - studying - development