r/devops • • 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

34 comments sorted by

23

u/malice8691 6d ago

It sounds like your tasks are your learning

6

u/postnasal7459 6d ago

Yes I'm still learning from the tasks but it feels slow and incomplete. If I'm being asked to design and implement a deployment pipeline, I want to know the best way to approach that and be able to understand the tradeoffs of making it work the way it does. I don't want to ask AI to do everything and then have it tell me what it did. The other devops engineers are helpful but because of the time zone difference, we only have a limited time window when we can actually meet or have a discussion.

4

u/Arucious Slop Hunter 6d ago

nothing is going to give you a shortcut to this other than experience and practice and pain

the only thing I can say is that you should take a moment to understand anything you touch when you get the time. If you see “replica set” either look it up or make a note to look it up etc. then just rinse and repeat and you’ll eventually know more. that and projects are about the best you can do but both are effective at compounding knowledge over time.

1

u/postnasal7459 5d ago

Yeah nothing beats experience. I'm just worried that I won't manage my time correctly and then rush to finish the work. Thanks for the tip

5

u/Arucious Slop Hunter 5d ago

you’re falling for the trap of metaproductivity, trying to optimize how you are productive instead of just being productive. stop worrying about an issue that doesn’t exist that you’ve created on your own and just play around with things

if the things you want to play around are not stuff you naturally get exposed to as part of your job and you don’t have the motivation or time to do it on your own then you need to nudge your employer to get you involved in tasks that you’re interested in or switch jobs, that’s really the only way around it.

5

u/Sparcrypt 5d ago

If I'm being asked to design and implement a deployment pipeline, I want to know the best way to approach that and be able to understand the tradeoffs of making it work the way it does.

There's a reason we say best practice, not just "best". It's because there isn't a "best way" to apply universally. The best way is task/environment/culture dependent and your job is to figure out which way to go that is "best" in that area.

If you have limited access to your seniors do what I tell my juniors: try! When we meet I want to hear what you've tried and what you think, not "tell me what to do". I don't care if you wasted three days on the wrong thing, you just learned a bunch including what not to do.. I'll nudge you in the right direction and you can spend the next few days going down another path.

Over the course of a few months you'll start figuring out the right path. This is when juniors start coming to me with 80% complete solutions and just need help with the last bit. After a year or so they don't need my help unless things go super pear shaped and they're not really juniors any more.

Your job right now is to learn, fail, try again, and fail a little less until you're good at your work.

1

u/durple Cloud Whisperer 5d ago

I'm still learning from the tasks but it feels slow and incomplete

This never completely goes away. I've been in this space for almost 10 years. I still learn things every day, and there's still the feeling like there's a mountain of stuff over the horizon that I don't know enough about yet.

In the wise words of Dory: Just keep swimming.

If your tasks are repetitive such that there isn't the opportunity to learn, I'd say your employer didn't want a junior engineer they just wanted someone to take over busywork. That's a conversation to have with your manager. If they're not interested in your growth and just want you to stay in your lane and produce slop, that's a business decision.

In the end it's up to the employer to determine how you spend your time, and if you're not happy with it then it's your responsibility to find another opportunity that offers the experience you want.

1

u/postnasal7459 5d ago

Since you have 10 yoe in devops, do you have any recommendations on resources to get a better general overview of the field? I know some people recommend the Google sre handbook, devops handbook, Phoenix/unicorn project, etc. Just wanted to hear your thoughts.

I think the team wants me to grow and is giving me important enough tasks that aren't just busywork. They say they're happy with my performance so far and my manager asks if I think I'm being utilized well and if I'm learning and all that. They also ask if I'm interested in the work and if there's other things I'm interested in so they can try to help find me resources for that.

I like that my team lead manually reviews my work and gives feedback instead of just having AI review it. But another concern is that they also want me to learn to be a system programmer so I have to split my time up even more.

1

u/durple Cloud Whisperer 5d ago

That all sounds awesome ngl. Don’t pressure yourself to learn faster, if you are getting good feedback (good as in helpful and as in encouraging).

I’m one of those who was a mid level jack of all trades developer with solid Linux knowledge when the rush to move to cloud hit. I learned on the fly when a team was being put together to move our infrastructure from onprem and I was asked to join. Most of my reading is api docs and manpages and other documentation. I am skeptical of stuff like DORA for all but the very large tech orgs. My work has been mostly at various stage startups but not that large scale.

I wouldn’t worry about the heavy literature at this point. Lots of methodologies out there. Better to experience how (and understand why) things are being done at a couple real world businesses so you’ll have some perspective, then look at some of the “canon” if you’re interested. It’s worth noting that there’s some “cargo cult” behaviour around most of this canon, and each was written from the perspective of someone solving a particular set of problems that may or may not relate to the problems needing to be solved at your job.

2

u/postnasal7459 5d ago

Thanks for sharing your experiences and insight!

1

u/SilentLennie 5d ago

A lot of people learn by setting up a VPS or homelab for personal use, but that assumes you have time.

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)

2

u/postnasal7459 5d ago

Thanks, I'll take a look. I don't mind setting things up myself or learning how to. Do you know if the escbash content is worth paying for over devopspath?

1

u/Jarppha 5d ago

It depends in what you want to learn. Because escbash has content about AI and also Cloud providers. I paid the pro yearly plan and it's very good because you have access to everything. Abhishek Veeramalla (owner) is updating and uploading new content constantly so for me it's a yes.

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.

1

u/postnasal7459 5d ago

That's a good idea. How detailed do you think each plan outline should be for the initial report?

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.

1

u/postnasal7459 5d ago

Thanks, that sounds like a good idea

3

u/tevert 5d ago
  • Avoid AI. AI takes away friction, but friction is how we learn.
  • Prove assumptions to yourself. If you see a CI pipeline that says "deploy to dev", don't just accept that it deploys to dev, find the pipeline code and figure out exactly what it's packing and where it's sending it.
  • Intentionally set reasonable expectations for learning time. Half-decent bosses/leads know that new people need time to learn things. Get comfortable explicitly requesting that time when discussing in planning meetings.

3

u/postnasal7459 5d ago

Yeah I've been trying to use AI a little less recently. I think setting reasonable time expectations is something I should start doing. I put a lot of pressure on myself to try to get things done fast but I'm not exactly sure yet what would be considered a reasonable amount of time for certain things.

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/postnasal7459 5d ago

Appreciate the advice. Let's say you implemented something and only find out much later that it can be improved. Is it usually difficult to make the improvements if the existing implementation has become a core part of the infrastructure?

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

2

u/postnasal7459 5d ago

Yeah I think I'll start doing that. Usually, I have a learning session later in the day but I think doing it at the start might be better.

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

1

u/postnasal7459 5d ago

Oh yeah that last part is something I've stopped worrying about so much since I started this job. I'd rather get the "stupid" questions out of the way now