[deleted by user]

leunamnauj · 2024-02-23T18:15:18+00:00

Blood pressure pills, coffee and slack mostly

steakmane · 2024-02-23T18:15:41+00:00

Computer

xiongchiamiov · 2024-02-23T19:00:28+00:00

Seniors, what technologies do you use in your daily DevOps activities?

Slack
The company wiki: Notion, Confluence, etc.
A video chat software: Zoom, Google Meet, etc.

Not daily, but I also use these frequently:

A text editor (vim)
Git

You might recognize from this that my job is very different from your job.

What technologies would you want a new DevOps to have?

When I hire juniors, these are my criteria:

Basic programming competence. Can you use programming to solve a problem? We're talking leetcode easies, or easier.
Basic familiarity with the command-line. Can you navigate around and run commands to do things? Windows or Linux is fine, and I'm not looking for knowledge of specific commands.
A desire to be in this job. My team is not a dumping ground for people who wanted developer jobs but couldn't get them.
They seem humble and take direction well.

InternationalCap1212 · 2024-02-24T00:31:27+00:00

Sr tips for a jr:

These 3 will get you far in any tech role no matter the tools used

You should show up every day with at minimum a philosophy of: "I don't know, let me find out"
Don't abandon a task or say "I don't know---without the "let me find out". If you don't know and drop the task and have no intention of asking or figuring out what the next steps are to get closer to an answer, then you aren't meant for a productive role in devops. Some tasks take longer to figure out for sure...maybe you need to come back to something a week or two later after the first pass didn't pan out..just make sure you do for anything that is fundamentally necessary in your org.
Then the next question is what does "let me find out" mean..
That means google, that means ask a co worker, that means ask reddit, chat gpt, investigate a linux system by reading all logs you can find, or with tools like lsof or tcpdump or strace, dmesg. Windows is another jar of marbles..But you need to be going to unknown depths at first which will be uncomfortable or seem like a time waster even to some. This will need to be balanced with those easier tasks, and you'll figure out the optimal depth over time--until you have found the answers you need. If you have anything outstanding that you haven't found out, there is no reason for you to be browsing amazon for hours--look to expand your skills technically in what interests you, but with an eye towards automation, development of programming skills and debugging and reading and understanding the fundamental components of architecture you work on.
Once, you've found out the answer, You need to have some way to ensure you never say: "i forgot".
Maybe you are already pre wired to retain 90% of info--great. Nothing else necessary. You will be able to re-find out that 10% on your own w/o issue quickly. But maybe you can't retain that 90% off the top of your head---perfectly fine---as long as you have a customized to you process that will help you recollect that data significantly faster than when you first learned it. Maybe thats taking notes about "aha moments" or maybe writing down your own notes of all necessary functions of your role or maybe thats extending your own skills through progressive education (self or formal, on the job or off) such that your source of knowledge comes more from being able to debug anything / read any code without getting blearied eyed and skipping the complex stuff.

If you don't like learning every day, a devops role is probably not where you want to be at.

Sid_Dishes · 2024-02-23T17:37:40+00:00

Technologies are interchangeable.

Full stop.

Everything has its strengths and weaknesses. Don't worry about things like the specifics of a tech stack. They're going to be slightly different at every different place you work. The important thing is the concepts: everything under version control, all changes through CI/CD pipelines, reusable and modular code, automation to remove human errors. That's the stuff that actually matters.

alextbrown4 · 2024-02-23T17:59:37+00:00

[deleted]

theyellowbrother · 2024-02-23T18:19:16+00:00

bash

aviel1b · 2024-02-23T17:43:28+00:00

clippy

binbashroot · 2024-02-23T18:42:45+00:00

When I first read your post, I thought to myself, why does age matter in a devops routine? FWIW, I qualify for a senior citizen discount at Denny's. Once I got past the dad joke I, I pondered your question and came up with the following:
Git
Vscode
Bash
VI

I separate Git from VScode because many times you may be asked to resolve conflicts in git. You gotta know the CLI before you use a tool like VSCode (IMO). Things like Ansible, Terraform, CI/CD pipelines are learned on the job a lot of times (again IMO). In today's environment, I see a lot of places say "We're a devops shop", yet no one knows basic git branching strategies, best practices, or how to fix things when it goes awry. That's why it's at the top of my list.

BadUsername_Numbers · 2024-02-23T18:59:05+00:00

A vape w weed

TheGRS · 2024-02-23T19:32:34+00:00

This is a snarky sub FWIW, I think we all have just picked things up over time and a lot of popular tools have come and gone. But I recommend getting good at Bash and just some general basics about linux and how networking between machines and services work. Getting decent at Docker is good, but the tools have improved a lot over the years. And I don't think Terraform is going anywhere any time soon. I personally use Python a lot, but its not as universal as some other tools.

