- #The chief architect tutorial is full of mistakes how to#
- #The chief architect tutorial is full of mistakes series#
I guess my question there would be, what’s your advice to someone who, whether I’m trying to start from one side or the other-I’m a dev person, I’m trying to get something started, maybe I’ve been doing agile, or if I’m an ops person, I’m trying to eliminate some of that air gap. Todd: You sit in an interesting spot being an architect there at Blackboard where you can sort of see all of these pieces and how they work together and have some influence over that. That can work to a certain extent, but what ends up happening is you have this air gap between your development and operations organization that results in a lot of loss of fidelity, a lot of missed opportunities for things to get better for everybody.Īnd so, in my eyes, DevOps is all about reducing that air gap, getting it as close as possible, if not the same people, so that the people that are doing the operations have an intimate understanding of what the development organization has had to do to get to the point of having a product, and that the development organization has an intimate understanding of what the operations team has to do to make sure that application runs well, so the two organizations can work together to make sure that everybody benefits both internally and externally. Development did their work, we wrote our code, we wrote our tests, we verified our stuff, and then we packaged it up and we threw it over a wall to our operations team and we said, “Run it for us.” Historically, particularly at Blackboard, there has been a very strong separation between operations and development.
#The chief architect tutorial is full of mistakes how to#
It’s a view and a perspective on how to do things more efficiently as a development in an operations organization.
#The chief architect tutorial is full of mistakes series#
It’s not a series of people doing certain specific things.ĭevOps is really a culture. The biggest misrepresentation I always see is that DevOps is a team, and I see that used a lot, and it’s happened a lot at Blackboard where there’s a team labeled “DevOps.” It’s not really a group people. It’s a question that comes up all the time, and I feel like the one misrepresentation I hear the most-I’ll start with that, and then talk about what I see as the real definition in my eyes. If I had to try to tackle you down and make you give me a definition of what DevOps is, what is that to you?ĭavid: It’s a great question.
Todd: Let’s start with the question, this nebulous question that everybody has, about DevOps and what DevOps is. He’s the Chief Architect at Blackboard, and we’re going to talk about DevOps. I’m your host today, Todd Sattersten, and today I’m talking with David Ashman. Todd: Good morning! Welcome to the IT Revolution Podcast. IT Revolution interviewed David Ashman on his definition of DevOps, his DevOps journey, and how DevOps has affected Blackboard. This is the first of a series of interviews with DevOps practitioners.
0 kommentar(er)
