Tag: DevOps

  • Study: Real-Time Data Has A Transformative Effect

    Study: Real-Time Data Has A Transformative Effect

    We all know that data is the heart of the modern digital business. And real-time data is arguably the next evolution—having up-to-date data can empower energy savings and optimizations to reduce cost. Real-time data processing also aids fraud detection and improves health care responsiveness.

    Especially in DevOps, access to real-time data is necessary to reduce incident response time and inform ongoing SRE objectives. Leveraging performance data can also empower future decision-making and open new revenue opportunities. In essence, real-time data can have a transformational effect on the operations of a digital business.

    DataStax and ClearPath Technologies recently released the 2022 State of the Data Race Report. The study found that the majority of data leaders are using real-time data to create additional value. The report also suggested that working with cutting-edge real-time data technologies increases developer experience, which is good to maintain amid ongoing talent shortages.

    Below, I’ll review the key findings from the study to infer how organizations can effectively use these technologies and how they can mitigate roadblocks that arise throughout the process.

    The State of the Data Race

    Simply put, customers expect real-time experiences. And it’s not only the end consumers—developers are also increasingly accustomed to building in this modality. This is evidenced by the recent rise of asynchronous, event-driven architectures. The survey depicted how fundamental real-time data is to modern software, finding that 78% of respondents agreed that it is a “must-have,” not just “nice-to-have.”

    The investment appears to be paying off. A full 71% of all respondents said they can directly tie revenue growth to real-time data. Not only does it seem to have a transformative impact on revenue growth, but it enhances productivity, too—66% of real-time data-focused companies agreed that developer productivity has improved. Naturally, the report found that developers are the ones most likely to be working with real-time data.

    Although modern databases and real-time data processing tools are more readily available these days (and open sourced), the maturity of data handling is not homogenous. Based on the classifications of this report, “data leaders” made up only 10% of respondents.

    Roadblocks to Value

    The road to data maturity has a few obstacles that could limit adoption. First is data complexity—33% said this is one of the biggest barriers to leveraging real-time data. This was closely followed by controlling data costs (32%), data accessibility (30%) and available skillsets (28%).

    Most notably, a skills gap continues to be a commonly cited hindrance throughout industry reports and across technology niches. Interestingly, a lack of in-house talent rises slightly higher in organizations with a high real-time data maturity. Those surveyed in this category said that their top barrier is finding the appropriate skills in their business unit.

    Cybersecurity is also a top concern—51% say security challenges are a big concern when it comes to the use of real-time data. As the report surmised, the business-critical nature of real-time data raises its worth as a commodity and area for attack. Furthermore, amid new data sharing regulations, IT departments are now under more pressure than ever to uphold data security and avoid the leakage of sensitive personal information.

    Unlocking Real-Time Data

    This area has a lot of potential; 86% of developers at organizations with a strategic focus on real-time data said that the “technology is more exciting than ever,” the report found. Real-time data is beginning to be applied at the edge, where AI/ML can be trained to give a more responsive advantage to modern applications. Yet, organizations must prioritize its adoption and mitigate the roadblocks mentioned above to unlock the benefits of real-time data.

    Prioritizing real-time data will take more than tools—it will take vision. According to the study, those who created more value with real-time data initiatives were found to:

    • Have clear product owners
    • Have business unit accountability of data
    • And have department representatives working together in a cross-functional team.

    As you can see, these foundational goalposts have less to do with technology and more with lucid leadership and collaboration. That being said, an investment in the appropriate tooling is undoubtedly required to achieve real-time data.

    For example, this tooling might encompass NoSQL databases optimized for real-time or Apache Cassandra for high throughput. The transition to real-time will likely require streaming and messaging technologies as well. Less obvious, however, is an API layer to sit between the applications and the database. This element could greatly help open data accessibility in a standardized fashion.

    The State of the Data Race: Final Thoughts

    Working with real-time data can be a differentiator and have a transformative impact. As a result, most developers and leaders see real-time data as an exciting area. Yet, organizations must reduce data siloes to open up data access to realize its benefits. It will also take collaboration between data scientists and business divisions to construct meaningful outcomes.

    The State of the Data Race report surveyed 500 leaders across various industries. Above, we’ve summarized the key points from the survey. Readers are encouraged to pick up a copy for more nuanced data points and further commentary.

  • Tech. Strong. Women. EP 3

    Tech. Strong. Women. EP 3

    In this episode of Tech. Strong. Women., guest Nicole Dove, head of security at Riot Games, discusses with hosts Charlene O’Hanlon and Tracy Bannon her non-traditional path into IT and ways in which females can unconsciously sabotage themselves, as well as the impact of a strong mentor, regardless of gender. The video is below followed by a transcript of the conversation.

    Charlene O’Hanlon: Hey, everybody. Welcome back to Techstrong TV, and welcome to another episode of Techstrong Women, the ongoing series that elevates the conversation about gender equity and parity by celebrating the successes of females in IT, and so much more, we have so many great conversations. I’m Charlene O’Hanlon, as you probably know, but my cohost is Tracy Bannon with Mitre. Tracy, thank you so much for joining me, as always.

    Tracy Bannon: Oh, I always get so excited. Thank you very much for allowing me to cohost with you.

    Charlene O’Hanlon: Oh, listen, you – we are equals, we are equals, we’re not, you know, superior or inferior. And with us today we have Nicole Dove, who is an amazing, amazing female in IT, cybersecurity, and just a rockstar in the industry. Nicole, thank you so much for joining us today. We’re really thrilled to have you on the show.

    Nicole Dove: Thanks for having me. I love any thing, effort, or people who celebrate women in tech, so this is, like, the party to be at. Thanks for having me.

    Charlene O’Hanlon: Excellent, all right, well, hopefully, we’ll do right by you today, but do wanna thank you again for being here. We’ve got a lot to unpack in today’s show, but really what I wanna do is start out by, you know, telling us a little bit about what you’re doing today, and maybe how you got to be where you are.

    Nicole Dove: Yeah, so I’ve got, like, 50 jobs, and it’s easy [laughter] because I love them all. So, by day, I’m head of security at Riot Games, which is super exciting. It’s a new role for me, so I’m really, really happy to be there, fantastic team, fantastic products and services. I’m also a visiting lecturer at a local university, Clark Atlanta University. And I also extend my teaching into being a LinkedIn Learning instructor, where I create cybersecurity courses. And then I sit on a couple boards for two tech startups. One is called Wraith Audio and the other is called CyberSaint. So, a lot of tech, a lot of learning, a lot of teaching, a lot of people in my world, but I love all of it and I wouldn’t change it for anything.

    Tracy Bannon: So how did you find your way, though, to this most recent, right, the head of security?

    Nicole Dove: Yeah.

    Tracy Bannon: You’re one of the few females that I’ve met, so far, who are truly head of security. I’ve got lots of women who are on the rise, and in the security area in particular, it is booming, and that’s awesome, it’s completely amazing. How did you find your way into hat role?

    Nicole Dove: I slipped and fell into tech, and [laughs] this role was something that I don’t know that I expected, but I think that I found myself looking for an opportunity to have impact, right? So, you know, my career started – I went to school for accounting and finance. I started my career on Wall Street; it was all I wanted to do. And when I got there, I quickly realized, like, “Yeah, this may not be it,” right? So, like, I’ve got, you know, I don’t know if it translates, but I’ve got purple hair, you know – 

    Tracy Bannon: Oh, it does, I see it. [Laughs]

    Nicole Dove: Yeah, right? So, you know, back in the day, you know, 20 years ago, it wasn’t as accepted as it is now for, you know, a young woman of color who looks different, ’cause I’m, you know, different than the typical Wall Streeter, maybe to be accepted or to rise through the ranks. But I learned a lot, I learned so much, got into consulting, I just, I loved solving people’s problems, right? I loved the, you know, working on different engagements with different teams and different clients, and I really, really love to travel. But again, much of the big four consulting culture did mimic Wall Street, so I said, “You know, I’ve gotta figure out how to actually make the change,” because I began to see how culture impacts business. So I went all the way to a videogame company. I worked at Take-Two that owns Rockstar – had a blast, stayed there about five years, did some videogame voiceover work, got my first promotion, I was, like, “I’ve found my people.”

    And then I wanted to do something a little different, so I got into audit at a payroll company, and that’s where I started to just, like, explore all types of things. I was on a team, we built, staffed, and managed international work centers in Philippines, Romania, India, Brazil. I got to live in Romania for a little while; that was fascinating. But then I started to see how every single thing I did, whether it be Wall Street and treasury or videogames or payroll or even international operations, tech was the common thread, right? Like, we essentially took 20 percent of the company’s headcount and staffed it overseas, and they were able to be seamless and flawless because of technology. I’m, like, “There is something with this thing.” So, I really just took, you know, my expertise from risk and my willingness to learn tech, and that’s how I got into cyber.

    And what I love about this role is, you know, as a company that’s growing so rapidly, you see what’s happening in the industry, ransomware attacks, new technology, I mean, everything is just exponentially changing. What I like is that I get to bring that business background to cyber, to tech, and help people understand that tech is not – it doesn’t slow you down. If you position it correctly, it can actually enable innovation and speed and agility and creativity. And that’s what I love most. I would’ve never ever thought I would work in tech, like, I can barely hook up a printer, but I know risk [laughs], right? And I know people. And a lot of tech is people and risk and really just getting the best product and service to the customer, and that’s essentially what brought me right here today.

    Charlene O’Hanlon: What I love about that story is the fact that you did not swim in your own lane, you were going back and forth. So many people, I think, just kind of create a vision for themselves and they go for it. you know, it’s, “This is my goal in life is, you know, is to be a cybersecurity professional.” Great, you know, it’s – but you’ve had a lot of so many varied experiences that you’ve been able to kind of parlay into what you’re doing now. And I wonder, how did you create the narrative behind that? Because, you know, when you’re thinking about, you know, say, a job title or a job description, and you’re maybe going for a particular job or something like that, so many women, and we’ve had this discussion before, if they don’t check all the boxes, they’ll never apply for a particular job.

    And so, you know, so many times, you look at a job description and you’re, like, “I’m just not sure, you know, that what my skills are will resonate or will translate very well, without me actually having to explain how things go and how they do actually work.” So, how have you created the narrative around your experience into what you’re doing today and how it all fits together?

    Nicole Dove: Yeah, so, creating and changing narratives is the story, right? And I think the important part was not allowing these unicorn job descriptions to intimidate me, right? I think the second motivation was seeing men in positions that they didn’t qualify for, I’m, like, “Well, you know what, if they can do it, why not?” Right? And so, but as a woman, you know, like, we think a lot, we’re very tactical, right, we think things through. I tried to not think so much about what I couldn’t do and thought about what I could do, right? So I’ll look at a job description, everything I have, I’ll cross that out, I’ve got that in the bag. Then I look at the things that I don’t have and think through, “How can I get these things?” or, “What in my experience may not be exactly this but lends another perspective on this that I can bring?”

    And then the last part is, I’m a nontraditional technologist, so there is gonna be a host of things that I bring that nobody else is gonna bring, right? And that’s gonna be, like, the magic potion. So, you know, I often challenge – you know, one of my mentors said, “I don’t even read the job description.” [Laughs] Right? But it takes away that intimidation factor. Because there’s so much of the job that’s not on the paper. That’s always something I ask in interviews, “What do I need to know about this job that I cannot read on this paper?” And those are the things that, you know, we need to be prepared for, because it’s not so much what you expect to happen; the challenges are always the unexpected. And so, just by digging in that toolbelt and keeping an inventory for my own self, it helps you have something to pull from when you’re changing that story, or wanting to change your story and wanting to know what you can leverage to unlock that next level.

    Tracy Bannon: You bring up a really good point, a side conversation, which is: what has happened with job descriptions? They’ve become magic unicorn listings, and quite frankly, anybody that I interview, anybody, any that I look at, there’s never anybody who can check all of the boxes.

    Nicole Dove: Yes. [Laughs]

    Tracy Bannon: And it was an important message 20 years ago, but it’s an even more important message now. And there’s a reverse to that, which is, the folks who are putting those things out need to not focus on finding unicorns. You might run across one by accident, or the four-leaf clover in that one yard that you walk by, but in general, what are those applicable skills? What are the crossovers? And what you had was a lot of crossover skills and a uniqueness that other people didn’t bring to the table. That’s thought diversity, right? Educational diversity, background diversity, right? That’s what has helped to jettison you forward. That’s fantastic advice.

    Nicole Dove: Yeah, thank you.

    Tracy Bannon: So, you know, I’d be interested, when you are going through and working and mentoring with other people, and helping them to figure out what they want to do with their career, are there times where they’ll bring a job description and you’ll help them to walk through, like, “Don’t look at this,” or interpret it in that way? Do you help them apply the same skills that you’ve done for yourself?

    Nicole Dove: Absolutely. So, this is an exercise that I’ve used – so this exercise actually was a big part of me coming into tech, right? I was very intimidated by the job descriptions in technology, and it was only because of amazing mentors who were just, like, “No, you can do this. [Laughs] Go in the room and sell what you have, right? You can do this.” And so, it’s – you know, things are so much bigger when we don’t put them down on paper, right? And so, and I realized that a lot of other professionals feel that same intimidation, whether it’s within their own field or going into a new field, especially going into a new field, even more going into tech, right? Because it just seems so huge and big and so much relies on it, right?

    And so, because that exercise was so successful for me, it’s something I walk people through when they have something that they wanna do, when they have a big role they wanna apply for. Like, it’s a great way to pressure-test it, right? Because now you walk in pretty much knowing what they want and what they expect, and now you have the opportunity to align yourself with that, and be honest about what you don’t have, right, but what your thought process is to how you will get it. ‘Cause nobody knows everything, right?

    Tracy Bannon: I’m gonna guess there are times where, whether it’s you or whether it’s somebody that you mentor, goes into this conversation and the Charlene O’Hanlons walk away going, “Oh, my gosh, that’s a great idea. I hadn’t thought about that,” right? [Laughter] 

    Nicole Dove: I hope so.

    Tracy Bannon: So, whether they hire you or not, they’ve learned and gained kind of in this, you know, odd reverse-mentoring that happens, when you’re bringing those new ideas to the table.

    Nicole Dove: Oh, yeah, oh, yeah. And I’ve had some interviews that I’ve done horribly on, but those were learning experiences, too, right?

    Charlene O’Hanlon: Yeah. I feel like, you know, with these job descriptions in particular, I think companies do that on purpose, so that they can kind of gauge the type of people who do end up applying for those jobs. Because those are the ones who are the mavericks, if you will, those are the ones who really feel as though they can bring as much as possible to the table. And they know that they’re not, you know, they don’t have 45 years of whatever, you know, but they think that they’re qualified for the job, and that alone should get them in the door. But, you know, but at the end of the day, it’s kind of this push and pull between being what people expect you to be and being your authentic self, your true self, what you know you’re capable of doing and who you know you are at your heart. And that sometimes can be a difficult thing to reconcile, being your true authentic self, when you know you don’t tick all the boxes. And so, has that ever been a challenge for you to kind of get beyond, you know, just knowing that maybe who you are is not really everything that this person wants you to be on paper, but you know that you bring so much more to the conversation?

    Nicole Dove: You know, so, let’s unpack the term “who they want you to be,” right? Because what they really want is somebody who can get the job done, right? We get in our heads, like, and I am so guilty, and honestly, Charlene, I’m guilty of this with every single job that I take, even till this day. I don’t know why this is a lesson I have to keep learning, but it’s, like, as soon as I step outside the box and I do something bigger, you know, I’m, like, “Oh, crap, they really think I can do this.” [Laughter] [Crosstalk], like, “Oh, okay, I gotta deliver, now.” And you get so caught up in that ticking and tying and going back to that profile that sometimes you don’t see the forest for the trees.

    Because when you really take a look, it’s, like, it’s not about knowing those things; it’s about being – it’s not even about knowing everything. It’s about being relentless about finding the solution, being resourceful about looking for the answer, right? If there’s something that you don’t know, instead of just going to ask someone, figure out a couple options. Do you know how much I google, like, all the time, right? And I felt so bad about that, at first, but now that I’ve been in cyber for a while, I realize there are so many domains, like, I know a little bit about everything, right? But sometimes I need that deep expertise.

    I’m not expected to be an expert across the board. So, I think it’s more about taking a step back and understanding what’s needed to thrive and be successful in the role, and making sure that I’m checking those boxes as opposed to, like, a set of technical aptitudes and expertises. ‘Cause I’m not gonna have that. I study all the time now, and it’s never gonna happen, but it takes some time. And as much as I’m saying this, I’m probably gonna be going through this tomorrow [laughter] [crosstalk].

    Tracy Bannon: I think that it’s common, and I’m finding that at first I thought that it was more women. Sometimes we call it the Imposter Syndrome, and I used to think maybe it was more with females, but I’m actually realizing that it’s not. It’s everywhere, it’s everybody. However, to your point earlier, I do see a difference with a woman looking at the list and wanting to be a perfectionist and looking to checkmark everything on that list, where, sometimes a man goes, “Ah, I have three out of five. That’s good enough.”

    And I think what you’re saying is: don’t worry about everything that’s there. Be close, be energetic, bring your life to it, bring all of your life energy along with you, and see what happens with it. See what happens with it.

    Nicole Dove: Yes.

    Tracy Bannon: You know, along that line is, the number of changing job requirements or job descriptions where they no longer are including advanced degrees. I’m seeing a lot in technology, where it’s, like, “You know, we used to want a master’s degree in compute science, and somebody who is doing postdoctoral.” There would be wonderful educational academic credentials that they would want. IBM’s one of the first ones to say, “Let’s go nontraditional,” and they’re expanding their workforce in crazy amounts. Do you think that that’s helping with some of the other work that you’re doing? I really wanna hear a little bit about IANS and that kind of mentoring, because you’re helping, you know, people who are in all kinds of different roles. Now, you’re not necessarily mentoring kids, at that point; you’re out there mentoring the world.

    Nicole Dove: Yeah, so I love this question, because I think, and especially with me now having a foot in the education and the academia world, I’m seeing things shift, right? I love LinkedIn Learning because it saved me so many days, because there can be a project that I need to work on or lead, that I might not have in-depth experience in. And I can go and find a course on LinkedIn Learning, and within an hour, right, I’ve got a foundational understanding of what’s happening, from a verified expert or professional. And my certificates from Harvard, my double bachelor’s from Clark Atlanta didn’t create that, right? It was that one hour that I sat and learned.

    When I think about, like, different career experiences that I’ve had, on-the-job learning is something that I think hasn’t been prioritized as much in the past as maybe it is now, right? And I think that’s what’s beginning to rise. I think education is going to shift. I think on-demand learning and on-the-job experience is going to become more acknowledged and respected than it has been traditionally. And I talk a lot about this, I’ve got a podcast called “Urban Girl Corporate World,” you’d be surprised at what – I had a CISO who went to school for women’s studies, right? The head of risk and security at TikTok, she went to school for finance, she was a former Wal Streeter, too, right? But as leaders, it gives us so many different lenses. And that’s what I really love about working with IANS as faculty.

    So, IANS is a service that organizations can subscribe to and they provide a ton of support in different ways, so they’ve got forums and conferences and online classes. But they have this service called “Ask an Expert,” and essentially, you can look across any cybersecurity domain, we’ve got about 85 to 100 faculty, typically CISO or CISO directs, and you can spend an hour on the phone with this professional expert and talk about anything. I have helped CISOs look at their strat plans, develop security awareness programs, help government agencies enhance their third-party risk management programs, right? They’re not – this is – and this is different from, again, they could go on with their learning and get that foundational aspect, but they want the experience, right?

    And I think to your point, Tracy, that’s what mentorship is about: getting the firsthand perspective from somebody with experience. Because theory is great, but execution is so much better, and what I’m able to share is, “Hey, I’ve done that before,” or, “Oh, you’re thinking about doing this? Well, I did that and it flopped, and here’s why, here’s what you need to be mindful of.” And that’s what’s, I find, really, really special about that offering with IANS.

    Tracy Bannon: I think you’re gonna see, you know, to the point you just made, the education system is changing, higher education. One of my besties is a tenured professor and we talk about this all the time, and how it changed with the GI Bill, how it’s changing now. But we are always going to need specialized STEM, we’re always going to need those researchers, we’re always going to need the theorist. So the theorist won’t go away, but we also don’t need everybody to be a theorist. So how do we move towards the type of education that you’re talking about, which is relevant to where we are now, based on experience but relevant to what’s happening right now, with those theorists helping us to get smarter and stronger as we go. I think we’re gonna see a big change in the number of students that are, you know, looking for at four-year degrees for different reasons.

    Nicole Dove: I agree.

    Charlene O’Hanlon: Yeah, I remember even before, you know, the pandemic, there was a big push to get people doing trades, going back into the trades, because we just, we didn’t have – everybody was in college, so nobody could actually unplug a toilet, basically. So, you know, now with the pandemic, we have all these people who have gone on and done a lot of online learning, gotten certifications, and recognizing that, “I hope I just didn’t waste three years of college money, you know, learning something that, quite literally, the last six months or the last nine months, going online and really hyper-focusing what I’m looking at, what I’m learning about, is helping me in my career more than my four-year degree ever did.” So, I agree with you 100 percent, that the education system as we know it is changing, the traditional four-year degree probably is gonna be going away. And between you and me, I hope it happens within the next six years, ’cause I’m sitting on a really bad 529 account that I would like to use that money to buy a summer home or something like that. [Laughter]

    Tracy Bannon: I don’t think it’s ever gonna go away, but I think we’re going to see it return to a more pure sense. We need – now, I’m an advocate of the liberal arts programs, where, you know, we teach people how to teach. I’m also a big advocate of nontraditional education. It can be on the job, it can be through, gosh, bootcamps that you take, it can be through LinkedIn Learning. We just have to help with corporate America, to think about the diversity of the education itself, and to be more accepting of it. That’s the pivot point that we’re at right now, as I’ve been in some interviews where people have, you know, where we’re interviewing and I’ve had to kind of mute out and say, “Guys, they don’t have that, but that’s okay. Are you not listening to the story?” Right? “Are you not listening to the story?” Now, Nicole, do you also –

    Nicole Dove: I agree with that.

    Tracy Bannon: Go ahead, I’m sorry.

    Nicole Dove: I’m sorry, go ahead, Tracy.

    Tracy Bannon: I was gonna ask you if you also, you know, you’re mentoring adults in a formal setting with IANS. Are you also still mentoring with some of the other outreach groups that you were working with before?

    Nicole Dove: Yeah, so, I typically, kind of the first priority for mentorship that I get now are my students, so that go through my lecture series, just because I’m finding, quite naturally, you know, you have, like, that top 20 percent of your students that really, really are excellent and really engage the content, and then really take it to practice. And a lot of them, ’cause my course is MBA level, a lot of them are, you know, really starting, you know, or management level or supervisory level in their careers. And, you know, bringing in that people aspect is a totally different ballgame than just being a tactical executor. I also speak a lot at conferences. My podcast has an online community of about 800 women all over the world, where we talk about, you know, different things about our experiences as women in the workplace.

    And then, you know, this industry is so small and we’re just circles of people intersecting. And so, there’s always, you know, different CISOs who are starting mentoring circles, or they may want you to meet someone and meet someone else. So a lot of it is just, is very organic. But I am very intentional about connecting with professionals on the rise, on, like, the next generation of professionals, because every single fantastic opportunity I have had, nine times out of ten it’s gonna be because of a mentor or somebody who sponsored me or spoke up for me. So I feel obligated to pay it forward. There’s no possible way.

    Charlene O’Hanlon: I agree, I think, you know, where we go in our lives, from a career perspective, has a lot to do with the influence that other people have on us. And as well as the influence that we have on other people. So, I would be loath to be able to count on one hand how many experiences or how many opportunities I got by answering an ad in the newspaper or online. The best ones have always been, “You know, I know somebody who’s looking for this person. I think you’d be perfect for the job.” So, and I think, again, that kind of goes back to that, that being your authentic self conversation, because, you know, these people know who you are, they know what you’re capable of doing, and they know what you can bring to an organization.

    And I think that can only be had by developing these relationships, whether it’s with the people you’re mentoring or who are mentoring you, or even just people who you’re working with on a day-to-day basis. I always think that it’s best to bring your authentic self to whatever you do, and that can pay off in spades.

    Nicole Dove: Agreed.

    Tracy Bannon: Now, Nicole, you do a lot of mentoring, but let me turn the question a little bit. Did you have mentors? So are there people that you’re, like, “If it hadn’t been for Joe or Sally or Mary or – “? [Laughter] Any stories you can share with us, there?

    Charlene O’Hanlon: I’m sensing a yes, there.

    Nicole Dove: Man, there are so many stories I can share. I’m gonna share [laughs] – so, I was at a tech conference, once, and, you know, even now, but even more so years ago, there are very few women, right, in attendance. And so, I am a complete introvert, and so, after I engage with people, lots and lots of people, I need to take a break and just kind of like replenish. So, if you’re at a tech conference, the best place to take a break, as a woman, is the women’s lounge, because nobody else is gonna be in there. So, I’m at the women’s lounge, I’ll never forget this, it was the Saint Regis in Atlanta, and I’m just hanging out being an introvert on my phone, and in walks a woman who was on the stage earlier. And I had really admired what she spoke about, and I had said to myself, “Oh, I’m gonna reach out, I’m gonna talk to her before the day is over.”

    But again, I’m in, like, relax introvert mode, “I’m in the women’s restroom, that’s so weird, I’m not gonna talk to her,” and I just kind of left it alone. And she came back and she was, like, “Oh, my god, you’re an introvert, too.” I’m, like, “Yes, my people.” And so, we just started talking and I mentioned some things that she had spoken about earlier, and she was just, like, “Oh, my goodness, we just have to stay connected.” And we have. She has been so instrumental to my growth in the industry, right? I ended up changing jobs sometime after. She helped me think through, you know, which options to take which aligned and why, right?

    “The industry is small, I know this leader, I know that person. Oh, you need to meet such-and-such,” right? Like, if I really trace it back, my opportunity at Riot kind of goes back to her and some folks that she connected me with sometime ago. And she’s – her name’s Olivia Rose; she’s a CISO at Amplitude. She is just phenomenal and fantastic, and I strive and hope to be half of what she was to me, to many others. Because literally, mentors have changed my life. Another one is Trina Ford, who’s the CISO at A&G. When I was first thinking about coming into tech, she was the chief business security officer at my then company, and I reached out to her and I was, like, “I’m not sure, but I’m really interested.” And she was, like, “I think you would be good. You should interview.”

    Right, just getting that nod of approval or getting that push can make so much of a difference. And these are women that I call on often for advice or perspective, and they’re just fabulous, and I only can imagine, you know, what challenges they had to overcome to get where they are, right? And so, I’m really grateful to have amazing women like that in my space and my circle.

    Charlene O’Hanlon: It sounds like they were all organic mentoring, you know, they weren’t set up, you know, just, like, you click with somebody or you don’t. And if you click with somebody, then, you know, those are the best relationships to have, because you know each other, You know where your strengths and weaknesses are.

    Nicole Dove: Yeah, a lot of people try to force it. [Laughs]

    Charlene O’Hanlon: Yeah, exactly, exactly, and that’s why I love the idea of mentoring programs, and I love them when they work, but I really do think that the best mentors are the ones who you actually kind of find on your own, whether intentionally or unintentionally.

    Nicole Dove: Yeah, I agree, I agree.

    Tracy Bannon: Now, have all of your mentors been women? And the reason I ask that is that, when I look back over my career, a lot of my career, I’ve been the only woman in the room. So, one of the most impactful mentors to me was a fellow by the name of Scott Bar, and he was the wind beneath my wings. He just said, “No, you are this. Go and do this,” and he would open doors, not literally open the doors, he would open the door of opportunity and say, “You need to charge through that,” and we would talk it through. And I know that I would not be where I am right now had he not, you know, looked at this person a couple years younger and said, “What are you doing over there being quiet? Get up here at the table.”

    Nicole Dove: Yeah, so they have not all been women. One of my favorite and most impactful mentors was a man, Steve. I was working at audit and I audited him, and I think he was just really impressed with my preparedness, my executive presence, and he told me, he said, “If you ever need anything, let me know.” And I was, like, “Okay, I’m gonna call you,” [laughter] and I called him, right? And he helped me navigate some of the, at that point, some of the biggest decisions that I had in my career. And what I loved about Steve is that, you know, first of all, legal is much like cyber audit, it’s a service to the business, right?

    So he has a perspective of how you have to position your offerings in order to get buy-in, how to effectively manage relationships and rapport. Which is something that I might not get from another business leader, because, right, they are income-driving. What I also liked about him, he would always, sometimes, like, I was so young and, like, so ambitious, and he would just say, “Nicole, get out of my office. Like, what are you doing? What are you talking about, right?” And I loved the candor, because sometimes you need to tell super young ambitious kids, like, “A lot of things are timing. Not now.”

    And I can’t imagine, had I taken some of these opportunities that were just crazy, it would’ve rerouted my path. But having someone to ground me and tell me when I’m absolutely nuts, but then motivate me and push me. And what I love most – and I say I love most ’cause I love so much about Steve – he never tried to make a decision for me. He helped me think through the consequences and downstream impact of my options, and that is a great mentor.

    Tracy Bannon: That absolutely is, don’t tell me what to do. I may ask you for a little bit more guidance than what you’re giving me right now, I may say, “Let’s roleplay a little bit,” but don’t tell me what to do, and teach me, help me figure it out. 

    Nicole Dove: Yes, yeah.

    Tracy Bannon: I love it, I love it.

    Charlene O’Hanlon: That is great. So, you’re actually keynoting at RSA, this year, right?

    Nicole Dove: Yes, I’m so excited. I am really, really excited.

    Charlene O’Hanlon: So tell us about that, how did that come about?

    Nicole Dove: So, RSA, I mean, that’s like the godfather of the tech conferences, and I remember when I first got in tech, one of my peers had presented at RSA and I was just, like, “Wow – ” It seemed so big, so far, so great, and I was, like, “I wanna do that, one day,” because I really, really love speaking, and I love speaking about tech, and I love speaking about being a woman in tech. So, when I saw the open call for RSA, I was, like, “You know what, I’m gonna throw my name in the hat,” and I did, and it worked. So, I’m really excited, I’m gonna be on the C-suite track, and I’m going to be talking about how your business information security officers are your cybersecurity secret weapon. It’s a new emerging role in the industry, right?

    Many companies are starting to build this into their teams, their leadership teams, but I don’t know that a lot of organizations know how to best leverage them. And so, I think by helping them understand how to unlock all of the benefits, so I think it can really help take organizations and their cybersecurity programs to another level.

    Charlene O’Hanlon: That is awesome. I wish you the best of luck with that. That’s gonna be a great discussion. And, you know, do you have other folks who are gonna be speaking there with you, or are you doing it all by yourself?

    Nicole Dove: So I’m doing a solo presentation by myself, yeah.

    Charlene O’Hanlon: That’s great.

    Nicole Dove: Yeah.

    Tracy Bannon: Well, hopefully we see you there. I am hoping to make it there. It’s hanging in the balance, right now, but it would be fun to connect, yeah.

    Nicole Dove: Yes, listen, we won’t be hard to find, I’ll have purple hair, you’ll have pink hair, right? [Laughter]

    Tracy Bannon: That’s right. Form our own –

    Charlene O’Hanlon: With the grey hair, so. [Laughter]

    Tracy Bannon: All colors and coalitions, we’ll be doing it. You know, as we’ve been talking about mentoring, I had mentioned this to Charlene, earlier, you know, I try to really tailor where I spend my time, not to be stingy with it, but it’s very easy to bleed out by just wanting to be too many things to too many people. I noticed a trend across yours, you’re not necessarily at the food pantry, but you are – you know, and I don’t mean that as a negative, I mean you’re figuring out how do you get the most bang for the buck? How do you take the things that you’re doing during the day – it looks like you’re using that as a way to kind of tailor where you’re mentoring and how you’re leaning in. Is that fair to say? I mean, give some guidance to those listening on, how do you figure out where to mentor, where to build community, where to invest your time with the extracurriculars, you know, that are tangential to career?

    Nicole Dove: Yeah, I think the first thing is being intentional, right, and being self-aware. It’s, like, and it starts with your own journey. Everything that I pour into people is motivated by what I wish I knew then, right? Like, I strive to be the person that I needed then, and I think that begins to lay the roadmap for the communities you engage in, the perspective that you hope to share, right? And so, I think another big thing, too, is you can’t be everything to everybody, so it’s about carving out time for that specifically. So, for me, I typically will take mentoring calls one day a week, and I’ll block off, you know, maybe three or four hours, right? But I also, and maybe it’s not necessarily mentoring, because when I say – well, maybe it is.

    Because I see mentoring as more of like a long-term relationship-building, right? But I think sometimes, and I think you have to be – there has to be a finite amount of that. Because if I’m gonna mentor 50 people, I’m gonna give them just a tiny bit. I think they deserve more. So, I’m more than willing to have a 30-minute conversation and talk to somebody, you know, go through things and chat through things and pressure test things and brainstorm, right? But there’s going to be a reduced few that I really am gonna connect with and carry through that process. I remember I had a mentor, once, and she said, “I do this for one a year.” And I was, like, you know what, I love that, because it’s like we’ve got stuff to accomplish, we set goals upfront, we check in, and we make sure that we’re on the right path.

    And if we’re not seeing results, we change courses. But again, I think it’s all about carving out time, being intentional, being selective, both the mentor and the mentee, understanding what it is that you have to offer and what that’s anchored in and rooted in, and just finding your people. And some of it is trial and error, right? You don’t get it right every time, but you’ve just gotta start somewhere and it will all kind of it.

    Tracy Bannon: But you’ve mentioned that there were some very intentional mentoring relationships where you have goals that are set, and so, it’s more formal.

    Nicole Dove: Mm-hmm.

    Tracy Bannon: But there’s also another side of it that you hit on, which is, there are accidental or unintentional or casual mentoring that happens. Both are really valuable. I do have women that reach out who want soundbite guidance, which eventually turns into a little bit more. But you’re right, you kind of have to limit that, because, you know, that opinions that are provided without getting to understand them and know the context of their lifeforce, right, what’s their spark, what’s their essence. I can give them some generalities that they might be able to google [laughter] or they might be able to find in a book. So, the formality, did you find that the formality, making sure that you set goals with a mentor, helped, as well?

    Nicole Dove: You know, I think even in the casual mentorships, there is still a little bit of formality in there. Because I’m not going to set up time with, you know, somebody that I admire, just to, like, you know, shoot the breeze, you know? Like, it just, it doesn’t make sense. But there are spaces for that, right? But if I’m gonna take an hour or 30 minutes or 45 minutes out of your day, I wanna make it worth my while, right? And so, I think there’s always – we always have things that we’re working towards, right? And some of those goals are big, some of those goals are small. All are relevant.

    But I think making sure that, when you get access to this person with this knowledge and perspective that you wanna pull from, you make the most of that time, ’cause time is the most valuable thing that we have. And, you know, some personalities lean towards they need that structure, right? Some people, for the time, they need that structure. On the other side, you know, some personalities like it a little bit more fluid, that’s what works, go for it. But I think within both, we’ve gotta be intentional in what we’re hoping to gain and what we’re hoping to give.

    Tracy Bannon: Thank you for that. I learn something every time we have a conversation, every time that we engage in one of these, with any of the guests that we’ve had. Charlene, I think we’re running a little bit low on time.

    Charlene O’Hanlon: Yes, we only have a couple of minutes left, so I wanna actually close with one question, and maybe we can just kind of think about it, if we can’t actually answer it here. But what is the one thing that you wish you had done differently in your career?

    Nicole Dove: Not second-guess myself. Just go for it. Worrying is a waste of time. It’s a waste of time. Either you win or you learn, right? So, you know, winners never quit and quitter never win, so just keep going. If I would’ve just kept – I would’ve probably saved everybody so much time, including myself.

    Charlene O’Hanlon: That is great advice. I actually recently read something, somebody said something to the effect of, “You can’t run the race before it starts.” You know, you can’t worry about things that you really don’t have any control over, so, I love that, I love that, you know, stop second-guessing; just live your life, you know, in the best way possible. So, I think it’s great. Nicole, thank you so much for your time, your expertise, just for being so awesome. We really do appreciate your being on Techstrong Women. It was a great conversation. I sure hope you’ll come back for it and join us again on a future episode.

    Nicole Dove: Absolutely. Thank you, ladies, Charlene, Tracy, you are amazing, and I love this platform and what you’re doing.

    Tracy Bannon: Thanks, guys.

    Charlene O’Hanlon: Thank you. All right, everybody, we’ve got lots more Techstrong TV coming up, so stay tuned.

  • Tips for Better Governance – Techstrong TV

    Tips for Better Governance – Techstrong TV

    David Williams, VP of Porduct Strategy at Quali, and Charlene discuss David’s top tips to better governance in DevOps. The video is below followed by a transcript of the conversation.

    Charlene O’Hanlon: Hey, everybody. Welcome back to Techstrong TV. I’m Charlene O’Hanlon, and I’m here now with David Williams, who is the VP of product strategy over at Quali. David, thank you so much for joining me. Good to see you.

    David Williams: It’s good to see you, too, Charlene. It’s good to be here.

    O’Hanlon: Excellent, excellent. So, lots of stuff going on in the world of DevOps these days, but one of the things that we have been hearing a lot more noise about is governance in DevOps. And especially with just the insane amount of automation that’s going on to help kind of speed up the processes, obviously, it can be pretty easy for things to kinda go off the rails. So I wanna kinda get a sense from you as to what you see happening in the space with respect to governance in DevOps, and how we can kind of maybe move away from the herding cats mindset when it comes to governance.

    Williams: Yeah. It’s been a journey on DevOps. DevOps, when it was introduced many, many years ago as a concept immediately aligned itself with Agile, so it became only the ability to get things out as continuously as possible, and also as fast as possible. And so what happened is that at that time, things were very much managed. It was small teams doing lots of work. As enterprises started kicking in, with DevOps become a serious strategic way of actually delivering applications to their consumers, the amount of people got involved grew. 

      The amount of teams that were involved grew. Even though the DevOps philosophy was small teams, fast moving, application componentry going out into the ether as fast as possible, it stopped being that quite a while ago, and started becoming much more mainstream. So unfortunately, DevOps grew up a lot, and one of the things that became an issue was governance. And governance from that perspective wasn’t really just about security – y’know, SOC 2 compliance, and making sure that your secrets are held and managed efficiently across the pipeline – 

      but it was also around, how do you understand what people are doing? And what is the interaction that they’re having? And why are they having that interaction? And basically it’s a fragmentation challenge, more than anything else. DevOps pipelines are fragmented, and so how do you get control without inhibiting innovation? And how do you get visibility, having lots of teams that wanna innovate in their own areas, but not necessarily give you that full end to end? So that’s the challenge that has emerged. 

      And I think it’s going to continue to do that for quite a while to come, because the applications are getting bigger and more contention-based in regards to infrastructure sharing. So governance is gonna be the thing.

    O’Hanlon: It’s interesting, because I think of it a lot like a company itself growing out there. When you have two or three people working in a company, it can be very difficult to get a lot of achieved without everybody kinda going all in. But as a company grows, you’ve got more people who are doing the work, but maybe they’re not necessarily talking to each other, and not everybody has all the information they need. So you kind of have to kinda build a technology, or at least a process, around being able to get the information out and helping everybody be on the same page. 

      And it kinda sounds like the same thing is happening in the DevOps space with respect to just having a greater understanding. Not just an understanding of the process, but just, I guess, a better way of enabling the process from an understanding and a communication perspective – as well as just making sure that all the right things are getting done at the right time. So what do you guys propose? What do you see that you believe could make a real difference?

    Williams: You used two words that always make me smile when I talk DevOps. I used to be an analyst, talking to a lot of DevOps practitioners, and the two words that I used to run for the hills were “process;” y’know, that was one thing. And so they wanted collaboration, but they wanted to be able to collaborate without being governed in any way. So I think that that process word is one, and anything to do with “abstraction.” So abstraction’s not a good thing. It takes you away from the core. 

      So what I’m saying to you is that any solution that enables you to get greater control on governance and understanding has got to be able to do it without impeding people’s ability to do their jobs. And it’s gotta be something that is subsumed within their normal breathing in and out. It can’t be something that’s another job to do. That defeats the whole point of, anything that’s to do with lean practice is about removing stuff. We’re the software industry, so the way that we make things less complex is by adding something, y’know; that’s the normal inclination. 

      I think DevOps, when you actually use it, whatever you add into the mix has got to be subsumed within your normal day-to-day activities. So it can’t be yet another thing to do. For example, security has gotta be there, but not intrusive. Why I came to Quali was because I’d spent a lot of time with companies where infrastructure, the ability to provision into the cloud, do all the things, was becoming a bit of a mystery. People would assume infrastructure. 

      So the governance around what you’re deploying and how you’re provisioning your infrastructure not only became fragmented through your pipelines – Because you plan something, and then you code it, you build it, you release it, and test it, et cetera. Each one of those is a very defined area. It might be one person; it might be many teams. But each one of those is a very specific thing you have to do. But wouldn’t it be cool if you could subsume testing into your code? Wouldn’t it be cool if you could consume compliance while you’re coding? 

      So you’re coding, and it’s automatically looking at configurations and modifications, and logging that appropriately without you having to add another layer. And I think the same with infrastructure. I think that the companies I’ve worked for before really didn’t know what was going on, and I worked for DevOps companies that were trying to work out, “Okay, so the infrastructure was there; now it’s gone,” or “It’s there, and it’s modified.” 

      Every commit that a coder does is, y’know, a point in time. “So what has happened between that commit and the next commit?” And so all these stages of infrastructure, how do you build that in? So at Quali, what we looked at is providing a method with which you can let people use infrastructure as code practices, configuration management tools. Do what you need, but it gets automatically subsumed into a model. And the model is what you rate on. That’s what applies the policies around access and et cetera. 

      But it should allow the coders, the release managers, the testers to do what they need, but also it provides sort of like a control plane on top that enables you to talk and be governed, but without that Big Brother type of thing looking at you. So I think that’s the magic about DevOps, is if you add something in, it’s gotta be something that doesn’t get in the way of speed. It’s gotta not provide another barrier. It’s gotta do these things. It’s a hard problem to solve, but if you approach it in a way that assumes that people are going to do things, they’re gonna break stuff – 

      People do that; that’s what they do. They do their own stuff. They don’t like being told what to do. So if you can provide as subliminal a level of control over infrastructure that says, “I know how you’re doing it. I’m now going to provide that same capabilities that we used in build to help the testers understand what to build.” So now you’re providing some consistency across, using the control plane. So you’re using your models, and you’re moving them across. But it subsumes what they already use, so you can add it in. 

      Your infrastructure stack and the way that you deploy it is implemented in the model that has policy, access control, secrets integration. And so that’s really the philosophy, is to make sure that we can provide the end-to-end capabilities, accelerate the delivery life cycle, but not impede the practitioners from what they do, but provide the business with visibility which they do not have today. So I would just follow up by saying cost isn’t a governance thing, but unless you govern it, and you understand why you’re doing something, then how do you associate a cost of the cloud, if you can’t associate it with a pipeline? 

      At the moment, cost is associated with instances, and you’re having to group that together. What if you could provide the model with a value while you’re doing it, the application that you’re delivering on? And if you could do that, then you’re subtly applying what they do at the practitioner level with an application, with an owner, with a cost. So that is a way that governance actually comes in with the access, the controls, without being intrusive. We can basically provide all the capabilities there, and enable the business to get better visibility control over all sorts of things, including, for the first time, cost on the end to end. 

    O’Hanlon: Yeah, that makes a whole lot of sense. And in my mind – please tell me if I’m wrong – but it also means that the developers don’t really have to think about, how shall I say? They don’t actually have to learn more about something that would – If they’re moving from, say, a regular kind of a developer motion into more of a DevOps motion, it doesn’t require them to kinda add on a level of expertise that they might not need otherwise. This kinda does it for them, and kind of fills in the blanks for them, and also kinda helps other organizations or other teams within the organization understand the flow a little bit better, which makes a whole lot of sense. 

      And I think that may be part of kinda the governance conversation as well, is if we all have a greater level of understanding about what is happening at any particular time, we can better manage it.

    Williams: Yeah. I mean, secrets management, people hear a lot about that. They don’t quite know what it is when you talk to them about secrets management. I mean, something like a password or a username would be used maybe throughout a process, and it’s a shared piece of knowledge that you don’t wanna expose. So you keep that consistent throughout your environment, but keep the access controls consistent throughout whoever uses that access throughout the pipeline. One thing that we’ve learned is that DevOps isn’t a thing; it’s an interpretation of a thing. 

      The objective is very clear for people, but how they implement it can differ, depending on organization, application, design, et cetera. So what we also have to do is make sure that people with lesser skills – And I don’t mean lesser skills in regards to infrastructure; infrastructure can be cloud provisioned. But what if they have to manage all the networking components and the database instances, the things that aren’t inherent within a cloud-provisioning environment? 

      So we’ve gotta make sure that as developers of different skill levels interact with the infrastructure, we can fill the gaps for them, so they can do what they need to do, but if there’s networking, et cetera that needs to be managed, then the model should be something to give them the guardrails with which to implement that in support of the application requirements to that part of the pipeline. So it is something that we’re working on quite heavily, to make sure that we can get those guardrails in place.

    O’Hanlon: That’s great. And I think about all of the things that have kind of expanded DevOps, if you will, beyond the original parameters, including the implementation of DevSecOps, and the adoption –

    Williams: Yeah.

    O’Hanlon: – and DevNetOps, and all of these things that have kinda piled on top of DevOps. 

    Williams: [Chuckling] Yeah.

    O’Hanlon: It can be very, very difficult for the DevSecOps community, or the DevOps community, especially developers, to kinda have to manage all of that knowledge. So having those guardrails in place, I imagine, is going to be very well received by a lot of organizations, simply because we’re also talking about the dearth of talent in the developer community these days.

    Williams: Yeah.

    O’Hanlon: So anything that an organization can do to help ensure that there is a level of governance around the way their DevSecOps tools and practices and culture and everything is run, I think is a huge benefit. David, thanks very much for walking me through what you guys see happening with DevOps and governance. And hopefully this is an issue that is going to get better as we move forward. To your point, we do tend to throw technologies at problems, and hopefully this is one that will stick, if you know what I mean. 

    Williams: Yeah.

    O’Hanlon: So thanks again for your time. I do appreciate it.

    Williams: Right. Thank you, Charlene. It’s been a pleasure. 

    O’Hanlon: All right, everybody. Please stick around. We’ve got lots more Techstrong TV coming up, so stay tuned.

  • Apache Hop Integrates DevOps and DataOps – Techstrong TV

    Apache Hop Integrates DevOps and DataOps – Techstrong TV

    Matt Caster, chief solution architect for Neo4j, explains how open source Apache Hop projects advances integration of DevOps and DataOps. The video is below followed by a transcript of the conversation.

    Mike Vizard: Hey, guys, thanks for the throw. We’re here with Matt Casters, who is Chief Solution Architect at Neo4j and we’re talking about a new open source project called Apache Hop, that helps you move data round more easily. Matt, welcome to the show. 

    Matt Casters: Thank you very much for having me, Michael.

    Vizard: So walk us through what exactly is Apache Hop, what’s the problem we’re trying to solve, and it seems like we’re trying to move more data than ever, and when I was a kid people told me moving data was not necessarily a great idea, but we’re doing it anyway. So what’s the challenge and what are we trying to solve?

    Casters: Oh yeah, yeah. So that’s a great observation. I remember when everything was going to be the new mainframe, do everything in one box, right? And the opposite happened; we saw more and more services on prem, in the cloud, and all mixed up. See, I think, you know, more specialized services, in the cloud, on prem, graph databases, you know, advent of containerizations, virtual machines, and containers. So it’s become like a really complicated ecosystem out there and I think a lot of organizations are struggling to find expertise to service and cater to all those needs.

    I think what we’re trying to do is make the life of the developer easy by wrapping up user interfaces and easy-to-use tools around all these technologies so that you get like UMLI diagrams that you can work with and that can be easily understood by not only the experts but medium-level educated people on subjects, right? For example, if you’re working with a Kafka queue you might need to know how it works in general, but you don’t need to dive into the Java or Python APIs to get the best out of it. I mean that’s kind of it. 

    So lower the maintenance costs. And this comes down to the DevOps side of things. And while we try to make the life of the developer easy we position ourselves exclusively on the side of the organization. We’re not made to just make life fun for the developer, but we really try to make the life fun for the developer, but we really try to make life for the company or the organization that uses the software better. 

    So with that in mind you come to the conclusion that, okay, we need to also focus on configuration management, life cycle management, version control, unit testing, security investment, and that companies put into often many years of work of data orchestration, data integration, ETL work, right? So that is what I think Hop has been trying to focus on the last couple years by making sure that all these technologies are standard in the tool and easy to use. 

    Vizard: Do you think that we’re reducing the need for specialists, ’cause back in the day you had to have somebody who knew how to program with ETL and that capability and now with this we’ve got more of a visual tool, and maybe some people still prefer CLIs and APIs, but this is designed for developers to just easily handle this task themselves without any outside intervention, right?

    Casters: Yeah, that’s the lore. We fully acknowledge that it’s like a 95/5-percent kind of deal, right; you’re never going to do the last 5-percent without some scripting or coding. But solving the 95-percent is a big deal, it means that all of a sudden you open up possibilities to people that we would never have expected of using Apache Hop. Right? I’ve seen salespeople use it to extract the sales numbers from Salesforce. I would’ve never expected that in the past. It’s like, “Oh, they can figure it out.” “Oh, I can just enter the details: username, password.” “Oh, I can read this” and before you know it people start to use that. 

    Vizard: Citizen developers are here with us today. One of the things about Hop is that it’s lightweight and I don’t think people appreciate just how much heavy lifting went into ETL historically. So why does it matter that this thing is lightweight and metadata-driven and what’s the impact? 

    Casters: Well, at some point we saw the advent of LANDesk, you know, microservices, but also in its previous life, Kettle, before that was used was for plotting trains in more like an IOT settings. Call these Edge devices, maybe Raspberry PIs or very tiny devices. And there’s a real use case out there for a device that doesn’t have to do it or anything; it’s just trimmed down to the bare essentials for what it needs to do. Maybe it would be like measure temperature and air humidity and pressure and then send it off every 30 seconds or something, over some – using some Rescall. 

    And then this whole Hop library trims down to something like 30-40 megabytes and starts up fast and uses next to no memory. That is not in contrast to saying like, oh, maybe I run it on an AWS LAN in a small services. And it also gives us the ability to create new packets, right? You can only remove them, remove functionality, but you can add functionality quite easily as well. And that is really important. We’ve also already seen people implement machine learning or libraries or Python iteration and plug-ins for Hop. So this will be our next goal, is to create a marketplace around that plug-in kernel kind of architecture. 

    Vizard: Do you think that the functions of DevOps and DataOps are starting to converge more? Is this becoming more of a team sport or is DataOps just going to be folded into DevOps? What’s the relationship?

    Casters: Well, what I’ve seen personally is now that we have the ability to lock everything that a workflow or pipeline does into a graph, a Neo4j graph, it makes it easy to see where the arrow was, right? Can use graph algorithms to figure out not just where an arrow was, but figure out what the execution pat was in milliseconds. So the convergence of, “Oh, the developer has an easy time figuring out what went wrong, but also on Monday morning when you come in the office and see that the Saturday night run failed for some reason, or the monthly load of the data warehouse or whatever people are doing, they don’t have to troll through millions of lines of loading texts for a large workflow, but just see straightaway what went wrong, where it went wrong, saves a lot of time. 

    So is that DevOps? For sure. For sure DevOps. It’s also ease of development. There’s really like an overlap and we need to do better in providing a lot of these tools. They’re still too primitive in a lot of our software, As if locking text is enough, right? We can do so much more. [Laughs] We’re executing stuff; we know where it went wrong. Why guess? Why go through the effort? [Laughs] 

    Vizard: There’s a lot of focus these days on the volume of data that people are trying to work with, but it seems to me it’s also the speed in which that data is starting to emerge more, and people are trying to work in near-real time, and the data is going to be updated. We’re moving beyond batch. So are we really prepared for not just the volume of data, but the speed at which that data is starting to emerge. And for that matter, there’s a lot more types of that data, right?

    Casters: Yeah. So being from the Hop from the beginning opted to choose Beam to work as an abstraction layer so that we could execute on Spark, Flank, and Dataflow for the really fast use cases, but also, yeah, like real-time streaming, and just like playing, just streaming, Spark streaming and cloud Dataflow are really cool. And this comes along with the advent of all the streaming back-answer messaging services: Kafka, Pulsar, jewel clouds pops up. I think repertoire, right? I probably forgot like Azure. [Laughs] 

    But yeah, so these services have become really popular in making it possible to create cool Hop and Spoke architectures, where you can send stuff in all directions. Yeah, so it falls under the sort of like streaming category, and you can do all sorts of cool load-it-and-see exercises there. And opening that up is quite easy for us in Hop; all the pipelines are streaming, whether it’s in batch or not. So yeah.

    Vizard: So what’s your best advice to folks as they kind of look at these DevOps/DataOps challenges? What do you see as the best practice that people do the right thing? And for that matter, what kind of mistakes are people making that maybe they should avoid?

    Casters: So I think when it comes to these best practices, and then we’re talking about the classical list, put everything in version control. You know, keep your passwords and usernames and everything separate. Don’t hardcode anything. Like these are not specific to ETL data orchestration, but they’re genera programming best practices – development best practices. So even if it is like graphical programming, it still applies. Same with unit testing and integration testing.

    What we’ve seen in the past is that if you want to do, for example, unit testing, there’s a lot of plumbing that you need to put in place. So specialized Docker containers and so on and so on and so on. What we’ve tried to do is always look at the return investment of metadata. So what is the return investment for setting up like a lot of infrastructure and a lot of manual plumbing? It’s very low, right? So you see some benefit from a unit test like that, but it’s not great. So by building the integration testing and unit testing into Hop, into GUI, making it very easy to create, we’re saying like, “Okay, now you really don’t have any reason not to do it anymore. Right? [Laughs] Well, apart from laziness or not knowing what the value is. But at least those best practices are not different from any other development job that you might have.

    Vizard: All right, so we finally reached a point where we’re going to automate the orchestration of the data, just like the rest of any other DevOps process for that matter. So it’s onwards and upwards. Matt, thanks for being on the show.

    Casters: Hey, you’re welcome. It’s good to talk to you, Michael. 

    Vizard: All right. Back to you guys in the studio. 

  • Plutora Releases Test Environment QuickStart Bundle – Techstrong TV

    Plutora Releases Test Environment QuickStart Bundle – Techstrong TV

    Bob talks about Plutora’s new “Test Environment QuickStart Bundle”. It provides an easy, immediate fix to the Achilles’ heel of software development: environments that cause delays, produce bugs, and waste time and effort. The video is below followed by a transcript of the conversation.

    Alan Shimel: Hey, everyone. Welcome to another Tech Strong TV segment. I’m really happy to be joined today – I don’t know if he’s actually been on Tech Strong TV with us, but I’ve spoken to him many times; it’s my friend Bob Davis from Plutora.

    Hey, Bob, how are you? 

    Bob Davis: I am great, Alan. It’s so good to be here. I haven’t had the pleasure of being on the Tech Strong TV spotlight and it’s great to be here.

    Shimel: Fantastic to have you. So, Bob, our audience has been fed a steady diet of Plutora for years already, right? So most of them know Plutora, one of the leaders in the value stream management space, a DevOps pioneer leader. But I don’t know if they really know you. I’d like to introduce them to Bob Davis. 

    So why don’t we start there? Give them a little bit of your history, Bob.

    Davis: Sure thing. Alan, I’ve got a few years under my belt, and I started in the semiconductor business back at Intel as a chip designer. And I ultimately said, “Gee, you know, I think I understand why I want to build things bigger, better, faster and cheaper, but I don’t understand the business.” So I went and got an MBA and I moved into more of a product marketing orientation, and from there became a serial entrepreneur. 

    This is, Plutora is my tenth startup. I never joined another large company after I joined Intel, but I found my way into some through acquisitions and so forth: Novell, CA. Always on the software side, always on the, you know, typically the infrastructure, you know, a lot of enterprise IT, networking, compression, security, a lot of that, and ultimately back up in recovery and continuous data protection and those kinds of things, which ultimately led me to really understanding, wanting to understand more about the developer side. 

    And so about five or six years ago I found my way into Plutora and I became chief marketing officer and away I went. Along the way I became a pilot, I play golf, and love the water. So I’ve got a lot of things. And six grandchildren, so good stuff.

    Shimel: Six children. God bless you, man. Whoo. You know, I’ll tell you off camera; I don’t even want to get into it now.

    But anyway, that’s great, man. It’s great to have you here. And it’s interesting, ’cause you know what, a lot of people will hear “Bob Davis, CMO Plutora” and say, “Ah, he’s a marketing guy.” Well, yeah, but you’re a marketing guy who started off designing chips at Intel when a lot of people watching this were playing computer games, not even computer games, Show & Tells or whatever the heck they were. Right?

    Davis: Yeah. Well, I’ve always been on the product side and I’ve always been more on the “What’s the next idea?” In fact, the best example of that was right around 2000 – you know, we started Kaseya. 

    Shimel: Oh, I remember that.

    Davis: So I was the original founder of Kaseya and started that in my kitchen and it’s …

    Shimel: Really?

    Davis: Yeah. To being what it is today. And there wasn’t even a managed service provider market at the time.

    Shimel: No, I remember that early on. Because I had started a company called StillSecure and in 2005 we pivoted into MSSP. ‘Cause I just thought MSSP was the way to go. It was too hard for too many companies; they needed an MSSP. Actually Kaseya bought friends of mine, Carl and Billy Austin, they’re serial entrepreneurs as well. They were acquired by Kaseya. And then of course Kaseya was acquired, what was it, a year or two ago maybe? 

    Davis: Yeah, Inside Venture Partners bought Kaseya in 2013, which is when I left actually.

    Shimel: Right. Oh, okay.

    Davis: That’s when the new management came in. And we sold the company and kind of went off on our own journeys. I went to a company called Atlantis, which we were doing hyper-converged storage, and then ultimately Dalibor Siroky, CEO of Plutora, found me and brought me over to Plutora in 2017. 

    Shimel: Very cool. So, Bob, we were talking off camera a bit. We’re at an interesting sort of boundary layer here again. I think many of us are let’s call it cautiously optimistic that we are going to emerge from our kind of COVID cocoons and venture out again en masse. 

    Davis: Yes.

    Shimel: Many of us are already.

    Davis: Yes. 

    Shimel: The interesting thing is the world we left two years ago is a different place today than it was two years ago. We’ve learned a lot of things, we’ve experienced a lot of things. Digital transformation – no pun intended – has transformed many a business – many a business model. For us in the tech industry, for our audience, you know, the way they shop for products, try products, use products, measure flow in terms of value stream and stuff like that, it’s really changed in two years. They’re different. You can’t put your foot in the same water twice, right? And so companies like Plutora – someone once said that, I’m pretty sure. 

    But companies like Plutora, they’ve had a change. You’ve had to adapt. And you guys have. You have that sort of a whole new program you’re coming out in market with. Let’s talk about it.

    Davis: You bet. You know, in the beginning, right in the beginning of the pandemic, early pandemic, early 2020 we saw as the world was trying to find its axis again we saw an incredible increase in people wanting to learn. So they spent the first part of that 2020 just in this learning mode. And value stream management was one of the things that people were really focused on learning. And the notion of being able to say “Wow, if I could really see a pipeline, a value stream from the beginning to the end and understand if I’m getting better.” And that was really the question that the CIOs were asking, “I’ve spent millions of dollars on these tools. Am I getting better?”

    The point I’m making is that everybody was trying to understand how they could tell if they were getting better. And all these flow things became almost an MBA project or a PhD-type project to really understand all that’s possible. And that was awesome and we got a lot of interesting traction from that. 

    What we found, however, is that that transformation is a daunting transformation and the world changed around everybody. We went from distributed teams to distributed teammates. So now that autonomous team was distributed in and of itself, and the communication and collaboration became very difficult to achieve. So processes, organizations were changing. So many things changing all at once that people were really slowly doing like they’d be happy to go to an event, sit on a virtual show. What do I need to understand to get better?

    That’s not what’s happening today. Some of it, sure. Some of it still happens. But people are moving to more execution. They want to get value. They want to start seeing the value of that journey and they want to see the value in real-time. They don’t want to see it a year from now; they want to see it right now, this year. So we have seen our customers struggle with saying “How can I get started in value stream management? I may not even want to go all the way to the end of the value stream management journey, depending upon my specific tastes.”

    So we’ve developed an entire program around doing just that. How can we get people into a value stream process mentality, into a value stream platform, and do so quickly so that they can value right away. And so we have this program called the Quick Start Program and we released in January the first of several Quick Start products. This one is on environment management, which is a core component of value stream platform that Plutora sells. And in so doing we’re able to provide people solutions to a very complex test environment problem in three or four weeks, whereas today it can take 30 days just to configure and make an environment available on some of the prospects that we’re talking to.

    So in the time it takes to get an existing manually configured test environment ready for a test event you can have a full test environment management program and go from manual management of test environments to an automated process very quickly. Now I see value. Now I can see value in terms of the efficiency of utilization of expense and test environments. I can see better quality. I can see saving tons of money. 

    We find that people with average levels of releases, well UMA did a study and they came out and said the average number of releases in an enterprise environment was 76 a year. That was in a survey. They did a survey and they came back and said that was the average. There was certainly a distribution, but that was the average. And if you’re manually managing your test environments you’re losing money. They determined based on all the issues of managing these things almost $1.5 million a year you’re wasting. 

    And so we can save you that with a product like this. So imagine I’ve got a bottleneck in my DevOps tool chain, the Achilles’ heel of my tool chain is waiting for test environments as I shift left and try to test earlier. I solved that problem, I removed the wait states there, I become more efficient, I save money, and I can do that in about three to four weeks worth of setup. And now I’m rolling. Wow, I’m getting value. Now I go to the next problem and so forth. And I get quick starts, I can come into the platform pretty soon. I’ve got a full value stream management platform down the road. I’ve gotten value every step of the way and I never had to really think about the prospect of doing the whole thing. It’s like one step at a time; every journey is one step. So it’s like let’s give people the ability to get value in that same way, one step at a time. 

    And that’s really, it’s been met with tremendous success already. We’ve seen a lot of responses, a lot of people wanting more information, and our SDR team is very busy fielding calls on it. So it’s been a real successful launch so far.

    Shimel: That’s great. You know, Bob, I think part of the reason for its success is there’s two kind of trends you’re riding there. First of all it’s this, I call it “deliver delight,” but I mean that’s just two words, right? It goes to when I was an entrepreneur founder of companies we were hiring enterprise salespeople who sold to the C-levels and all that stuff. In today’s world we hire DevRel evangelists, and the idea is get the software into the hands of the people who are going to use it, deliver delight, and if it works they’ll tell their bosses and so forth to buy it. So it’s a different sales model. But it’s become dominant, especially in DevOps cloud native, you know, the kind of markets we play in. So this really is kind of playing into that. 

    Davis: Totally.

    Shimel: It’s delivering delight. Because synonymous for delivering delight is delivering value. 

    Davis: Yes. Well, that’s the point, right? Now it’s the whole point of value stream management in the first place. You know, it’s interesting; it’s really an agile approach to delivering the value stream management solution. There’s a parallel there. You know, saying “I’m going to buy a value stream management platform and implement it” is a little like deciding I’m going to build a waterfall process. ‘Cause it’s everything at once, this is what I want to do.

    Shimel: No, it’s like trying to eat an elephant.

    Davis: Exactly. 

    Shimel: You’ve got to eat it one bite at a time. [Laughs] That’s the only way you can eat it.

    Davis: Right. Well, you’re crossing – you know, by the very definition value stream management embraces both, you know, everything from the ops person on the far right to the strategic planning office on the far left, and so you’ve got lots of people, you’ve got lots of moving parts. It’s hard. We actually have found hard when we market the product we get the interest from the pain point, I’m having trouble. In this case I’m having trouble managing my environment. If you’re selling the entire platform that environ manager, in order to take advantage of that feature, has to sell the platform to the planning person, to the ops person, ’cause they’re all going to get affected. 

    There’s value there, but they’re like, “Show me.” Now we’re giving them a tool they can do that. It’s an on ramp into the platform, a smaller bite of the apple, as you said, an agile approach to delivering value stream management and value at the pain point level. And so we’re doing everything around it to make it super-clear if you have this pain, this is what it looks like in our product when you solve it, and you can get there by the end of the month. Does that sound reasonable? And it’s way cheaper.

    And so that’s the other thing, these platforms can be expensive. But what if I can buy something that’s in my sign-off authority, so it’s more approachable to me? The whole notion of S-a-a-S is all about product life growth and let me get something in my hands for free and try it out and then I can grow from there. That’s the beauty of what so many people have enjoyed with S-a-a-S-style software products. 

    Value stream management is hard in that sense, ’cause it’s complicated. There’s integrations into the tool chain, there’s process changes as people evolve from more legacy processing to DevOps tool chains and DevSecOps tool chains and so forth. There’s that. There’s organizational change, budget-holder changes, people moving from silos and project-oriented things to product-oriented things. So we’ve run into prospects that get so frustrated, they want the solution but there’s a lot going on in the organization. We’re answering that question.

    You can each have had a success, show the value, and go from there. It’s a great on-ramp. It’s a freemium approach almost in a complicated environment and its value stream management, and we think it’s really going to be awesome when people can have multiple. We’ll do probably deployment, we’ll have a quick start for master deployment plans. You know, Jeff was on in November talking to you about our progressive release management and some of the new stuff that we did with the Insights dashboard. That’s another screaming for of Quick Start, “Hey, wouldn’t it be cool if you could get this up and running very quickly?” 

    So all of those things is where we’re headed. We started with environment management and it was made available on the 18th of January and it’s already in the market, so we’re excited about it.

    Shimel: So no pun intended, but where can we get a quick start on this Quick Start? [Laughs] Where can we go, Bob? 

    Davis: Well, we have, there are online demos. You know, there are all kinds of spots on our website. We have a spot where you can say “Talk to me and you can sign up for that and have it by the end of the month.”

    Shimel: So just go to Plutra.com and check out the stuff for Quick Starts. 

    Davis: Yep. There’s a banner right on the top of the home page that will take you right to the information on it.

    Shimel: Love it. Good stuff.

    Davis: Yep. It’s all right there.

    Shimel: Hey, Bob, we’re about of time. I want to thank you for coming on and telling us about the Plutora Quick Start program. You know, the first one, as you mentioned, came out the 18th. Any timeframe on subsequent quick starts?

    Davis: We’re going to bring out the next one in the beginning of the next quarter, so right around April. 

    Shimel: Excellent, man.

    Davis: So you heard it here first, Alan. 

    Shimel: Well, that’s why we’re here. Thank you for letting us know. We’ll be watching. Good luck with this one. Maybe we’ll see you show up on one of the Plutora webinar workshops that you guys do with us so often. Love to have that.

    Davis: We’re going to do that.

    Shimel: Cool stuff. All right. Bob Davis, CMO Plutora here on Tech Strong TV. We’re going to take a break right now. We’ll be right back with our next guest. 

  • A New Development Model: Bringing SaaS Apps to Data

    A New Development Model: Bringing SaaS Apps to Data

    The last few decades have seen multiple major shifts in how applications are built and deployed, and now we’re seeing the start of a new shift that opens up enormous opportunities for all kinds of developers. Instead of bringing data to applications, developers are bringing their applications to the data.

    Let’s back up. In the 1990s, as data grew too large for local machines, applications moved with the data to data centers—a model more like the mainframes that preceded them. Then, in the 2010s, those same applications migrated from data centers to the cloud, bringing the data with them again. Now we’re seeing a third major shift, where customers take back control of their data and centralize it in the cloud. And developers are picking up on this trend, building their applications to not control their own data, but instead to connect to the customers’ data, letting them have and control a single copy.

    In a traditional SaaS application, the SaaS vendor stores and processes data in their own platform, even if that platform is running on one of the major public clouds. A traditional CRM (customer relationship management) tool, for example, will use its own data platform to store all of the data that all of its customers are managing with the tool. When a customer wants access to their data, often to join with other data sets, they either have to export the data (via APIs or CSVs) or upload the other data set into the tool and use whatever analytics capabilities the tool has built. This is painful for customers and also painful for the developer who has to support use cases that are further afield from traditional relationship management.

    In this new world, the customer runs and the applications all connect to the same data platform, storing and processing their data there. This means that joining two data sets is a single query away, with no movement of the data required. It also means that the customer owns and controls the data, making security and governance hurdles much easier for developers to overcome. And, because the customer pays for the data platform, the developer doesn’t have to mark up the costs and is able to command significantly higher margins.

    While it’s early, this shift is already underway. Fast-growing startups like Supergrain, Anecdotes.ai and Rudderstack, to name a few examples, are taking full advantage of this shift and leading investors have picked up on it as well.

    Why Now? Access to the Best Data Platforms Available

    There are two key trends that are leading to the emergence of these connected applications: The wide adoption of cloud data platforms and the prioritization of control over data by customers.

    In the last ten years, a new class of highly scalable and cost-efficient data platforms has emerged, allowing enterprises of all sizes to adopt technology that was previously only available to the most sophisticated vendors for use inside their own products. Previously, SaaS vendors had to roll their own complex data platforms that were very specific to their use case and charge high prices to cover the cost of running those platforms. Today, we’re not only seeing SaaS vendors migrate to cloud data platforms but also enterprises adopt the platforms themselves. This means that, for the first time, every enterprise has access to the best data platforms available.

    We’re also seeing a huge change in how enterprises think about and secure their data. Partly because of regulations, and partly because of publicity around data breaches, large and small companies are paying significantly more attention to how secure, how controlled, and how well governed their data is. When your data is spread across dozens or more different SaaS applications, it’s nearly impossible to guarantee its security and access controls. Centralizing that data into a single platform, and connecting your applications to it, allows for a single point of control and security for every piece of data.

    What’s In It For Developers?

    It’s clear that connected applications are a big win for customers: A centralized source of truth with strong security and control. But this model has enormous benefits for application vendors as well.

    First, it changes the go-to-market dynamics by letting you tap into work that customers have already done to centralize their data. According to George Xing, co-founder and CEO of customer engagement platform Supergrain, CEPs built with traditional SaaS models suffer from several drawbacks including long implementation times, poor reporting, and higher costs. The connected app model makes Supergrain more competitive, he said.

    “Instead of moving your customer data to a third-party data platform, we bring the marketing software to your data warehouse, unifying source-of-truth customer data and marketing product experiences into one cohesive system,” Xing said.

    It also accelerates time to market. Developers no longer need to build and maintain a data platform for their customers and can focus instead on their core product differentiators. They also get to leave responsibility for data security and compliance to the customer and their data platform.

    With the customer managing and paying for storage and compute directly, vendors can significantly increase their margins, charging for the value they provide, rather than trying to mark up the compute they’re consuming.

    What’s Next for SaaS?

    The incredible growth in the amount and types of data available to companies is only accelerating this shift in how applications store and operate on their customers’ data. We’re going to see more and more SaaS vendors support connected application deployment models, but it won’t replace vendor-managed models. Instead, there will be opportunities for both models to flourish depending on the customer and specific application. We expect that many vendors will offer both models, just as we’ll see others go even further, bringing their entire application—including its UI, logic, authentication, etc.—fully into the customers’ data platform.

    The opportunity for companies that take advantage of these new models is enormous, and we’re in the very early days. But the applications that take full advantage of this shift will be the winners of the next generation of data apps.

  • Survey Shows Steady DevSecOps Progress

    Survey Shows Steady DevSecOps Progress

    A survey of 200 DevOps and IT/information security professionals published this week by Mezmo, a provider of an observability platform, conducted in collaboration with the market research firm Enterprise Strategy Group (ESG), finds only 22% report their organization has a formal DevSecOps strategy to integrates security into their software development lifecycle (SDLC) processes.

    Among those that have adopted best DevSecOps practices, however, 60% saw an acceleration in incident detection, while 53% saw a reduction of incidents in production environments.

    Overall, the survey finds 62% of respondents report their organization is actively evaluating use cases for, or has plans to implement DevSecOps.

    Mezmo CTO Rob Fry said the primary challenge organizations face when it comes to DevSecOps remains cultural. In fact, 99% of survey respondents said establishing a culture of collaboration between development and cybersecurity teams is either critical (51%) or important (48%). Building cross-functional DevOps teams that have the required level of security expertise, however, is a major hurdle when there is a general shortage of cybersecurity expertise, noted Fry.

    The survey finds that on average it takes 17.5 person hours to triage and understand security incidents, an amount the survey finds that 82% of respondents desire to reduce.

    However, organizations are also struggling with the sheer volume of data collected by DevOps teams. More than half the respondents (52%) said the variety of data to be captured, analyzed and be acted on throughout the software development lifecycle (SDLC) hinders security efficacy/efficiency. A total of 43% said the scale of data to be captured, analyzed and acted on throughout the SDLC also hinders security efficacy/efficiency.

    Organizations surveyed capture several (54%) or even hundreds (32%) of terabytes per month, with 6% capturing a petabyte or more per month. Well over two-thirds (69%) do not capture certain data sources because of the high cost of storage/retention, which Fry noted is going to be problematic if there is an incident. Log data (35%), followed by metrics (29%) and traces (22%) account for most of that data, the survey finds.

    In all, 84% of respondents said getting the right data and tools to developers is key to achieving success. A full 91% of respondents are using multiple tools to get the most value out of their data. Two-thirds (66%) have dedicated logging analysis tools, while 59% have a security information event management (SIEM) platform. Cloud to two-thirds 64% have a data lake hosted in the cloud, while 55% have one in an on-premises IT environment.

    A full 87% are using open source tools as part or all of their observability stack because they are more customizable. However, 84% noted that over time it will become challenging to manage, adapt and scale with these solutions. Nearly all survey respondents (98%) said they will likely investigate a managed observability solution over the next 12 months.

    The application security issues that plague organizations today have been around for decades, so it’s not likely they will be resolved in a few short weeks. On the plus side, at least, there’s now a lot more awareness of the root cause of the problem than ever.

  • Building a Platform for DevOps Evolution, Part One

    Building a Platform for DevOps Evolution, Part One

    Winston Churchill once said, “To improve is to change; to be perfect is to change often.” While nearly everyone will confess that change is necessary to grow and succeed, we all know it’s much harder, especially when human behavior is involved. Professionals who work in DevOps environments know this all too well.

    Adoption of DevOps principles and behaviors should be viewed as a gradual process. Many organizations make false starts or attempt to implement a change only to see it fail. Sometimes this is due to changes in leadership, market conditions or technology, but then organizations catch their second wind, build momentum and reaccelerate their evolution.

    DevOps can Change

    With a shared vision, mutual goals and hard work, DevOps can change to keep up with user demands. DevOps professionals will always confront two potent barriers: Cultural and process debt and technical debt.

    Cultural and process debt occurs when leaders refuse to delegate authority, distrust their teams and lack a value stream approach to work. Technical debt develops when monolithic systems are tightly coupled, automation is delayed for testing, environments and version control and there is no access to cloud technologies.

    Although these obstacles are challenging and complicated, many organizations still meet them head-on. Evolution depends on a habit of making improvements every day through the use of an improvement kata such as PDCA (plan, do, check, act), which involves long-term strategies and objectives and continual experiments between the current and next target states.

    An evolving DevOps approach maintains moving pieces across a large organization of hundreds, thousands or even tens of thousands of people who cannot change overnight. Many lack the will and the cognitive capacity to embrace and enact change.

    This environment requires release managers to delegate power and transition from centralized commander to an enabler, understanding different value streams have varied skills and requirements. Mark Peters, a cybersecurity specialist and DevOps leader with years of military operations experience, outlined his top release management traits in the context of DevOps ways of working as automated processes, distributed accountability and accelerated delivery.

    PDCA Improvement Kata

    DevOps proposes that we adopt an improvement kata in our day-to-day efforts as an improvement habit, consisting of four steps that are repeated:

    1. Set the long-term vision
    2. Understand the current state
    3. Identify the next target state
    4. PDCA between the states

    Experimentation is at the heart of the PDCA cycle. The most practical experiments are empirical, data-driven and date-specific. Using a value stream management platform to give data to support the experiments leads to data-driven discussions on real and measurable success.

    In the next part of this series, we will begin exploring different experiments DevOps organizations can conduct to drive change and improve their release management procedures.

  • Five Great DevOps Job Opportunities

    Five Great DevOps Job Opportunities

    DevOps.com is launching a weekly DevOps jobs report today through which opportunities for DevOps professionals will be highlighted as part of an effort to better serve our audience.

    Our goal in these challenging economic times is to make it easier for DevOps professionals to advance their careers.
    Of course, the pool of available DevOps talent is still relatively constrained, so when one DevOps professional takes on a new role it tends to create an opportunity for others.

    The five job postings shared this week are selected based on the company looking to hire, the vertical industry segment and, naturally, the pay scale being offered.

    We’re committed to providing additional insights into the state of the DevOps job market in the weeks ahead. In the meantime, here are five DevOps jobs for your consideration:

    Indeed.com

    Mayo Clinic
    Phoenix
    Senior MLOps/DevOps Engineer
    $121,701 – $176,446 a year – Full-time

    Dice.com

    AWS – Professional Services
    Anywhere
    DevOps Engineer
    $131,000 Base Pay

    LinkedIn

    Kasisto
    New York
    Director of DevOps
    $160,000 to $180,000

    Monster.com

    University of North Carolina
    Chapel Hill, North Carolina
    DevOps Developer
    $80,000 to $95,000

    SimplyHired

    Tide Cleaners
    Cincinnati (Preferred)
    Senior DevOps Engineer
    $120,000 to $160,000