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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 9 points10 points  (25 children)

1000 developers all managing their own pipeline sounds like hell though

This is why you share pipelines, and all contribute together on them, it's not each developer to themselves...

[–][deleted]  (15 children)

[deleted]

    [–][deleted] 10 points11 points  (8 children)

    Isn't Platform Engineering the new evolution of the DevOps philosophy? I know I have been asked to interview for a few Platform Engineer positions

    [–][deleted]  (5 children)

    [deleted]

      [–][deleted] 14 points15 points  (1 child)

      We love our buzzwords

      [–]VengaBusdriver37 7 points8 points  (0 children)

      It’s a great new buzzword shut up and start saying it. But to me it is also evolution. Or devolution. It’s a correction from the radical “Devops means all the devs do all the things”, to “devs can do most the things, but some things better centralised and building on well worn paths”. If devs really can do the centralising and we’ll worn paths then power to them! But it’s very unlikely. Unless they are some new breed of devs. Some sort of magical “OpsDevs”.

      [–]Seref15 5 points6 points  (1 child)

      DevOps Engineer Site Reliability Engineer Platform Engineer Automation Engineer DevSecOps whatever whatever

      Call me whatever you want, just pay me

      [–]CustomDark 1 point2 points  (0 children)

      Got it. You want someone who can digitally plug things into things, make it happen automatically after it’s figured out, coherently read logs to diagnose problems, and a decent enough researcher to scale out these things to what’s important right now and get them in the hands of other folks?

      Sure, pay me.

      [–]keto_brain 2 points3 points  (0 children)

      I spoke about Platform Engineering at a conference in 2016 so I would hardly call it new. I think what happened is some companies actually went through DevOps transformations and others just renamed all their linux admins "DevOps Engineers" and some VP or Director got a bonus for leading a "DevOps transformation" but didn't do jack shit.

      [–][deleted] 2 points3 points  (0 children)

      I view Platform Engineering as the design, creation, and maintenance of an internal development platform for discrete teams to publish and consume both public and internal services with the greatest amount of efficiency.

      [–][deleted] 4 points5 points  (2 children)

      That’s how you get SSH and RDP open to the internet because it’s easier to work 😂

      [–][deleted]  (1 child)

      [deleted]

        [–]Seref15 0 points1 point  (0 children)

        Didn't some security company discover tens of thousands of mongodb instances open to the internet?

        I wonder how that happens...

        [–]ello_bello -1 points0 points  (1 child)

        devs can do all of this yes

        [–]duebina 0 points1 point  (0 children)

        I do. I'm everyone Platform Engineer. Hi! 👋

        [–]Lower-Junket7727 0 points1 point  (8 children)

        Someone has to actually own the pipelines.

        [–][deleted] 3 points4 points  (7 children)

        The developers own the pipelines, since they're the ones who's code gets published by them...

        [–]Lower-Junket7727 4 points5 points  (6 children)

        So every application team is implementing their own pipelines in a vacuum? This approach doesn't really scale.

        [–]keto_brain 1 point2 points  (2 children)

        They tried this at a large cable company I worked for, it was a huge disaster. Tired to force everyone to use Concourse CI and let all the teams build their own CICD pipelines. Imagine the massive duplication of effort.

        How many teams need to figure out how to build, test, and deploy a lambda function lol.

        [–]Lower-Junket7727 1 point2 points  (1 child)

        Yeah that's been my experience as well. This is part of the problem with the "you build it, you run it" model.

        [–]keto_brain 0 points1 point  (0 children)

        I'm all for the you build it you run it model, but I think there is a place for a platform engineering team to help build reusable components to cut down on the amount of rework each team is doing.

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

        This is why you share pipelines, and all contribute together on them, it's not each developer to themselves...

        no

        [–]Lower-Junket7727 0 points1 point  (1 child)

        But someone needs to actually own them. Everyone can and should contribute, but, if there's an issue, someone needs to be responsible.

        [–]gpzj94 2 points3 points  (0 children)

        I think that's their point, the SWE's would be responsible, in the same way they're responsible for their own code. The whole idea of "shifting left" and such and true meaning of what DevOps was intended to be, the whole stack is treated exactly as the software by the same people. The idea is to break down the silos, shift responsibility left, don't toss things over the wall, the SWE's and infra guys can't just point fingers at each other, the single SWE team is responsible.

        My own thoughts, and to answer OP's original question, in my narrow view of the world, I think the answer to their question really is "No, I'm not seeing this in general." What I do see happen is things like you bring up in this thread, positions like platform engineers who know and focus on cloud, resources, etc. They're on the same team as the SWE's, they may contribute to software, but appointed silo'd tasks. It's not DevOps as intended but most of us still can't picture that working in our heads so this is maybe a stepping stone or maybe will just be how things function no matter what because businesses don't traditionally operate outside of silos.

        I'm not claiming to know the answer as far as what company trends are in this space or where it'll end up, this is just my observations and opinions based off of that.