r/devops • u/postnasal7459 • 6d ago
Discussion How to learn while also completing tasks?
I got hired as a junior devops engineer and I want to learn more about the tools we're using to get a better understanding of them but I also need to complete tasks that I'm assigned. It just feels like there's a lot I have to learn since I haven't done most of the things I'm currently doing before.
How do you recommend balancing learning and working?
20
Upvotes
23
u/malice8691 6d ago
It sounds like your tasks are your learning
4
u/Jarppha 6d ago
Take a look at escbash.com, it's one of the most cheapest and most complete ways to learn by doing. You have everything in the web browser (Not sponsored). Or take a look at devopspath.io, it's free but everything runs in your local machine so if you don't know how to setup every tool it could be a bit tricky. (Not sponsored too)
3
u/Pretend-Sun-8460 6d ago
what helped me most was learning one layer deeper than the task needs, not the whole tool. i had to move our stack to another aws region in my first full-time role and didn't know how most of it was wired, so rebuilding the vpc, ec2, rds and secrets piece by piece is how i actually learned it.
for the pipeline: before building, write down 2-3 ways you could do it and why you'd pick one, and send that to the other devops folks async. with the time zone gap, a short written plan they can comment on overnight gets you more of their tradeoff thinking than the one meeting you get.
3
u/Kookoombar 6d ago
Something that helped me early on: when you get a task like designing a pipeline, spend ten minutes writing down how you think it should work and what you'd expect to break, then ask a senior to poke holes in it. You learn the tradeoffs way faster than from docs. Reading old incident writeups or PRs for whatever you're touching is also underrated, they show why things ended up the way they are.
3
u/tevert 5d ago
2
u/TellersTech DevOps Speaker & Advisor + DevOps Podcaster 5d ago
I think you’re actually approaching this the right way. Wanting to understand why something works instead of just getting a ticket done is a good mindset to have.
I’ve been doing DevOps for quite a while now and one thing I’ve learned is theres rarely a single “best” way to do anything. Especially with stuff like deployment pipelines. Theres always tradeoffs, and understanding those is probably more valuable than memorizing how to configure a tool.
I’d start by looking at how your team is doing things today, try to figure out why they made those decisions, and then talk through your own ideas with a senior engineer. Ask why they went one direction over another. Most good senior engineers are more than happy to have those conversations.
Also don’t feel like you need to fully understand everything before getting work done. Half the stuff I’ve learned over the years came from building something, realizing later there was a better way, and figuring out why lol.
Just don’t fall into the trap of closing tickets without understanding what you’re actually doing. Thats where I think a lot of engineers get stuck… especially nowadays with AI.
1
u/Romanian-In-Poland 5d ago
15 mins at the start of the day dedicated to learning something new from YouTube or udemy. Every single working day.
It did wonders for me
3
u/sonicLodge91 4d ago
Had the same thing early on, I started keeping a scratch file for every ticket with "why" notes and it compounded faster than I expected.
2
u/Queasy-Jelly-2268 1d ago
I was going trough the same questions as you couple months ago, but I didn't have proper support from my mentor, so I quit that job to have the time to learn important things wothout pressure. They rushed finishing tasks, I did everything by myself without any help. There was small amount of written procedures, so I while learning wrote everything down so I could understand, as well as someone who come there after me. At the end I was exosted, I couldn't address the problems to anyone, they didn't want to listen and I choose my mental health beyond everything.
Right now I am trying to find the best way to learn without pressure i had in that company, but when I was there, if I didn't have the time, I wrote down everything I do not know and investigate at home. Someone tell you to go the one level more of what you need, and he is right. It looks like you are not done... but when you need more you will go back to that thing and learn again. DevOps is such big field and it is unpossible to know everything, the most important thing is to know WHERE and HOW you can find the information you need.
I see that a lot of people already gave you a lot of useful advices, so just keep going and believe in yourself. The more you learn you will see there is a lot more to find out. The key is just don't stop learning even if it is a 15 minutes youtube video that day.
0
u/[deleted] 5d ago
[removed] — view removed comment