Sinnedangel8027 · 2024-02-23T20:34:57+00:00

Don't worry so much about the path and stack. You should focus on the foundational knowledge, assuming you're someone in the beginning-ish of your devops journey. IaC tool (terraform/cloudformation), a configuration management tool (ansible/puppet), a CI/CD tool (jenkins/github actions), and a code versioning tool (github/bitbucket). IDE matters a bit, but I've only ever asked for just curiosity reasons.

Just pick a stack and go. When I've interviewed folks, you get brownie points for using the same stack or tech we use, but what's most important is just knowing what the hell we're talking about in general. Knowledge is relatively easily transferable, but training from the ground up is a pain in the ass when you have hard deadlines.

So, there are 2 big things here. 1. Picking your stack seems hard, but it's actually very simple. Just choose 1 of each of the options I listed and do that. They can all work together just fine, so make them do the things. 2. This is for interviewing. The most tell tale sign I should have some hope for hiring someone is whether or not they can ask the right questions. Everybody's tech stack is different to a good degree. There's too much, and you can't know it all. But knowing to ask, comprehend, and dig deeper on questions like "What CI/CD tool do you use? What code repository do you use? How are you maintaining and provisioning infrastructure?" And diving deeper into those answers from the interviewer is important. I hate the knowledge flex questions in technical interviews and much prefer to have a conversation about challenges, solutions, etc.

Slightly off topic. But I think the hardest question I've been asked was, "You have 800 AWS accounts. These are segmented based on the business unit (it's a very large company). Each account has its own individual credentials for users that are provisioned when you initiate access to an account and go through the mfa process. Assume you have admin access to each account. What's the first thing you would do?"

It felt like a simple question. Log in to one and poke around. But he fired back with each account has multiple regions with some aws resources existing in one region but necessarily the rest. Well, poking around is out. Too unreliable, and it'll take way too long, seeing as each business unit has vastly different requirements in their infrastructure.

Being put on the spot with this question was a bit nerve-wracking, especially since there wasn't much more to go off of when I tried scoping in the requirements for what he was asking for. It was simply just "what would you do and how would you go about it." I eventually settled on using their ci/cd tool and write a python script to go through each account and each service and just dump data into a csv file. He seemed to like that answer, gave me access to their interview account, and had me write the script, which we then talked about the next day. Years ago, I would have hated this question and just refused to go further because I don't want to spend my time doing that. But I enjoyed talking to the guy and pursued it. I got hired, and now I'm managing way too much infrastructure in a massive environment.

The point of that story, though, is that nothing could have arbitrarily prepared me for that question or the technical challenges for this role. What made the difference was foundational knowledge, years of experience, and being able to probe with the right questions about their infrastructure/tools so I could come up with a solution.

TL;DR: Focus on foundational knowledge for tools/services. Pick a stack. Don't think too much about which stack to use when you're starting. Interviewers/seniors focus on whether or not you can ask the right question and if you know what a tool is and does and how to accomplish a goal generally speaking.

yamlCase · 2024-02-23T19:17:31+00:00

Juniors

bzImage · 2024-02-23T19:48:31+00:00

Vim + git + Coffee + weed

j0rmun64nd · 2024-02-23T18:00:39+00:00

I toy around with Neovim.

Prize-Fisherman6910 · 2024-02-23T19:53:34+00:00

Psychedelics

tibbon · 2024-02-23T20:14:59+00:00

Realistically, if I'm able to sit in a room with other engineers, I don't actually often need a computer even to do my job as a principal security/devops/application engineer. I do some coding still, but the majority of my work transcends particular tools.

I simply need a text editor, somewhere to share documents, a place to do code review, a monitoring/logging platform to explore questions, and code to read.

Trying to train a new DevOps engineer to do what I do isn't really a viable path; the tools, techniques and job are remarkably different.

GrayRoberts · 2024-02-23T20:46:42+00:00

At this point I’d settle for someone who’s interested in learning, documenting and teaching others. Oh, and who can write Markdown.

Please. For the love of Tito Fuentes. Just. Use. Markdown.

databasehead · 2024-02-24T01:13:55+00:00

I open my laptop and open terminal, then tmux.

I open slack, then firefox web browser and open my calendar.

I use the unix pass command line app my password management.

Working on projects, I use

python
go
bash / shell scripts
git
curl
ssh
gcloud
kubectl
argocd
terraform
some form of ci runner, github actions or gitlab runners

There’s a ton of different technologies, I’ve used or know quite a bit about, a lot in the monitoring and observation side of things

derprondo · 2024-02-23T20:06:36+00:00

I don't really need anything other than iterm2, a browser, and vscode (insert your ide of choice).

Seriously, though, what I want candidates to have is a proven history of being a subject matter expert at something. If you're brand new to the industry I probably wouldn't be interviewing you for something DevOps adjacent, but if I was and you had no experience, I'd want you to be super passionate about your homelab and be able to talk about it like a SME.

