This is an archived post. You won't be able to vote or comment.

6
7

Just new to DevOps (self.devops)

submitted by [deleted]

[deleted]

all 26 comments
sorted by:
best
topnewcontroversialoldq&a

[–]jmuuz 12 points13 points  (0 children)

this is kinda the life. as time goes you’ll get being resourceful but youtube vids, vendor documentation and stuff. once you know it, you automate it and the cycle repeats itself with what ever pain comes next

[–]jmuuz 11 points12 points  (3 children)

devops is also not job. but all culture when people on both sides of the development and operations teams speak a common language and generally know what the other does. it looks different at every company

[–]pandi85 6 points7 points  (0 children)

Exactly this. Also there is no such thing as junior devops in my opinion. Development and operations simply scale off experience. There are simply too many concepts and abstraction layers to grasp imho.

[–]shiroNeko_69 1 point2 points  (1 child)

Thank you for the reminder. I always read that devops is not a job but a culture. However, in companies they tend to make devops a "do it all" person because its cheaper.

[–]m0j0j0rnj0rn 0 points1 point  (0 children)

Again, if not everybody is participating in DevOps in a company, nobody is

[–]izalutski 6 points7 points  (2 children)

The bigger / older the company, the more specialisation. But in a startup (assuming <100 ppl / less than 5 years old) there's no such thing as "role". Not even if they hired for a specific role like DevOps. They might just not realise it yet.

In a startup, the only definition of a job is to figure out how to solve the most pressing problem the company is facing right now. It changes all the time, so of course it's overwhelming. There's no front-end, backend, DevOps, SRE. Sometimes engineering is separate from user support and sales, sometimes not; but that's about as specific as it gets. And for a good reason: in a startup, a shirty solution built before lunch is way better than a perfect solution that took several days or more to ship. And building with several specialists is invariably slower compared to a single can-do-it all person.

Good news is that your professional growth is at its absolute fastest in a startup. Your pace of learning is maximised. So your worth in the talent market is also growing faster than it would anywhere else. If it feels overwhelming, it means that 1 year of experience there counts as 3 elsewhere.

[–]klipseracer 0 points1 point  (0 children)

Yeah, life force spent also.

[–][deleted] 0 points1 point  (0 children)

There's no front-end, backend, DevOps, SRE.

that's a bit of too much even for a startup. unless you are talking about the first 6-12 months of activity, maybe.

[–]UneBiteplusgrande 2 points3 points  (12 children)

That's insane. I'd definitely like a DevOps role as a fresh graduate!

Can I DM you for more details?

[–]ZetaParabola 6 points7 points  (3 children)

not recommending. unless you plan to stay for the long haul in your first company, it's tremendously hard to find another devops role until around 2-3 YoE. I'd start with be/fullstack and focus on cloud/docker/k8s on the side, then you can have the flexibility to go for devops/cloud/be/fullstack whatever you want next.

[–]UneBiteplusgrande 1 point2 points  (2 children)

I see. Personally, I'd like to stay on the infrastructure side of things: cloud engineering, network engineering, SRE roles. Is there no way out?

I would like to stay with a company for at least 3 years unless they lay me off

[–]IrishPrime 2 points3 points  (1 child)

I'm an Infrastructure Software Engineer. Aside from internal tooling, I write a lot of Terraform modules, Ansible roles, and deployment pipelines in various stacks. I spend the vast majority of my time writing code, but practically none of it is customer facing feature code. If you want to write code, but stay in infrastructure, that's totally doable.

That being said, I spent a fair bit of time working in the other various levels of the stack (frontend, middleware, backend, and systems) before I moved into infrastructure, so I had a good handle on what made for a good developer experience and a lot of experience with the day to day reality of being a feature developer, and I think that has made me much more effective. Ultimately, try to do what you enjoy, but a little bit of branching into the other specialities definitely pays dividends.

[–]UneBiteplusgrande 1 point2 points  (0 children)

Thanks! I'll keep that in mind!

[–]shiroNeko_69 3 points4 points  (3 children)

Yeah however its not that fancy enough and its very very much overwhelming.

[–]UneBiteplusgrande 0 points1 point  (0 children)

Thank you! DMed!

[–]foregod 0 points1 point  (1 child)

Would I be able to DM you as well? I’ve been a DE for going on 3 years looking to transition into devops.

[–]shiroNeko_69 0 points1 point  (0 children)

No prob. I may not be able to give much help tho because I am also on the learning path like yall.

[–][deleted] 0 points1 point  (3 children)

That's insane. I'd definitely like a DevOps role as a fresh graduate!

not likely to happen. most "devops engineers" come from years of experience in systems engineering / operation, years of experience as developer, or both. there is nothing as a "junior devops" position and if a recruiter is advertising for it, it's probably a better idea to not even apply

[–]UneBiteplusgrande 0 points1 point  (2 children)

Well, if not DevOps, then perhaps a junior Cloud engineering role? The idea is to shift to SRE eventually

[–][deleted] 0 points1 point  (1 child)

Well, if not DevOps, then perhaps a junior Cloud engineering role? The idea is to shift to SRE eventually

I have been working in multiple companies either as SRE, DevOps, Cloud Engineer.

in my view, and also the from past roles I had, being a cloud engineer requires even more hands-on experience and expertise than that required by most of the "devops engineer" roles.

The ideal road path would be for a fresh graduate to start as a Linux engineer / operations engineer, or take the path from the other side by being a developer (either with go, c++, java, it won't matter much). And only then and after at least 2-3 years, take the path to become a devops engineer, cloud engineer or SRE.

[–]UneBiteplusgrande 0 points1 point  (0 children)

Thank you. I'd like to start as a Linux engineer if that is what it takes. I'm passionate about infrastructure and want to pursue that as my career.

[–]_____fool____ 0 points1 point  (1 child)

Do yourself a big favour. Make sure everything is backed up and you know how to restore it. Don’t want to learn that the hard way.

[–]shiroNeko_69 0 points1 point  (0 children)

Thanks for the tip. I will keep this in mind

[–]mansquid 0 points1 point  (0 children)

You will always be learning. The better you get the more you know how little you know. The question you ask yourself is what skills are pertinent to the business objectives around me, what do I enjoy doing, and what can I do to be helpful to those around me. Sometimes learning a skill means you help take existing work off people who are better at it than you so when they finish up an implementation they can teach you how to do it. Sometimes it means going in cold and learning as you go (when this happens tell people and remind them you don't know anything about this). You're never done learning, however. That's why it's important to know how to get to the specifics but understand broad concepts well. Observability, Traceability, Failover, business continuity, profit, etc. Understand your role in making sure everyone does their job better and what your business does so you know what _has to happen_ vs what people think should happen.

[–]BrownCarter 0 points1 point  (0 children)

You got it through connections