A small intro to a daddy’s journey balancing life between DevOps and DadOps
I am a DevOps engineer and also a dad. Half of the day I’m DevOps and half of the day I am DadOps. And while thinking about the two, I noticed that the activities and work per se, are similar. So that being said, this is the first article of many, from my adventures as a DaddyOps or DadOps at home.
“A DevOps engineer introduces processes, tools, and methodologies to balance needs throughout the software development life cycle, from coding and deployment, to maintenance and updates.” More on the subject here.
Ok, so what does a DadOps do in this context you ask? Well let me rephrase the above quote just to give a small sense of the whole DadOps thing, and after that, I will put it in a bit of context 🙂
A DadOps engineer introduces processes, tools, and methodologies to balance needs throughout the life of his kid(s), from early stages, through education, and constant updates to raise a beautiful person.
My kid, is 2 years 8 months 6 days 2 hours, and 49 minutes old, but nah, who’s counting? He is wonderful in all the ways possible like all children are.
I will do sort of a comparison next, with my work concerns as a DevOps and the things that occupy my time as a DadOps:
DevOps: IO (Input/Output) pressure on the systems
DadOps: “Did he/she eat enough? How many poops did he/she have? Was that consistent/inconsistent with what he/she eat? Smell, texture, quality ok?”
DevOps: Monitoring Tools and Systems to keep everything in check
DadOps: “Where is the thermometer? Is it a fever? Hospital or no hospital? Do we have medicine in the house or not? and so, so, so many more (if you are a parent you know that the need for monitoring his/hers health is endless and you never have enough knowledge, tools, and people to help you understand if he/she is ok or not)”
DevOps: Automation, pipelines, flows
DadOps: “If you do this, daddy will give you that. Our schedule is our day flow, and almost nothing can interrupt or perturb that, without catastrophic consequences like lack of sleep, moodiness, crying, and so on.”
DevOps: Debug and resolve issues in production
DadOps: “Unfortunately with a kid, you do not have a dev or test environment, so you are always in production!!! All situations need to be handled with extra care, and everything is sensible, all need a discussion, and nothing remains untouched when giving an answer to a Why? question.”
DevOps: Find solutions to problems
DadOps: Find NOW solutions to ALL the problems
DevOps: Get your hands “dirty” and go full code
DadOps: You are already dirty, so one more diaper will not kill you, and some vomiting there on the floor, definitely needs your immediate attention!
DevOps: Write documentation and put in place coherent processes and procedures to make everything work
DadOps: Do a schedule. Respect the schedule. Repeat.
The list can go further but for now, as a small intro, I think this is enough 😀 If you liked this intro please show your happiness by sharing it and commenting, and that will definitely make me write the continuation sooner 😛