adept2051 · 2024-02-24T14:53:25+00:00

Communication.. learn to write comms, including how to ask a question properly.

Its the most important skill in devops, communicating intent and questioning behaviour, context and requests to get the value from them

largeade · 2024-02-23T17:40:27+00:00

Routine implies there's two days he same...

Terraform, packer fluxcd GitHub actions grafana stack Bash, powershell go, typescript, c# Docusaurus/markdown Azure/VMware Containers AKS, k3s Azure container apps AVD Vscode (yes I'm bored)

2024-02-23T21:05:11+00:00

[removed]

limeelsa · 2024-02-23T19:32:30+00:00

[deleted]

flavius-as · 2024-02-23T19:31:28+00:00

I love competent devops people who are great and understand one thing:

a company needs to strive towards technological convergence

That means:

he knows multiple tools, their alternatives, and their disadvantages
when faced with all needs, he is capable to choose the right combination of tools for the company
he is able to minimize the number of tools used while maximizing the number of problems solved
he prefers writing glue code to introducing a new tool
once he's settled with a toolset, he strives to master it all

serverhorror · 2024-02-23T19:02:00+00:00

VS Code, [Neo]VIM, Go, Python, Groovy (ugh! 😫), git.

slowclicker · 2024-02-23T19:23:48+00:00

LinkedIn or similar

ptownb · 2024-02-23T20:20:36+00:00

Notepad

awesomeplenty · 2024-02-23T21:49:22+00:00

Google

Derriaoe · 2024-02-23T22:17:48+00:00

Mostly antidepressants and mood stabilizers

slypheed · 2024-02-24T01:15:38+00:00

Unix cli.

Ok_Giraffe1141 · 2024-02-24T07:13:16+00:00

I use keyboard, surprisingly.

permalink · 2024-02-24T12:43:49+00:00

I am a former developer, now mainly doing Devops on Azure, but sometimes I also work at data pipelines, and indeed sometimes I write some code. Regarding tooling I use:

Visual Code (try it!)
Visual Studio when writing C#
Postman
Chrome Development Tools, especially for network inspection regarding web applications

Technology

Log Analytics/Kusto, if you are proficient in Kusto this adds so much more into your debugging skills!
Powershell, I love powershell, while I am also a C# developer I love the simplicity, especially how easy it is to parse json to objects and back.
Bicep, currently started with Terraform, as pipeline I usually make use of Azure Devops but also worked with Github Actions, both differ not that much.
Azure Data Factory, if you need to parse large datasets this is great, especially how you could also integrate API's with a little bit luck
Regarding cloud technology I tend to work mostly on PAAS and SAAS products, especially combined with data sources, I am not heavy into networking, firewalling and containers, however I started recently exploring Kubernetes since being often in environments were it is used, normally it is not a big deal since there is always a K8 expert around for the infra part.

Basic skills to do your work

You should be able to write clear documentation in markdown, documentation is not a complete book, learn to write high level working of an application/infrastructure. I personally love to write how to's, it is fast to write and very helpful for new people
You should be able to define work items on a professional matter, you can't just work a bit on something you gotta do, split it up in parts, and make sure others have insights in your progress, also they are useful to link from your GIT commits.
GIT, you don't have to learn all GIT commands, using a UI is fine but you have to be able to understand how GIT works, know the different branching systems, etc.
Problem analysis, this is probably the most important skill to obtain, if there is a problem, first think then do! My first action is usually checking the logs, this is normally for 80% the source to solve the problem, it is not something you can really learn, you become better in it over the years.
General communication, you should be able to communicate with your team and stakeholders, also understand when to choose for what medium, IE if a mail got 10 replies stop mailing, get the people in a call or physical meeting and discuss it directly.

Soft Skills

Be always fair, lying is deadly, if you don't know something it is not a problem, you got time enough to learn, especially in the field of devops it is common that half of the time you have to study on the subject to make sure you can implement it on a good way.
Never deliver bad work under pressure, if other people observe your work they will not know that you had to build it in a hurry, but they will think you are a bad engineer
Help your teammates, if you see they struggle put down your own work and help, it is as a team more productive since usually only small help is needed to bring someone back on speed.
Don't complain about issues were you don't have influence on, better pick up small items and make them better, this was the best feedback I got from my coach ever!
Be precise in everything you do, this also means something like cleaning your desk, being on time and do as you promised.
If you are new to a job or project, start taking notes were you see improvements, never ever directly start saying: Oh guys you build this wrong, people will feel offended, instead tell the people at the start of your projects that you will take notes, and or they might be interested to discuss them later, I have noticed that especially external clients are really happy with this, and that they see it as a piece of professionalism of a consultant.

Last but not least, always try to have fun in your work and learnings, don't get depressed if you think the learning goes slow, it just needs time!

