Related Posts
Anyone in metro DC looking to transition out?
More Posts
Chief
I love my neighbors.
Newbie to investing and never invested in a company that went through a reverse stock split.
In theory, I understand the market value should increase but I’m not seeing this reflected in the price and naturally my book value/ share is very disappointing.
A) When should I anticipate the stock appreciation to occur?
B) What’s the next move for companies that do this? Issue more shares?
TIA!
https://finance.yahoo.com/news/retransmission-hive-blockchain-announces-5-100000300.html
Additional Posts in Tech
When is a 3 page resume acceptable?
McKinsey & Company Any advice to help prepare for data science analyst role at top consulting firms (McKinsey & Company EY Boston Consulting Group etc)? Any materials, open source platform recommended to take on freelance data science project? When should I start actively looking and applying? I am a new grad who is working in tech as a marketing analyst I’m looking to pivot to marketing& sales data science consulting next year. Would like someone with similar backgrounds offer some practical tips.
New to Fishbowl?
unlock all discussions on Fishbowl.
You can do DevOps practices even without the title. A good starting point might be to read DevOps: A Comprehensive Beginner’s Guide to Learn DevOps by Ethan Thorpe (also available in audiobook).
Once you get the gist, learn as much as possible how to use Git. As DevOps you need to work with code and how to versioning your code, so Git is widely popular nowadays for versioning.
Next, read, learn and practice from this book: Ansible for DevOps, by Jeff Gerrling. As a DevOps you need to learn how to setup and automate with code aka Infrastructure as a Code with tools like Ansible, Chef, Terraform, etc.
A good reading for Terraform will be, Terraform: Up and Running by O’Reilly Media (there is also a certification you can get for Terraform by Hashicorp).
From there you might want to learn some stuff about how to automate with CI/CD with pipelines. Jenkins would be a good place to start here. Again looks for books on Jenkins 2 Up and Running from O’Reilly media or any book you prefer or video course for this.
No way you can pick everything at once so try to look for projects within your company that allows you to integrate any of the skills one at a time. Once you can show how to automate stuff in your workplace I will assure you they will probably embrace the idea. You need to keep everything documented so learn how to write Markdowns and how tos effectively. Tools like Attlasian Confluence, Typora, Obsidian will be your daily bread and butter to document stuff.
More advanced topics could be Dockers and Kubernetes for packing, deploy and scale apps on containers/pods, Cloud Certificates (AWS, GPC Azure) are also recommended at this point.
Is a journey, not a destination but these key points will keep you on track to become a successful DevOp practitioner.
Keep one or two or even more project you can showcase and/or documentation of your own you can use on a personal blog or on Github/Gitlab/Bitbucket to showcase.
After a year or two, or maybe three, depending on how fast you can learn and showcase your achievements, you can start talking about and demonstrating to your interviewer’s your DevOps skills set and your road map to keep improving them.
Thanks for this. Reading it after posting, I just noticed you labeled it pretty much as I did... Is a journey, not a destination. That is VERY accurate. So I guess it is not lame after all ;)
DevOps means different things at different companies and is more of a jack of all trades. Breadth of knowledge is important..
Learn about infra (cloud, networking, security), CI/CD, automation. Always think that everything can be automated (whether true or not) and figure out how it could be done.
I see some comments about specific books and such. They are good. but they also are about specific parts of DevOps and tools that may not always apply. Even so, you will learn about the topics which tends to be more important.
Figure out what part of DevOps you like, then focus on it. Talk to your Infra, DevOps, Networking, Security, and Operations teams (depending on your companies size and organization). See if there are things you can work with them on.
If you want to focus on Cloud, learn some about AWS and GCP. You will need to know linux, if you don't already. Terraform has become a predominant tool for managing cloud infrastructure. So, learn about that.
Many companies have gone to Kubernetes, learn some about that.
I haven't made this specific shift, but I have just heard so many people say that making career pivots in this job market is a really difficult, even risky, move. People are requiring more years of experience than ever, it seems like a difficult move to make right now
I have switch different roles in the past manual, sdet, development to data eng. I self studied and looked for opportunities in the company to help and learn and practice and new skills. Then switch company after a couple years. You should discuss with your manager about the interest in other role so you get a different project or volunteer to help for exposure.
I was a devops manager for a few years. I usually looked for people who could do full stack development or knew infrastructure very well. I found that developers were easier to train since coding was a skill that infrastructure engineers sometimes were not good at picking up. My devops teams were involved in delivering products in data analytics. A full stack app deployed to the cloud connected to bi tools with data pipelines. I had members representing each of those areas.
I have been in a similar case and still in the process. Cant say for sure if it will work :) but if it makes you enjoy what you do more and more I would suggest you give it a try. In my case I dug deeper into learning APIs and postman and the usual suspect javascript, nodeJs and little by little I am moving from manual QA to actually do API testing and integrations. The risk is huge since you are stepping with very little experience into the world full of very good professionals with years of experience in coding and Devops... but things that are worth something are rarely risk free. Good luck! Lame as it might sound, look at it as a journey (where you learn everyday) and not the destination (where you might or might not get).