Husband and Dad 👨👩👧👦 DevOps Engineer 🛠️🤖🤘🏼 Geek 🕹️and Hobbyist coder 👨🏻💻🔰 Always longing for the Internet of the 90s 💾 I 💜 Python 🐍, learning JS/Node. 🤞
I work "in DevOps" and The Phoenix Project is required reading for anyone who wants to be a DevOps Engineer. It's super fun and you get to work with a lot of cool tools, but everything you do has to bring some value.
In fact, when disagreeing with another DE about something, the easiest question to ask is "what value does this provide?" If they can articulate why, the we'll go with it. If they can't, then they understand why the solution wasn't the right choice at the time. This also provides opportunities for collaborative development of best practices and is overall a positive for the team, IMHO.
The best part of working in DevOps is that you not only get to improve the lives of developers with efficient pipelines and self-service tools, but you can actually improve the entire company.
Anything that makes the business run more efficiently, faster with less labor, or eliminates toil will ultimately allow the collective efforts of the teams to produce better software faster.
DEV user @pirxdanford
does a great job of explaining the CALMS model (previously CAMS) which is the guiding principle of DevOps, IMHO.
Max is a life enhancer for tech & entrepreneurship. Which seeks to blend both to build innovative products or services for the world that solves hard problems.
Yes that's great!! Cause sometimes I wish there were more developers or DevOps engineers who reads it. Like for example of my ex co-worker, he literally took whatever my senior software engineer says. As words from God but did not think about it. To make it easier to work on deploying it into our testing and production server but choose to do everything manually without scripts to automate it to reduce the time taken.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I work "in DevOps" and The Phoenix Project is required reading for anyone who wants to be a DevOps Engineer. It's super fun and you get to work with a lot of cool tools, but everything you do has to bring some value.
In fact, when disagreeing with another DE about something, the easiest question to ask is "what value does this provide?" If they can articulate why, the we'll go with it. If they can't, then they understand why the solution wasn't the right choice at the time. This also provides opportunities for collaborative development of best practices and is overall a positive for the team, IMHO.
The best part of working in DevOps is that you not only get to improve the lives of developers with efficient pipelines and self-service tools, but you can actually improve the entire company.
Anything that makes the business run more efficiently, faster with less labor, or eliminates toil will ultimately allow the collective efforts of the teams to produce better software faster.
DEV user @pirxdanford does a great job of explaining the CALMS model (previously CAMS) which is the guiding principle of DevOps, IMHO.
dev.to/pirxdanford/calms-a-holisti...
Yes that's great!! Cause sometimes I wish there were more developers or DevOps engineers who reads it. Like for example of my ex co-worker, he literally took whatever my senior software engineer says. As words from God but did not think about it. To make it easier to work on deploying it into our testing and production server but choose to do everything manually without scripts to automate it to reduce the time taken.