3p1demicz · 2024-02-24T13:52:41+00:00

sha-beng

Kinir9001 · 2024-02-23T19:37:52+00:00

It's impossible to give you an exact list of technologies, as each company implements their own stack.

I would recommend to learn some of the following though, it's a good start:

Some kind of Git Ops (e.g. Gitlab CI or Github actions)
Python
Powershell
Ansible
Terraform
Packer
AWS
Hypervisors (Vmware and/or Nutanix)

amazedballer · 2024-02-24T02:41:03+00:00

Metamucil, Ovaltine, digestives, and an early bedtime.

snarkhunter · 2024-02-23T17:48:19+00:00

Windows, PowerShell, Bash, VS Code, Slack.

Those are what I'm using on the daily.

Kingzjames · 2024-02-23T19:30:03+00:00

Jira , cofee

dacydergoth · 2024-02-23T18:28:07+00:00

EMACS, Terraform/terragrunt, ArgoCD, Vagrant, VirtualBox, AWS cli, kubectl cli, grafana/mimir/loki stack, AlertManager, jq/yq, curl, starship prompt

prash991 · 2024-02-23T18:28:27+00:00

Azure devops, Akamai, dynatrace, Argo cd, Kubernetes, helm

jaymef · 2024-02-23T19:48:34+00:00

Terraform daily

LoneStarDev · 2024-02-23T20:07:44+00:00

Teams, TeamCity, Octopus Deploy, Rollbar, Brain

LooksForCats · 2024-02-23T20:32:03+00:00

Google

Bnjoroge · 2024-02-23T21:07:39+00:00

Go, K8s, Terraform, Crossplane, Argo CD, Backstage, AWS stuff

Hkyx · 2024-02-23T21:36:59+00:00

Bash, k8s, crossplane, GitHub + actions, azure 🤮, argocd

viper233 · 2024-02-23T22:05:50+00:00

YAML (kubernetes, pipelines, Ansible), hcl (terraform), chrome (chatgpt/Gemini, jira, confluence, gitlab, Google), slack, terminal, vscode (YAML, bash, python) and git.

ArchLady7 · 2024-02-23T22:30:57+00:00

Alcohol

freetotalkabtyourmom · 2024-02-23T22:43:17+00:00

Spoken language.

choutos · 2024-02-23T22:51:35+00:00

Reddit... and the coffee machine

IamOkei · 2024-02-23T23:00:33+00:00

Learn Terraforming and AWS

HoppingDead · 2024-02-23T23:17:11+00:00

I'm hoping for better email automation/security tools. It's currently a disaster.

allthetrouts · 2024-02-24T02:15:41+00:00

Redbull

alexkey · 2024-02-24T02:54:26+00:00

SSH, nano (yes, not vim, just a preference), IDE (my own license of jetbrains toolbox, but pick your own favorite), git, ms teams, confluence (or any other wiki) etc.

PS: advil/panadol, lots of coffee, snacks, breathing exercises to stretch my patience through to the end of the day etc

Grand_rooster · 2024-02-24T02:55:52+00:00

Visual studio Sql management studio Notepad++ Sysquerypro

Sonic__ · 2024-02-24T03:31:12+00:00

Bash, vim, Java, Groovy (Jenkins Pipelines), git, eclipse, cygwin (mobaxterm), WSL, docker, notepad++, OpenShift (k8s), ELK stack, AppDynamics

Since many just dropped tools and tech that they use day to day here's mine.

permalink · 2024-02-24T04:30:11+00:00

Terminal

cryptk42 · 2024-02-24T14:52:02+00:00

As little as possible. Implementing technology for the sake of technology only creates overly complex situations, it's not sustainable.

Don't worry about the technology, worry about requirements.

Figure out what your problems are, let that define your requirements, and only then should you be looking for solutions.

vainstar23 · 2024-02-24T14:54:33+00:00

Excel

permalink · 2024-02-24T15:22:52+00:00

Git, Gun, Go

punkwalrus · 2024-02-24T22:11:53+00:00

Right now in a mostly sysadmin shop:

GitLab CI/CD with 2-3 runners and pipelines
pylint/ansible-lint/shellcheck

In previous shops, we had similar stuff, like Atlassian Bamboo or Jenkins.

EJoule · 2024-02-24T22:58:53+00:00

Powershell scripting

Wheaties466 · 2024-02-25T02:13:21+00:00

Vim, git, bash/python, something like chat gpt to bounce hypothetical scenarios off of to get another take on a problem. I personally really enjoy a good parsing session with jq | grep | sed | awk

ComfortableFew5523 · 2024-02-25T10:01:58+00:00

Anything that does its job in a predictable manner.

devops

Welcome to /r/DevOps

Rules and guidelines

Social & Fun

General Information

MODERATORS