Author: Alan Shimel

  • The 2020 DevOps Dozen² Awards Nominations Are Now Open

    The 2020 DevOps Dozen² Awards Nominations Are Now Open

    The DevOps Dozen Awards are back for their sixth year and open for nominations. We are excited to celebrate the hard work and continued success of DevOps leaders, whose achievements over the past year deserve recognition. This year, we have expanded our awards program to include two different DevOps Dozen sections; hence, the name DevOps Dozen² (Squared).

    There are a dozen awards for each section this year:

    • DevOps Dozen Tools and Services Awards — 12 awards recognizing the companies that develop and deliver outstanding solutions to empower developers, DevOps and IT operations teams.
    • DevOps Dozen Community Awards — Closer to the original vision that we had with the DevOps Dozen when we instituted the awards five years ago, these 12 awards honor the leaders who have made a positive impact in the DevOps community.

    Nominations are made by the audience. However, it will work a little differently for the Tools and Services Awards categories than it will for the Community Awards. While anyone can nominate a tool or service for the final phase this year, there is a $250 fee for each Tools and Services nomination. This is meant to cut down on the spam and superfluous nominations we have received in the past.

    We are interested in serious tools/services in the DevOps space. Nominate only those you think are truly deserving of an award. Commercial tools/services are not eligible for the Community Awards and will not make it through to the finals.

    Winners will be chosen from among the finalists, with general public voting accounting for 40% of the final total and our judges’ selections for 60% of the total.

    The last day to submit your nominations is Oct. 15. To vote, follow the steps outlined on the DevOps Dozen² website.

    Meet the Judges

    Who are this year’s judges? You may already be familiar with their names. The 2020 panel will be lead by:

    • Alan Shimel, founder and editor in chief, devopsy.kinsta.cloud
    • Jayne Groll, CEO and co-founder of the DevOps Institute
    • Mitch Ashley, CEO and founder of Accelerated Strategies Group
    • Charlene O’Hanlon, managing editor, MediaOps Inc.

    The 2020 DevOps Dozen² Categories

    DevOps Dozen Tools and Services Awards

    1. Best End-to-End DevOps Tool/Service
      Consolidation in the DevOps space has led to a greater selection of platforms offering end-to-end solutions. This award honors the platform with the most diverse and robust solution for DevOps teams.
    2. Best DevOps Repo/GitOps Tool/Service
      Git has led to GitOps, which has become an integral part of the DevOps toolbox. This award is presented to the most outstanding Repo/Git/GitOps tool.
    3. Best CI/CD Tool
      This award recognizes the best CI/CD tool that helps teams to deliver quality code better.
    4. Best Value Stream Management Tool
      Value stream management has come into its own as an important tool for measuring the business value of DevOps and application development. This award recognizes the value stream management tool that most effectively helps visualize the value stream, track metrics and measure improvement.
    5. Best Observability Solution
      This award recognizes the best observability solution for observing and monitoring to understand the performance of individual components and systems and entire applications.
    6. Best DevSecOps Solution
      This award honors the best DevSecOps solution, which enables security to be included earlier and continuously throughout the SDLC.
    7. Best Testing Service/Tool
      Testing is a mainstay in the DevOps toolchain, and this award recognizes the best testing tool for ensuring the quality of code.
    8. Best Kubernetes Platform/Service
      The adoption of containers has paved the way for an entire solutions ecosystem supporting and enhancing the container technology. Kubernetes is perhaps the most widely recognized and utilized tool in the space. There are many platforms and services that offer Kubernetes-based solutions. This award honors the best Kubernetes platform/service available.
    9. Best Cloud-Native Security Solution/Service
      The cloud-native movement has taken the IT world by storm due to the depth and breadth of the solutions available and the benefits of building applications and services specifically for cloud-native environments. This award recognizes the best tools, solutions and services considered cloud-native.
    10. Best DevOps for Mainframe Solution
      Mainframes are far from being the dinosaur of the IT world, and a variety of solutions are available for enabling DevOps practices in mainframe environments and hybrid environments. This award recognizes the best of them.
    11. Best DevOps for DataOps/Database Solution
      Databases often have been left out of the DevOps conversation, but that is changing. Recently, the whole concept of DataOps has started gaining traction. This award recognizes the best solution in the database for DevOps and DataOps categories.
    12. Best New DevOps Tool/Service Provider
      This award recognizes the best new service provider or tool that has brought innovation to the DevOps space in the past year (must be less than 24 months old).

    DevOps Dozen Community Awards

    1. Best DevOps Industry Implementation
      This award honors organizations that have successfully adopted and implemented DevOps principles and practices.
    2. Best DevOps Survey/Analysis/Research
      This award recognizes research that has significantly and positively impacted the DevOps community.
    3. Best DevOps-Related Video Series (video)
      This category highlights the most entertaining, educational and inspirational DevOps video series—those with the most engaging and highest-quality content.
    4. Best DevOps-Related Audio Podcast Series
      Which is your favorite DevOps podcast from this year? There are many great DevOps podcasts sparking some interesting discussions on a multitude of topics from CI/CD and testing to DevSecOps, Kubernetes, containers and more.
    5. Best DevOps Book/eBook of the Year
      Each year sees a plethora of well-crafted DevOps-related books and ebooks. This category highlights the most popular and best read of the year.
    6. Top DevOps Evangelist
      This category is one of our favorites. There are so many great evangelists who spread the DevOps gospel and we want to know who does it best. Nominees can work within the DevOps space or outside of it.
    7. Best DevOps Transformation (non-vendor)
      In a year in which digital transformation became a must-have for survival, which organizations stood out in their efforts to transform their business through DevOps?
    8. Best DevOps Virtual Event of the Year
      COVID-19 has changed the game when it comes to hosting events. In 2020, virtual events have become the new norm, reaching a global audience while everyone stays safe at home. Which DevOps virtual event stands out from the others?
    9. Most Innovative DevOps Open Source Project
      Open source projects are meant to promote innovation and increase efficiency, velocity and quality. While there are many great open source projects out there, the best ones are those that create a community of people who work on and with the technology and support each other.
    10. DevOps Executive of the Year (non-vendor) This category celebrates excellence among DevOps leaders at the C-suite (or equivalent) levels.
    11. Best DevOps Presentation of the Year
      This category recognizes the best DevOps-themed presentation from the many (virtual) conferences during the year.
    12. Best devopsy.kinsta.cloud Article of the Year
      devopsy.kinsta.cloud publishes multiple new articles every day. Which was the best article from 2020? Let us know so we can recognize the author.

    All the solutions nominated to the Tools and Services Awards will automatically be registered into the DevOps Tools Guide authored by MediaOps and Accelerated Strategy Group. This initiative is our effort to create a comprehensive listing of tools and tools vendors to help end users better understand the DevOps market landscape.

    With so many talented and passionate leaders in our community, choosing a winner is no easy task. Though not everyone can take home the award, I truly believe every single person who is a part of this great community and has done some remarkable work to empower and support other members of the DevOps community is a winner. By acknowledging them in our award process, we want to highlight their work and show how important they are in the DevOps space.

    For more information on the awards, please visit the DevOps Dozen² website. If you have any questions regarding entry process, awards, timing or any technical issues regarding the website, please contact us at DD@devops.com.

  • TechStrong TV: Credentials Management, with strongDM and Software.com

    TechStrong TV: Credentials Management, with strongDM and Software.com

    Now more than ever, businesses around the world should pay close attention to how they manage their credentials and control access to their sensitive data, in order to protect it from being hacked or compromised in any way.

    During this interview for TechStrong TV, Mason McLead of Software.com and Elizabeth Zalman of strongDM, discuss the great responsibility of safeguarding credentials and how strongDM has proven to be an effective credentials management tool, helping Software.com to control access and keep their data safe, even when working from a remote environment.

    Software.com is a data platform dedicated to help developers and engineering teams learn from their data, increase productivity and improve their coding routine.

    Check out the interview below and follow along with the transcript to find out more.

    Transcript

    Alan Shimel: Hey, everyone, thanks for joining us on another episode here of TechStrong TV. We’ve got our recurring guest friend, Elizabeth Zalman, of strongDM joining us, here—hey, Liz.

    Elizabeth Zalman: Hey, Alan.

    Shimel: And joining—hi—and joining Liz and I is Mason McLead of Software.com. Hey, Mason, welcome to TechStrong TV.

    Mason McLead: Hey, thanks for having me.

    Shimel: Alrighty. So, Mason, you’re the new kid on the block, and we’re gonna give you a chance to lead things off. I think a lot of our audience has certainly heard of Software.com if they’re not really, really familiar with it. But for those who aren’t, you know, why don’t we give them a little background?

    McLead: Sure. I mean, high level, Software.com is a developer data platform, and our aim is to create and provide insights for productivity for individual developers as well as engineering teams. And we do this by gathering telemetry data from inside of code enders and then layering on contextual data from other parts of the software development life cycle, like how many hours you’ve been at meetings, what kind of music do you listen to while you code, do you code during work hours, after work hours, at the office, remotely—and then really pain the full picture of where your time goes and how it’s impacted by these external inputs. And that’s what we provide back to developers as kind of the product there, so you can really see how your time is impacted and what you’re doing throughout the day in order to improve.

    Shimel: Very cool. And then, Mason, we should tell people or at least give them a little background—what’s your role at Software.com?

    McLead: Yeah, so, I’m the CTO here at Software, just joined this year. And you know, it’s an exciting time to join in. The product’s been out for a while, and so, there’s a lot of proven track record and it’s just taken to that next level, and I’m excited to be here.

    Shimel: Very cool. And, you know, we do have Liz from strongDM here, so the obvious question is, you guys are using strongDM, I’m gonna assume. Talk to us—why? What’s happening that strongDM was a solution for you?

    McLead: Yeah. I mean, the main thing—and this is actually the second time that I’ve signed up to use strongDM. I used them before at my previous company I worked at, Fair, it’s a fintech company. And the real premise is that, you know, at Fair, it’s in fintech, so we gather a lot of personal information. At Software, it’s a lot of information about your behaviors and all of that stuff.

    And it’s just personal information, and I feel like, in the role that I have of being CTO, I have a responsibility to protect that, and I really, personally, feel like it’s a moral obligation to protect my users’ data. And strongDM helps me do that in a number of ways. And so, it’s been a rock steady foundation that I always build into the tech stack whenever I go and build something now.

    Shimel: Excellent. So, you know, you opened the box, we gotta see what’s packed inside—what are the number of ways why, you know, you can’t just leave us hanging there.

    McLead: Sure. [Laughter] Yeah, I’ll enumerate. So, for getting access to developers—and the classic way that you do it for databases, right, is you have credentials that you share amongst however many developers need access to that database. Which means, as soon as you rotate that password, if you do, then you’ve gotta update everyone else. And now you’ve got copies of passwords everywhere on people’s local machines. And not everyone stays at a company for their entire life, so whenever they leave, you must do something about that. Like, that credential is now out in the wild, and there’s not very many good tools to manage that.

    So, strongDM really fills that gap really, really nicely, that use case. So, we can issue credentials automatically for people as they come on. We use Gusto for our HR stuff. So, if they’ve got an API, we can just—as soon as someone comes online, we can issue them credentials to data stores immediately. And then, if they go offline to their contractor, they’re immediately revoked. And the perimeter of the security just gets really tight and really well controlled, which is such a relief for me.

    And then on the other side, securing access to servers via SSH, and we’re also deploying a new Kubernetes cluster, controlling QTTL access, and having all of that be auditable, because we also have some contractors working on our database so we can see what commands they’re running, what queries they’re running, and be able to trace that all back. And being—like, most of the time we’re not, of course, looking at the audit trails. It’s really, like, knowing that it’s there if something happens, we’ll know exactly how to trace that back.

    Shimel: Love it—very, very good stuff. And, you know what, I applaud your personal, you know, taking this, I’m gonna call it fiduciary duty or responsibility for safeguarding people’s really personal data—you know, for taking it personally like that, no pun intended. And, you know, maybe if more people did, we’d be better off.

    Though, look, no one ever raises their hand and says, “I wanna be breached,” right? And even sometimes doing everything you can, it’s still not enough in order to prevent these things, but you can certainly take precautions, you can make it harder by using tools like a strongDM and so forth. So much—I had a friend of mine call me last week, an old client of mine from my security days who, unfortunately, they got to pretty bad. They got into his Charles Schwab account, they got into his payroll account, they got into all of his e-mails. And he’s in the merchant processing business, so there was merchant applications—it was crazy. And, you know, he was beside himself. On the other hand, he didn’t use a password manager—you know, typical kinda things you hear. So, it happens.

    Anyway, but it’s interesting, you know, that across verticals, right, from fintech to what you do now at Software.com, though the mission may have changed in terms of the business, you know, goal, the mission in terms of protecting data hasn’t, is still relatively the same.

    Liz, is this—is Mason’s experience, Mason’s motivations typically, you think, for strongDM customers across the board?

    Zalman: I think our customers feel deeply that there is—our customers feel deeply that there is a right way to do things. I think Mason, as an early customer of ours and at Fair, I think came in it from day one, just had a very particular point of view on how things should be done. I think he was actually one of the first customers to even be deploying Kubernetes in a production environment.

    And so, our buyer is the head of infrastructure or infosec or DevOps as a way that they want to do things, it’s always very forward thinking. And finding a way to do them in an automated fashion that sort of fits into these, you know, Infrastructure 101, the ABCs of how to set something up in a way that helps them scale is probably a core precept that they have. I mean, Mason, how big are you guys now at Software when you inherited the team?

    McLead: When I inherited the team, there were five other engineers and we’ve grown that up by about 50%. So, it’s still small and growing, but you know, I think no matter the size, the problem is still the same. And, for me, the solution’s been the same, too.

    Zalman: Yeah. Yeah, so, at Fair, I think you guys were maybe 100 people who were touching some form of infrastructure, and here, Mason’s starting, he started at six. So, yeah, certainly, it’s like, when you know that there’s a good way to do something and a right way to do something, you start it right at the beginning.

    Because, to do that when you’re a thousand people is—you can do it, but it’s a two year process of rinse and repeat sort of work group by work group. You do it right from the start and you’re off to the races.

    Shimel: Well, if we all had the luxury of starting in a green field, right, and starting it from the beginning as it grows—what a wonderful world it would be, as they say. But unfortunately, we don’t, right? There’s a lot of brown field—muddy brown fields out there.

    Mason, let’s talk a little bit—and Liz as well—let’s talk a little bit about, you know, so, this whole COVID thing comes up now, right? We’re all here, you guys are in your houses doing this interview—what, if any, effect has that had on the business and has strongDM helped, hindered, not been a factor in that?

    McLead: Yeah. So, actually, Software.com was fully remote from the very beginning. So, internally, it hasn’t made a big difference in how we work. I think it’s an upgrade—like, going to strongDM for access control is an upgrade, no matter how you work. I think it’s probably more important whenever you’re remote—I mean, people have central VPNs and those sorts of things, but it’s still, building that defensive wall in strength and depth is still the right move there.

    And so, internally, it hasn’t affected us too much, just because of the way the company is set up. For the business itself, though, it actually highlights a big advantage that we can provide as part of our products, of being able to see productivity metrics between remote and in office. Because people are gonna have a big choice coming back in from COVID whenever this is resolved of how much office space do I actually—do I need an office? And then how do they actually guide that discussion and that decision when you don’t have data around it? And that’s where we can really fill a gap there between knowing how people are working remotely and how they’re working in the office, so you can have a real comparison.

    Shimel: Wow, what a great use case that is. I’m sure that was one of the use cases they drew up when they were starting the company, right? If there’s a worldwide pandemic and everyone’s working from home, wouldn’t it be great to know how well they’re working from home?

    McLead: Yeah, it’s amazing the foresight we had. [Laughter]

    Shimel: Yeah. But, nevertheless, it’d be nice to have there. You know, I wonder about that issue, question myself, though. I mean, here, you know, we’re a small company, we’re about 23, 25 people, and everyone’s remote now except for me and my video director and, you know, we’ve—we have three and a half years left on our lease. Actually, September, it’ll be three years, so three years left on the lease. So, I’m stuck with, you know, this for three years. But I don’t see people running back, and if they do, they might just come in a day or two a week.

    And, you know what? That’s fine. As the CEO here and founder, it’s fine with me. We’re working fine remotely. No one needs to necessarily be here to do their job, though I do think there is—there is some good you get from having people in the same office, whether it’s the water cooler or hallway talk or what have you. But that is—you know, that’s the new normal, that’s the new now, and I think we need to get used to that.

    Liz, you know, again, in any situation there are winners and losers. But this whole COVID thing has—you know, not your fault, obviously, right, but it’s given people a reason to say, “Jeez, I need something like a strongDM,” right? “I want to spin up my remote force” or, “I want to—we need to secure it better” or what have you. What are you hearing from companies? You know, Mason’s a two time user already—but first time people, what are they saying when they come by?

    Zalman: Yeah, Alan, I am the mastermind behind COVID, you just—

    Shimel: Yeah, exactly. [Laughter] Dr. Evil, okay—we got ya! [Laughter]

    Zalman: No, yeah, Mason is certainly in a subset of companies that enjoys being remote from the start and being able to build that way. We saw a doubling down of an existing customer base where even if they had remote or satellite teams, now everybody became distributed. But also, new people reaching out because traditional companies, you can’t rely on the corporate network as a perimeter any more. It’s dead. It’s just—it’s completely gone and you had to switch on a dime, and what do you do?

    And I can’t even imagine—you know, by deploying strong, oftentimes, you can just throw out the VPN. Many customers choose to do that. And I can’t even imagine what these poor IT folks were dealing with in old companies who, you just had to go into the office, there was no other way of working, all of a sudden getting all these requests, “I can’t connect to the VPN” or any sort of IP-based white listing. Oh, my God, to get access to privileged systems? My heart goes out to them.

    Shimel: Yeah. No, you know what, I actually did an interview last week from an analyst based up in Canada who just put out a report about, you know, how COVID caused a short term increase in people buying concentrator licenses and more VPN capacity, but how long-term, that’s probably throwing good money after bad in terms of out the window. I mean, you gotta just—you gotta re-architect is the bottom line, there.

    But it’s hard to do an engine transplant in the middle of the race. And so, people get stuck, you know, in those situations.

    Zalman: Well, as one of my investors is fond of saying, “You gotta build the Ferrari while you’re driving it.”

    Shimel: Yeah, and that’s—ain’t it the truth? I hear ya. Mason, what about you guys at Software.com? I mean, are you just ready for the new normal here and you were remote, anyway? Because there’s a part of—look, we can function in this environment, that’s fine. But are your customers functioning in this environment? Because ultimately, if they cease to function, no matter how high functioning you are, you know—big deal.

    McLead: Yeah. I mean, developers are customer based, so we’ve got to make sure that is continuing to function, yeah. You know, we’ve actually taken surveys on this for our customer base, which is nearing about 100,000 and the majority actually said that they would want to do a bit in the office and a bit remote. So, kind of a mixed use case, there. And I think that that fits really well to get the advantages of being able to control your own schedule and control where you are with the in person being able to white board together, being able to really come together and think of new ideas and I remember all the hours that I spent in the office at Fair with a tight group of people developing all the stuff that we did there, and there are definitely some advantages to just being able to randomly yell out to the person in the other room to go and fix something.

    So, you know, I think that it’s gonna be a mix of that, and you’ll have some people that’ll wanna go full remote once they’ve had the taste of it. Like, I really enjoy it. Like I said, and you can tell by the bare room behind me, I’m moving this week, actually, and it’s really interesting to start to feel the effects of being able to live anywhere and work the same job. Like, having it completely disconnected is a new feeling for me, and it’s weird, but I like it. And so, you know, I think [Cross talk] –

    Shimel: I think we’re gonna see it.

    McLead: Yeah.

    Shimel: Yeah, no, I think—look, I read an article, I forgot what percentage rents in San Francisco are down, right? I think we’re gonna see rents going down in a lot of the cities because people are realizing where they work from physically is not necessarily tied any more to where the company is based.

    Now, you still want to hire people with skills in places like New York and San Francisco or Austin or Boulder. They still have high concentrations of people with skills, so it pays to maybe put an office there. But, you know, I’ve had this conversation with Sid Sijbrandij, the CEO/founder at GitLab. They got, like, 1,200 people in 1,200 offices, because they don’t have an office. Everyone, including Sid, works from home, and his thing is, you know, for newer companies, it just doesn’t pay, because you know, once you put an office down, you’re saying, “That’s it, I’m only gonna—I’m confined to that talent pool.” Where, if you wanna swim in—you know, have choices in a wider talent pool, you’re not big enough to open an office wherever you’ll find talent.

    And so, you know, a remote force is probably the way to go. I mean, good for Liz and the strongDM team, right? But that’s—I think that’s part of where we might be headed.

    McLead: Yeah, and I think if you limit yourself to one specific geographic region to hire from, you’re limiting the upside of your entire company.

    Shimel: Yep.

    McLead: And incurring costs along the way. [Cross talk]

    Shimel: Absolutely.

    McLead: For the corporations that can do it.

    Shimel: Right, I think that’s an outdated look.

    McLead: Yeah, I think so.

    Shimel: You know, I think that’s where we’re headed. Anyway, guys, we’re about out of time. Mason, I told you the 20 minutes goes quick, because usually Elizabeth talks so much, she takes over the whole conversation—no, she doesn’t. We’re just kidding.

    But I’m gonna give you each a chance to say something before we log out, here. Mason, you’re the new kid on the block, so why don’t you go first?

    McLead: Okay. Well, again, thank you for having me on, and it was a pleasure to talk about what we do at Software where it’s a developer data platform designed to help developers individually to see where they’re spending their time, look at productivity metrics, and improve, as well as helping manage the entire software development life cycle from input all the way through output. And thanks to Liz for strongDM and strongDM for a great product that helps us secure our data. It’s definitely a huge benefit that I put into every stack that I build now.

    Shimel: Very cool. Elizabeth, I’m giving you the last word.

    Zalman: I think Mason just summed it up for me, although I think my hair is better than his, so, I’m gonna retain that for me. [Laughter] [Cross talk]

    Shimel: I think both of your hair is better than mine, and we’ll leave it at that. [Laughter]

    Zalman: I don’t know how his looks so tight—dude, who’s cutting your hair?

    McLead: I cut it. I learned how to—I watched YouTube. I missed this part here, but—

    Shimel: Yeah, no—you know what? I think that’s been a thing. I mean, yeah. It’s easier for guys than it is for gals, I will say that.

    Zalman: I commend you, Mason, both on your haircut and your choice of infrastructure technology products. [Laughter]

    Shimel: Very cool. [Laughter] Guys, on that note, we’re gonna call it a wrap. This is Alan Shimel for TechStrong TV. Elizabeth Zalman from strongDM, Mason McLead from Software.com—thanks for being our guests. We’ll be right back with our next interview.

  • TechStrong TV: The Low-Code Movement, With ServiceNow

    TechStrong TV: The Low-Code Movement, With ServiceNow

    ServiceNow is well-known for its IT transformation products and customer/employee workflows. But the company has another technology, App Engine, a low-code application platform that lets people build applications faster than they can on any other platform.

    In this TechStrong TV interview, I speak with Josh Kahn, general manager of the platform business unit at ServiceNow, about App Engine and the evolving low-code landscape, which is a very hot topic in today’s business environment. The video is below followed by a transcript of our conversation. Enjoy!

    Transcript

    Alan Shimel: Hey, everyone. Thanks for joining us on another episode of TechStrong TV here on Digital Anarchist. Really happy to be joined for this episode by Josh Kahn. Josh is the general manager of the platform business unit over at ServiceNow. Hey, Josh, welcome.

    John Kahn: Alan, thank you for having me. Really excited to be here today.

    Shimel: We’re excited to have you here, man. Let me just make sure I didn’t mess up anything with the title or the unit and everything, right?

    Kahn: Got it exactly right. That’s right.

    Shimel: Cool, man. Appreciate it. So Josh, look, our audience doesn’t really need an introduction to ServiceNow the company. You know, it’s probably one of the most successful companies over the last two/three years in the tech universe, if you will, right? Phenomenal growth, phenomenal story. But you’re the GM for the platform business unit, and I don’t know if our audience is as familiar with that. I think a lot of people think of ServiceNow with ITSM and those kinds of things. What exactly is the platform unit there?

    Kahn: Yeah, so the platform business unit actually has two parts to it. One is taking requirements from all of our different lines of business and defining shared capabilities in the platform itself that they use to build their products. The other part is defining the things that our customers and partners need to build their own applications on our platform just like we do. And the platform at ServiceNow really is a single platform. It’s one platform, one architecture, one data model. So we make sure that the same capabilities our own businesses have to build on are available to our customers and partners. It’s the job me and my team have to make sure that that’s world class for all of the developers out there in our customers and our partners and in the ecosystem

    Shimel: Sure. Excellent, man. Josh, if you can, share with our audience a little bit, what’s your background

    Kahn: Yeah, so I’ve been in platforms for a long time. I actually graduated college and my first job was at Accenture where they said, “Hey, you’ve got to do some development work before you can get on to being a business analyst.” And I thought, oh man, I can’t wait to be a business analyst. I’ll power through this development stuff, and I just loved it, and I spent the first years of my career programming and programming in C on Windows 3.1 and doing three-tier client server systems. That was a lot of fun. At some point, the internet came along and I realized, wow, that was a much better architecture so found my way to Netscape.

    Shimel: A little bit

    Kahn: Say again.

    Shimel: I said a little bit better.

    Kahn: Yeah. So I found my way to Netscape which was the only internet company at the time and ended up there working on the Netscape 1 platform in a product management role and just http: my career continued to focus on development environments, platforms, and helping people bring solutions to market. Fortunately, I’ve been at ServiceNow for about four years and am continuing to really focus on how do we build a platform that lets our customers unleash the innovation in their organizations and create the kinds of applications that we create ourselves today? We want to bring that to our customers. That’s a really fun job to have.

    Shimel: Excellent. You know, it’s funny. About two weeks ago I interviewed Tom Jermoluk. He was at Netscape obviously with Jim Clark, and he went off with Jim on a bunch of other adventures. They’re still adventuring, right? Tom is now at Beyond Identity or something like that. But yeah, we were talking about – I mean those Netscape days, you’re of an age, I was an OS/2 guy rather than Windows 3.1, truth be told. But you know, you’re at an age where Netscape, people forget I mean that was the opening of the internet commercially, right, without Netscape and what went on there. It was crazy times. Unbelievable times.

    Kahn: I mean the thing that I was building an application where we designed a billing system for an airline to bill back and forth and exchange services and fees and they just sort of wash out dollars at the end of the month and somebody wrote somebody else a check. You know, one airline painted the other airlines planes and then the other airline de-iced. It was a really complicated data model to build, and we had to roll it out to all these different hubs but we tackled the data model problem. We tackled the logic problem. The thing that we couldn’t get around was the messaging infrastructure. That’s the thing that the internet made so easy. I mean among many things, I think it’s one of the reasons that it’s unlocked so much potential is it’s so easy to get a message from point to point for an application.

    Shimel: Absolutely.

    Kahn: It’s really, really changed the –

    Shimel: Yeah, no, it was revolutionary. But you know, you bring up a good example and that is kind of what development was like back then versus what development can be like today. That kind of brings me up to App Engine and what I wanted to speak to you a little bit today, right, where, look, man, it’s – thank God you don’t have to do what you were doing in 1996/97/98 to develop an application today, right? We do have the internet. It does make a lot of things easier.

    But we also live in a time of low-code no-code revolution where you don’t have to be a C-plus developer anymore to put together an application rather quickly. Rapid application development, right? And so I think a lot of people who are familiar with ServiceNow, Josh, they may not be familiar with App Engine and what it brings. So talk to us a little bit about – if you don’t mind, talk to us a little bit about App Engine.

    Kahn: I’d love to, and I think you’re absolutely right. We’re well-known for our IT transformation products, customer workflows, employee workflows, less known for App Engine. So we focused App Engine on providing an application platform that lets people build applications faster than they can on any other platform. A lot of the first questions I get from customers is, “Hey, I have a number of application platforms and I can build – yeah, I want to go faster but what kinds of applications is your platform really best for?”

    And one of the things that we’ve really done, in addition to making it possible to build low-code and build fast, is focus on digital workflows. So digital workflows are ways to drive business process across the organization. A lot of organizations were building those pre-COVID because they had digital transformation initiatives, but the COVID pandemic put the speed and the need of digitizing business process to the forefront of every organization, every government. It’s really just been a catalyst for building applications that drive business process, run across a lot of different systems, and create those sort of digital outcomes.

    Shimel: Great. You’re preaching to the choir here, and we see it every day. Six years’ worth of digital transformation in about four months. That being said, digital transformation is way big, right? I probably went out of the screen on that. I apologize. It’s very big. But low-code no-code allows us to almost take it in bite-sized chunks. It allows us to get our hands around it without the huge development teams and all the languages and all that and really – especially like now in COVID, right, I need an application that does this now, right? We just sent everyone home remote. I need to be able to do this now. And so things like App Engine enable that sort of thing. Do you have any maybe examples you could share with us?

    Kahn: Absolutely. Yeah. I think you’re absolutely right. And we see a world where, look, people who write software and people who code are still going to be incredibly important, right?

    Shimel: No doubt.

    Kahn: The issue is demand. There’s just too many applications to build so we’ve got to help people who don’t know how to code but do know business process to create those applications. That’s what we really tried to do with our low-code platform. And I’ll give you some examples, and a lot of the kinds of applications that people build in a no-code way tend to be the simpler variety of applications. So a few that we’ve worked with customers on. One they call Opendoor. So this allows all of their employees to submit ideas or concerns to the executive team. It was an idea at this organization that started when it was a very small company.

    As the company has grown and grown, it’s no longer feasible for people to walk into the CEO’s office and he was getting 60,000 e-mails a year with ideas for how to do things better or how to mitigate risk. And so they had someone build an application using low-code technology called Opendoor, and any employee can go on a mobile device, submit an idea or a concern and it gets routed to the right executive team in the corporation at the executive level to address so it doesn’t all go to the CEO. If it’s obviously an issue that should be thought of in the finance department, it goes straight to the CFO. If it’s something that should be thought of in the human resources department, it goes straight to the talent officer. But it’s a way that employees are able to get those requests, visibility to the executive team. It was built without developers writing code. It was simply a no-code application process.

    Shimel: Excellent.

    Kahn: You know, I think there’s also an interesting dynamic, too, where we see an opportunity for people who write code to support those – we call those citizen developers. A lot of people use that term citizen developer. So what we think of as a citizen developer is someone who is technical but doesn’t typically write code. So I’ll give you an example. One individual was the person in her department that they would always go to and say, “Hey, we’re going to evaluate a SAS application for project management. Can you go look at these three apps and tell us which one you think is best?” So she really knew technology. She could log in, find her way around, configure things but wasn’t going to go write code to build an application herself.

    What we’ve seen with the citizen developers is they can get pretty far into building an application, but oftentimes they hit a cliff where they need help from somebody who can really write code, whether it’s an integration with a system of record or some kind of complex business logic that’s just a little bit beyond the capabilities of the no-code tooling that they’re using. That’s where we think it’s really important to bring these citizen developers and the developers who write code together on a single platform so that they can support each other and we can get scale from the citizen developers but also have the pro code developers do the tough stuff that really empowers and enables the citizen developers.

    Shimel: You know, Josh, that is so dead on to part of what DevOps is about, right, which is all of us working together in that thing. I wanted to let you finish your thought, but a couple of comments on it is number one, when we look at the full spectrum of the kind of applications modern enterprises, modern organizations need to function, yeah, there are some things that are really hard. They need applications that are really hard to build, have very, very complex workflows and very complex needs or requirements. You really do need to be a high-level developer, let’s call it, a really high level experienced developer to pull that off.

    But I would venture to say that that’s probably 20 percent or less of the kind of apps – when you look at the full spectrum of apps that people use, it’s probably 20 percent or less. I think the majority of the apps are rather mundane, right? They don’t need the rocket scientist to develop. If you just give someone some good building block tools, they could put together 90 percent of the functionality they need, 95 percent of the functionality that app needs to be functional and effective.

    And I think, you know, we said it before, there’s something like 40 million, 42 million developers in the world was the last number I saw, growing 20 percent a year. Would be the fastest growing country on Earth. It’s still not enough. As you said, there’s still not enough developers. So part of what we have to do in DevOps, part of what we do in digital transformation is say, “Hey, if we don’t need one of those 42 million on this but we have someone here doing it, let someone here do it.” We don’t need that pro developer, if we can call it that, to do everything every time. And so the citizen developer as the term is coined, right, becomes more and more important to do more and more of these 80 percent or so apps that don’t require it, right, that don’t require that pro guy or pro gal.

    And so the real question for organizations, and I’m sure this is something you deal with, is how do you empower those people? With an App Engine maybe. But sometimes – Josh, again I’d like to hear your voice – it’s not just the tool. It’s making the CIO, the IT department aware that, hey, let’s not just dump everything on that developer’s desk because he is dealing with security and DevOps and testing and deployment. He’s got enough on his plate. Are there things we can take off the plate for the citizen developer and get it done quicker, cheaper, and just as functional?

    Kahn: Yep, absolutely. So it’s really interesting you say that because we see a pretty common journey with a lot of our customers that have great success with App Engine and it tends to start with the team building a business-critical application of some sort. So I’ll give you an example. Academy Mortgages is one of our customers, and I talked for a bit with the CIO about their journey, and I’ll describe it in terms of what Academy Mortgage did, but this is a very common journey that plays out in lots of our customers.

    So Felix was describing first they had a couple of business-critical applications they built out on the platform. So Academy Mortgage does loan origination. Then a lot of times they will package them up and sell them to investors. So there’s a process when you sell them where there’s a set of stipulations that have to be attested to as a part of that process. So they had a hundred people that manage that stipulation process.

    So they built a digital workflow on our platform with App Engine, and they were able to do that process with half the number of people. So they reduced from 100 people to 50 people to process even more loans than they had in the past. You say, well, hey, where did those 50 people go? And I asked Felix that question. He’s like, “Hey, these are people that know the mortgage industry. They’re incredibly knowledgeable. They’re great employees. We redirected them to other work.”

    So this is a case where they took a business-critical application, had a huge cost savings and increase in revenue generation for the organization through the combination of saving those people and redirecting. But that was only step one. You know, the next thing is they built a small center of excellence. So they put, not huge, three people in a team that were like the experts on building App Engine applications. That team was able to build over 50 applications for 27 different departments at their organization. So now they’ve gone from a couple of big wins – I mentioned one of them, but they had a couple of big wins – to a small center of excellence team and then they move on to phase three.

    Once they’ve had that broad sort of impact with the 50 applications, they start empowering the rest of the organization to build the simple ones, right? So Felix calls it power to the people. He wants to let the citizen developers do the really simple stuff and his CEO team is gonna continue to do the high impact, high complexity, real business value-driving applications. So the vision that you laid out, Alan, is exactly what I’m seeing our customers doing is combining both professional developers for the really complex stuff and citizen developers for the simpler applications

    Shimel: I mean it’s the right person for the right job using the right tool, quite frankly. So you know, Josh, I, like the rest of the world, hope and pray that this COVID thing doesn’t stick with us forever and we come out the other side somehow into what the new normal is. In this new normal, what role – I mean do we go back – we can’t go back to the way it was before, but what role does low-code no-code play in this whole thing going in this new normal that emerges

    Kahn: Yeah, I mean it’s incredible the amount of processes that are being re-engineered across every industry. Anything that depended on contact, human contact, paper changing hands, two people being in the same place is now being re-engineered to become contactless processes. And so for any organization will have hundreds or thousands of those processes, and to think that you’re going to need a skilled developer to write code to reengineer each one of those processes is – you know, you’re going to put the timeline out too far for your organization to be successful. You’ll put people’s lives at risk. You’ll put your organization at risk.

    And so the pace of digitization is just going through the roof. The only way to really keep pace with that digitalization is to empower citizen developers. So what we’ve seen in our customers is a real demand to empower their citizen developers, their business analysts to reengineer business process. They know that process well. If they can be armed with tools that allow them to model it, define it, and deploy it, then the organization can create transformation at scale. That is what everyone is looking for in this post-COVID era.

    Shimel: Absolutely.

    Kahn: We’re dealing with it today, but even as we move out those processes will continue to be reengineered and change.

    Shimel: Agreed. I think, look, the whole thing around business process automation, robotic process automation, RPA, another popular topic and I think the other thing is we’re interviewing a analyst a couple weeks ago and they said something like we’ve done six months or six years of digital transformation in a couple of months.

    The interesting thing about that is it’s almost like putting money in the bank. So that money’s there now. So when and if this COVID enters, you don’t start with zero in the bank. You start with what you’ve already deposited, right, and then we build on that. I think that’s an important thing for people to remember in that all of these investments we’re making now and empowering our citizen developers with tools like App Engine. They’re now short term or diminishing assets. These are long-term investments we’re making that will serve us well going out beyond the immediate crises or whatever you want to call it.

    And it’ll be interesting because I feel like, you know, so like you, we both came of an age, right, when the internet came onboard and we had this concept of internet time, right, this kind of crunch time. In internet time, it goes three times faster than the real world. I think we have now introduced like COVID time, and I don’t mean to be – look, a lot of people are suffering. A lot of people are dying. But we have compressed timeframes in terms of how fast we’re developing apps, in terms of how fast we are bringing onboard these things. I don’t think that goes away. You can’t put that genie back in the bottle.

    Kahn: You can’t. You know, I think there’s a perfect example of that that we saw with the City of Los Angeles. So the mayor’s office wanted – this is early on in the pandemic. They wanted to roll out COVID testing for all of the citizens of Los Angeles, and they called ServiceNow, and we brought in one of our partners on a Saturday morning. The mayor was saying I have a press release on Sunday night. I need to roll out the testing application so that when we tell people there’s testing, we can tell them where to go to sign up. And so this partner, Cask was our partner that did this, they assigned six developers who worked through the night, did a demo for the mayor’s office on Sunday morning, and by Sunday evening they had this application up and running for 4 million citizens of Los Angeles, eventually expanded to the county so you get to 16 million people.

    But it’s interesting because it wasn’t a registration form. It was a really powerful logistics app. Behind the scenes, they had to have agents who could route the request to the right site to get tested. They had different sites and each site had two-hour windows where they didn’t want to put too many people in a window because then you have –

    Shimel: Unbelievable.

    Kahn: – too close together. So you want to talk COVID time, I mean within 48 hours they were able to build an application that handled a complex logistical challenge and make it available for 4 million people. You know what I mean? Even on the internet.

    Shimel: Fantastic.

    Kahn: – that would be inconceivable.

    Shimel: Crazy. I don’t want to get into politics, but why couldn’t we do that nationally, man? You know, if it worked for L.A. for a couple of million? But let’s not go there. Josh, we’re about out of time. I want to thank you for coming on and sharing a little bit with us, talking, learning. You know what we didn’t mention? For people who want to find out more about App Engine, where can they go.

    Kahn: Yeah, look, best place to go is ServiceNow.com. You’ll drill into the platform area, learn about App Engine. If you’re interested, you get your own developer instance and you can be up and running building applications in no time.

    Shimel: Fantastic, man. Hey, thanks for joining us. Josh Kahn, VP of the Platform Business Unit at ServiceNow, talking to us about App Engine, empowering citizen developers around the world. This is Alan Shimel for TechStrong TV. We’ll be right back with our next guest.

  • TechStrong TV: strongDM Helps Kustomer Go Remote

    TechStrong TV: strongDM Helps Kustomer Go Remote

    For a procurement process to be effective, the relationship between the customer and the product team is almost as important as the functionality and features of the product itself.

    During this interview for TechStrong TV, strongDM CEO Elizabeth Zalman and Steve Flinchbaugh, senior SRE at Kustomer (a customer support CRM platform for managing high support volume effortlessly), talk to us about the strong bond between the Kustomer team and the support team at strongDM.

    Steve explains how Kustomer uses strongDM to empower its remote teams, how it fits into their development workflow and how strongDM has made his and his team’s lives easier.

    strongDM allows remote teams to easily manage access to databases, servers, Kubernetes clusters and web apps.

    Check out the interview below and follow along with the transcript to find out more.

    Transcript

    Alan Shimel: Hey, everyone, thanks for joining us for this next session here on TechStrong TV. This is gonna be a really good session; it’s something we haven’t done before. I have two guests, which we’ve done before, but we’re really gonna zero, we’re gonna take two different companies and see how they interact and how that helps, especially given everything that we have going on around us.

    Let me introduce my two guests to you first. First of all, we have Elizabeth Zalman. Elizabeth is the CEO of strongDM. We’ve done—I think we’ve done at least a podcast and so forth with strongDM before. Liz—hey, welcome, thanks to TechStrong TV.

    Elizabeth Zalman: Thanks, Alan. Nice to be here.

    Shimel: Thanks for joining us. Okay, and then joining Liz and I is Steve Flinchbaugh. Steve is with a company called Kustomer, and that’s spelled with a K, and he’s gonna tell us about it, as well as his position and background there.

    Steve, why don’t we start off with you, okay? Kustomer with a K—what do you guys do, and what do you specifically do at Kustomer?

    Steve Flinchbaugh: Sure, Alan. Thank you for having me. So, I’m a senior SRE at Kustomer, and what Kustomer is, is a CRM for customer support. And we really are built off of our platform. There’s a lot of intelligent automation that allows our customer service teams, our customers, to give the best possible customer experience they can and accomplish their customer service goals through, ideally, less staff and less effort using our platform.

    My goal as the senior SRE is to ensure the reliability of our platform, the kind of implicit trust that everyone expects, and to make the job for our developers as easy and seamless as possible.

    Shimel: Cool. So, a real, live SRE right here on our show—very cool. You know, there’s a lot—I don’t know if you guys have seen, there’s been a lot of articles written lately in the press around, you know, are we overblowing the whole SRE thing, right? And is it real, how real, and where does it fit in and all of these other things.

    But anyway, Liz, we gave Steve a good chance to tell us about Kustomer with a K. Let’s give you your chance—tell us about, remind our audience about strongDM.

    Zalman: Yes. Steve is one of my favorites, by the way—so is Kustomer with a K. They’re one of the most forward thinking customers with a C that we have. [Laughter]

    Shimel: Okay. Very good play on C/K, there. [Laughter]

    Zalman: strong is a—it’s a proxy, it’s a control plane, it’s insert whatever word you want there and it lets you manage and audit access to servers, to databases, to Kubernetes clusters, to whatever infrastructure you’re running that is firewalled. So, typically, that access is managed by hand, or keys are sitting in a box or a vault somewhere, and we let you collapse all of that down into a single control plane for both the management and auditing of that access

    Shimel: Yep. And I just—look, I feel like we have to mention that, you know, given the whole COVID situation and working from remote, you know, strongDM has been a real godsend to a lot of companies who had to kind of flip a switch and empower remote people to have access and stuff that, you know, from a different place on different machines, devices than they had before.

    So, though strongDM had a great case before COVID, right, a great use case, post-COVID, Liz, how many—you know, I’m not asking for the amount of customers, but I mean you’ve seen a lot, I imagine you’ve seen a lot of activity from customers who are, have switched to remote and need help with that.

    Zalman: Yeah, certainly, it was challenging before. I think most companies today have remote workers, anyways, or multiple office locations. With the lockdown with COVID, I think what ended up happening is, for companies who rely on the corporate network itself as the perimeter within the building, that perimeter is now gone, and so, what do you do? If you’re using something that’s IP-based, all of a sudden, your IP surface area went from, like, two to 5,000 if you’re an enterprise.

    So, we certainly saw a doubling down of existing customers and an increase in interest in the product. I might ask Steve, like, could you have imagined what—I mean, what was it, like, you guys have an office in New York…do you guys have remote workers? I don’t—yeah.

    Flinchbaugh: Yeah, so, we have an office in New York and we recently—that’s our headquarters—and we recently acquired some office space down in Durham, North Carolina. That’s kind of our first official outpost, and that was kind of our introduction to people outside of New York, and it was—this was after we had adopted strongDM, and I have to say, it was entirely seamless. And ever since the pandemic began, I know it’s good because I haven’t thought about it that much. strongDM is—

    Shimel: That is always the sign. You know what—sorry—I was in security for 20 years. They didn’t call it cyber then, it was InfoSec, but we always used to say, “If they didn’t think about it and it didn’t hit anyone’s radar screen that they—you know, that was a good thing.” When people hear about security stuff, it’s because something bad happened.

    But I wanna make a point here, though, and that is—Steve, it’s my understanding you guys didn’t, you’re not a Johnny come lately to strongDM. You guys were using this well before COVID and the present situation. Talk to us—let’s go back in time to then, it was about a year and a half ago, right?

    Flinchbaugh: Yeah. And actually, if you don’t mind, I’d like to go even further back in time, about four years ago—

    Shimel: Be my guest.

    Flinchbaugh: – when I joined Kustomer.

    Shimel: Okay.

    Zalman: You joined it four years ago?

    Flinchbaugh: Four years in September.

    Zalman: Wow! How big were you then?

    Flinchbaugh: I was, I think, employee number 16. We were still in stealth mode, we weren’t charging our customers yet, and Steve comes into Kustomer bright-eyed and bushy-tailed. But at this time, we were running agents on our servers to provide SSH access to our engineers, and I was charged by the CTO to stand up a VPN, which I had never done. And this came in the form of open VPN, and I had to manage the certificates and the log-in and the users and every employee that joined the company, I had to on board them and configure a profile.

    And then, fast forward to, I think it was about a year ago, where the CTO again came to us and said, “Hey, there’s a really cool company that I think we should take a look at. We have a mutual investor, and they have a lot of cool features that we haven’t had for the past three years.” So, we had a couple really cool meetings with Liz and her team. I could immediately tell that we were working with a team that knew what they were talking about, they were technical, they were fun to work with and they kind of just got what we needed out of the tool.

    And now, today, there are so many things that are taken off of my plate in addition to more features for security and making developers’ lives easier that strongDM now gives us.

    Shimel: Very cool, very cool. Alright, now, we can fast forward to Durham and how strongDM helped with the rollout there of a new—I don’t wanna call it a remote office, but I think you used the term outpost?

    Flinchbaugh: Yeah, so, it’s definitely, like, our—we call it HQ2, I believe, but we’ve got a fully functioning, we call it squad, so we kinda have self-sufficient and cross-functional teams out there, and everywhere across the country, but Durham was our first remote squad, if you will.

    And the neat thing about strongDM is, I don’t necessarily have to say when a new user joins, when someone joins the company, there’s not necessarily a task in my to-do list. It’s so self-service with our Okta configuration, a user can go in and say, “Hey, I wanna start using strongDM, I’ve heard all about it. How do I get access to our data storage and our private resources?” And at that point, I get an e-mail, I can add them to a roll, to a group, and they’re happily on their way. So, I don’t need to configure a profile, I don’t need to do anything special for these individuals. So, from my perspective, it’s incredibly easy to onboard new and remote folks.

    Shimel: That sounds like too good to be true. Is it true, Steve?

    Flinchbaugh: [Laughter] It does feel too good to be true sometimes.

    Shimel: Okay, and you’re saying you guys use Okta for a lot of your IAM and stuff like that?

    Flinchbaugh: Yeah, part of our maturation as a company, you know, back in the day, we had, of course, authentication and identity all over the place and now it’s much more unified. All of our tools that can integrate with Okta, it just makes it that much easier. And again, it’s just things that I don’t have to think about as often

    Shimel: So, Liz, let me throw something back at you. Again, the whole IAM space is something I’m somewhat familiar with—how important is it for strongDM to integrate with an Okta or ADs or other kinda directories and stuff like that

    Zalman: It’s critical. It’s one of the core principles of the business. I think, you know, I’m guessing, Steve, the customer made the decision to buy Okta well before strongDM.

    Flinchbaugh: I think it might have actually been around the same time—but yes, I think Okta was shortly before strongDM

    Zalman: Yeah, so, you have to start with the question of, “What is my identity store? What controls identity, and then how do I integrate that identity store with everything else?” So, strong has integrations with all of the SSOs—because I don’t want to reinvent the wheel. Steve’s already invested a bunch of money in Okta. He’s already reinvested a whole bunch of money in whatever he’s using for automation, Terraform or otherwise or an Amazon tool. Most companies have already invested a whole bunch of money in Splunk or Sumo Logic or QRadar, whatever they’re using for logging, I don’t need to reinvent the wheel with logging and alerting, I just need to make sure there’s a connector between the two.

    And so, honoring what people have already invested a whole bunch of money in and sort of bet the farm on already is critical.

    Shimel: Yeah, you know, Steve, you’re an SRE, so you live this every day. But it’s something—I’m an observer now. My days of those battles are over, right? But as an observer, it’s still, I shake my head sometimes, because so many companies like Kustomer, right, have kinda made their bets on the tools that they use, right? They’ve put together an identity in access management, but it’s not log management, cloud platforms—you know, your whole tool set. But yet, there are still plenty of companies who are trying to say, “No, no—you should use us for everything, right? We can sort of do what strongDM does.” You know, and you know the old saying with this, right? They try to give you 80% of the functionality for 40% of the price, and if that’s good enough for you, it’s good enough, right?

    And I was never a fan of that model—Liz, you’re laughing; what do you think? I mean, we see this still, and I don’t—you know, I assume some companies go for that, you know? But I can’t imagine it really works out. You just don’t get the function—we live in a great time where there’s so much available to us to try to make lives easier for people like Steve, for the SREs of the world and the Ops folks. You know, why would you try to just shove everything into one vendor and do, and put up with less than.

    Steve, what do you think?

    Flinchbaugh: So, it’s definitely, when you’re a smaller company, it’s, of course, much easier to adopt and drop and try new technologies and vendors. But, of course, as we’ve grown, that cost becomes higher and higher. So, when I first joined Kustomer, we could try new things whenever we wanted, but I can already see in the couple years that I’ve been with the company that implementing something like strongDM would be almost exponentionally more effort now, because I’d have to go through different departments and accounting and finance and communicate with the team, and developers just wanna know, “How do I do my job? Like, just tell me what to do.”

    Shimel: Mm-hmm.

    Flinchbaugh: And more than the functionality and the features of the product, I truly feel like we have a relationship with the strongDM team, and that’s almost just as important to us. We know that they are responsive, that they’re gonna listen to us, that they’re gonna help us out—and they have, you know, literally weekly.

    And that is so important to us as customers that, if someone came along and said, “Hey, we’ll charge you 50% of the price that strongDM does,” I don’t think I would be too tempted to consider that right away.

    Shimel: Yeah. But I think that goes to the model today, right? It’s part of this whole cloud native, open source, freemium core, open core, whatever you wanna call it, which is—the key is not to go hire some enterprise sales guy who comes by and wines and dines people. It’s about—hey, here’s the product. Let me get the product in your hands, right? Let me deliver delight, as they say, right, with that product, and the bonds that are formed from that type of relationship, right, it’s—if you wanna call it DevRel, you know, a lot of people call it developer relations and community relations—those sort of bonds are much stronger than the old sort of sales game that I grew up in, for instance.

    Elizabeth, with what Steve is saying, is that sorta news to you that it’s much easier to get in and kinda grow with these customers than it is to kinda come in when they’ve reached a certain scale and it’s a lot harder to get adoptions done

    Zalman: Certainly, it’s easier when a company is young—50, 100, 150, even 200—to get implemented. I think to Steve’s point, eventually,  you have a procurement department, and then you have to go through the traditional, like, “Oh, that’s the price? Okay, we’re gonna knock it down by 50% now,” right, and that’s just how the operate.

    Shimel: Right, yeah. Mm-hmm

    Zalman: And certainly, there are much longer sales cycles in the enterprise side, with a company of Kustomer’s size. Even the size today, you know, two week POC and you can play with it enough, to your point, Alan, where you decide if it’s right for you, if it fits enough of your requirements.

    With larger enterprises, it’s—and again, to Steve’s point, it’s not…you do have to go team by team, right, at a larger enterprise and say, “Okay, we’re gonna do the finance team now, and then we’re gonna do the engineering team, and then we’re gonna do the DevOps team.” And it’s sort of rinse and repeat and you get the hang of it after a while, but it’s bite sized chunks, always, whether the bite sized chunk is the entire company at once, or work group by work group.

    Shimel: Yeah. And I think that very much mimics the whole DevOps adoption pattern as well, right? You don’t go in and just turn on a large enterprise to DevOps, you do it bubble by bubble, team by team, right? And quite frankly, the other thing is, though, is I will tell you that sometimes that procurement process and all the b.s. that goes with it is why developers or DevOps people will whip out a credit card and just do it, right? And you get the whole shadow IT thing or whatever you wanna call it, but it’s like, who wants to—you know, I gotta sit and explain to this person why strongDM makes my life easier? You know, I mean, it’s—especially someone who has no technical background, it’s like, you know, where do I begin?

    But, you know, nevertheless, you guys got a year and a half of history here. Steve, where do you see the first squad’s in Durham, I assume that means you guys are planning second and third squads and maybe outside the U.S. and what have you—is strongDM tied, I imagine, tied into that as the roll out moves along here

    Flinchbaugh: Yeah, of course. It’s become the way that we access our resources across all of engineering. And we actually acquired a Spanish company, Reply.AI, a month back.

    Shimel: Oh, very cool.

    Flinchbaugh: Yeah, so—

    Zalman: Congratulations

    Flinchbaugh: Thank you. So, I’ve been having some conversations with the Reply engineers, and I can already tell that they’re impressed with how we use strongDM and how it kind of fits into our development workflow. And so, that would be interesting, because they have infrastructure of their own, infrastructure that we haven’t used before, so it would be a cool opportunity to say, “How does this plug into strongDM?” And I really have no concerns that that would be the case, but it’s gonna be a fun task to get all of that in the same kind of workflow that all of our Kustomer engineers use today.

    Shimel: Excellent. When you say Spanish, like in Spain—they’re based in Spain?

    Flinchbaugh: Yeah, they’re based in Madrid. I believe they’re a fully remote company, though, throughout Spain. So, they kinda have that remote culture, already, so it’s perfect for us right now, and of course, their AI expertise is nice to have, as well.

    Shimel: Absolutely.

    Zalman: Steve, where is their infrastructure? Like, is it in the U.S. in AWS or is it in something sitting in Europe?

    Flinchbaugh: I can’t say too definitively, but I do know that they have a mix of AWS and Heroku right now.

    Zalman: Interesting.

    Shimel: Really?

    Zalman: So, you’ve got a distributed team in Europe and now, effectively, multiple data centers if you’re talking AWS and Heroku that aren’t merged with Kustomer as well—

    Flinchbaugh: Yes, indeed.

    Zalman: Yeah, I see.

    Flinchbaugh: That’s right.

    Shimel: Sounds like an opportunity, Liz. [Laughter] Liz, let me ask you a question—how many, I mean, what I’ve always loved about the Internet is, it knows no borders, frankly, right? I remember the first time I put up websites and I started seeing hits come in from around the world. This is, like, 1996, and I was like, “Wow, we’re global!” Not at Media—you know, not this company, obviously.

    But what is the customer mix at strongDM? Is it international or is it mostly U.S., or—if you know?

    Zalman: Yeah, it’s heavily international. We’ve got, actually, a big contingent in Australia, we have Europe, we have Asia. Our large enterprise customers all have offices in India, whether they’re using contractors as a work force or an actual office there, you’ve got the U.S., you’ve got Canada, you’ve got South America.

    Oh, and you know what? Actually, I was just gonna say we’re not in Africa—we’re totally in Africa, so it’s everywhere. And then even, we’re not in the Middle East, I don’t think. But even more interesting, I think, than where the people are, it’s where the data centers are. You’ve got this crazy Cartesian product of people trying to connect to stuff, and most companies—we’re in China, I mean, we’ve got people on, we have workers on factory floors in China who need to SSH into infrastructure.

    Shimel: Very cool.

    Zalman: And so, it’s crazy to think about all of the networking going on, the latency, and how to make that connect, and it’s just personally fascinating to hear the new use cases that come up. I was like, when I heard factory, I was like, “Wow!” And then I started thinking of, like, Tesla. I was like, “I wanna be on the factory of Tesla,” but no.

    Shimel: Yeah. That could be in China, too. You know, it’s funny you bring it up, I actually interviewed a CEO of a company maybe last week who, they are instrumenting manufacturing factories, because a lot of that machinery was not connected that you can, you know, you had visibility, and they actually put things on to machinery that allow you to instrument them and monitor and stuff. There’s amazing things going on. And by the way, each one of those add-ons to the manufacturing machines has to have a certificate, an identity—you know, there’s a whole piece of this, too, and I just think it continues to go on.

    Steve, we don’t have a lot of time left. How has the COVID thing kinda affected you guys?

    Flinchbaugh: So, personally, I feel incredibly fortunate to say that my work has changed almost not at all. I think my position and a lot of our department is very remote friendly, and even though we weren’t set up, really at all, for remote before the pandemic, the transition has been relatively seamless—obviously, from a strongDM perspective, it is seamless.

    But overall as a company, I think—of course, there’s a ton of adjustments with different departments and some are having it easier than others. But I actually think engineering is, our efficiency and output and how we’ve put out features since the beginning of this has actually increased just a little bit.

    Shimel: That’s great to hear, man. Really good. Guys, we’re about out of time. I want to thank both of you—both of you coming at us from New York, today, I should mention, so thanks for joining us. Liz, any last thoughts, comments you want to add?

    Zalman: Nope, I don’t think so. I wanted to say thanks to Steve, and I appreciate the comment on relationship. It’s so important, as I say—you know, at strongDM, everybody touches the customer equally. It doesn’t matter if you’re in account management or support or engineering that I joke that if we were to ever have commissions at the company, which we don’t, I would give support the commissions, because they’re that important.

    Flinchbaugh: As a support company, somewhat as an employee there, I can very much appreciate your support team as well, Liz, and it’s not an exaggeration to say it’s the best support that I’ve received from any vendor, ever.

    Shimel: Very cool, very cool. That’s a good way to end it. Alright, Elizabeth Zalman, CEO, strongDM; Steve Flinchbaugh, SRE at Kustomer with a K—thanks for joining us on TechStrong TV. This is Alan Shimel. We’ll be right back with our next guest.

  • MediaOps Video Productions Wins 2020 dotCOMM Awards

    MediaOps Video Productions Wins 2020 dotCOMM Awards

    We are pleased to announce that MediaOps is the recipient of not one, not two, but three 2020 dotCOMM Awards for excellence, in multiple video categories: TechStrong TV in the category of video series, DevOps Unbound for video podcast and CISO Talk in video news and information.

    The dotCOMM Awards are an international competition honoring excellence in web creativity and digital communication. They are administered and judged by the Association of Marketing and Communication Professionals (AMCP), an international organization that oversees awards and recognition programs and honors outstanding achievement and service to the profession. AMCP judges are industry professionals who look for companies and individuals whose talent exceeds a high standard of excellence and whose work serves as a benchmark for the industry.

    At MediaOps we are committed to creating and producing high-quality content to tell your story in the most powerful way, pushing the bounds of broadcast technology and creativity—and having fun while doing it.

    We are proud of everything we have accomplished so far, and these awards reflect the hard work and dedication of our talented and skilled team members, who strive for perfection to exceed the expectations of our audience.

    MediaOps Productions Take Top Awards

    Platinum Award for Video Series:

    TechStrong TV, a streamed broadcast featuring fresh video news and information three days a week and replays of prior shows two days a week, on the Digital Anarchist network. Covering DevOps, cybersecurity, cloud native and digital transformation, TechStrong TV keeps its viewers up to date on the latest news and features  interviews with thought leaders and education in the hottest IT areas.

    Gold Award for Video News and Information:

    CISO Talks, a bi-weekly series that explores the latest in cyberspace, featuring industry experts and newsmakers in the field. Hosted by MediaOps editor in chief Alan Shimel and Unisys CISO Matthew Newfield.

    Gold Award for Video Podcast:

    DevOps Unbound, a bi-weekly/monthly roundtable sponsored by Tricentis, which provides a deep dive into DevOps, with an emphasis on automation, continuous delivery, accelerating transformation, testing and quality.

    The MediaOps team would like to thank the dotCOMM Awards for recognizing the content we publish and the hard work that goes into it. Most of all, we would like to thank you, our audience, for all the support you have given us throughout the years.

    These three series, along with more than 1,500 other videos, podcasts and webinars, are available on MediaOps’ Digital Anarchist video platform and streamed via TechStrong TV.

  • TechStrong TV: How strongDM Helps mParticle in Secure Remote Access

    TechStrong TV: How strongDM Helps mParticle in Secure Remote Access

    In this interview for TechStrong TV, I am joined by strongDM CEO Elizabeth Zalman and mParticle CISO Dave Anderson. Dave shares with us how mParticle uses strongDM proxy services to rapidly enable the expanding mParticle team to access infrastructure, assets and applications necessary for mParticle to fulfill its mission to its customers.

    With the rapid growth of mParticle, the company needed a solution that would allow it to onboard its new employees and locations seamlessly. strongDM gives mParticle this capability. Have a watch of the video and follow along with the transcript to find out more.

     

    Transcript

    Alan Shimel: Hey, everyone—back here for another segment on TechStrong TV. I am joined once again by my friend Liz Zalman at strongDM. Hey, Liz, how are you?

    Elizabeth Zalman: Hi, Alan. I’m well, thank you.

    Shimel: Good to have you back on. And joining Liz and I today, another guest, is Dave Anderson. Dave is the CISO at mParticle. Hey, Dave—welcome to TechStrong TV.

    Dave Anderson: How’s it going?

    Shimel: Going great. Not as great as you are. Dave’s coming at us from a sailboat today and we’re all stuck in our homes and offices, but hey, the life of a CISO—and you guys complain.

    Anderson: [Laughter]

    Shimel: Anyway. You know what, we—yeah, I don’t know, it’s hard to make that less glamorous, Dave, but we’ll give you the pass. Liz, for those who haven’t seen some of our previous interviews with you and the strongDM team and some of the customers, why don’t we start off, give our audience a quick background, who’s strongDM, what you guys do?

    Zalman: Sure. Strong is a proxy and it lets people manage and audit access to any firewalled infrastructure—servers, databases, Kubernetes clusters, RDP, firewalled web apps, HTTP endpoints. So, essentially, instead of managing keys and creds, you give people access to strong, and then it talks to the target systems on your behalf, so you get access control and then auditing through the proxy itself.

    Shimel: Everything you expect from your proxy—great.

    Zalman: [Laughter]

    Shimel: And it’s sort of proxy as a service, if you will, yeah?

    Zalman: Yeah, there’s a portion of it that is hosted, the control plan itself, and then the rest goes through your own hardware.

    Shimel: Got it. And Dave—

    Zalman: Or whatever your virtual hardware is these days.

    Shimel: Well, yeah—no one uses hardware. Through your own infrastructure, how’s that?

    Dave, talk to us about mParticle.

    Anderson: Yeah, so, mParticle is a customer data platform. So, what that means is, our customers are able to use our platform to ingest pretty much anything, any data about their customers, about the activity that’s going on on their websites and mobile apps into the mParticle platform, and then we’re able to give our customers the full control of being able to fan that out to any of our different integration partners. So, there’s that, as well as being able to do things like data quality, match identity resolution, figure out where a particular user is, what sort of ways you want—like, how they’re interacting with their particular application or whatnot.

    To be honest, we have customers, like, in a bunch of different verticals, and they all use the product a little differently, and it’s—we’re continuing to grow and innovate and figure out different ways of kind of helping our customers along with their data journey.

    Shimel: Excellent. And, you know, that kinda mission is just so attuned with what I think companies are looking for today, right, which is—you know, there’s so much data out there. There’s so much—you know, do you want it all, what are you gonna do with it all, what makes sense, what doesn’t make sense? But the idea of being able to access that, analyze it—hopefully, with as much automation as possible—is what it’s all about.

    Of course, it also creates—as a CISO, you know this—it creates tremendous responsibilities and potential pitfalls from a security, data, access, compliance point of view. But it also, you know, to the strongDM mission of proxying through firewall to assets, whether those assets are remote workers who have to access, you know, data in the cloud or on-prem or wherever or just whether they’re remote or not, access incorporate assets, which, in your case are, in some cases, I’m gonna assume, a lot of PII kind of data.

    data
    Dave Anderson, mParticle

    Anderson: Exactly.

    Shimel: This is a potential security nightmare. This is what keeps CISOs up at night on their boats. So, talk to us, Dave, what is—you know, how does strongDM help you sleep better?

    Anderson: So, naturally, we’re a data collection—data collection and distribution company. So, we have a lot of data, a lot of data split up into a lot of different databases, and we have to have very tight access controls for those databases. So, one of the things that strongDM gives us the capability of doing for—when any sort of support people or operations people need access to a particular database or data set within the kinda mParticle back-end, we’re able to utilize strongDM to give us the ability to have secure access to that, that is able to be tied back to the individual who’s doing the work, everything is audited, everything’s logged, we’re able to generate reports for compliance.

    So, it gives us the capabilities of not having to give our, like a support person, for example, give them a direct access to the database. They have, like, a nice tool they can use, everything is integrated nicely on the desktop, and everything is integrated well with all of our identity management platforms as well.

    Shimel: Excellent, excellent. So, Dave, I think we—you know, we get what you’re doing there, we get what the potential risk is. And we’ve done a few interviews—in full disclosure, we’ve done a few interviews with some of the strongDM clients in fintech and other verticals. What we haven’t done is kinda peeled back what was—I mean, using a proxy, I think a lot of our audience has probably used a proxy one way or another.

    But I want to peel back now, in the case of mParticle, walk us through how you guys sort of say, “Okay, we’re gonna use strongDM.” How did you set it up? How did you deploy? How do you manage it, right? How does it give you the warm fuzzy feeling you need to know that you can sleep well at night?

    Anderson: Well, to be perfectly transparent, I was—I’m pretty new at mParticle, so, I wasn’t here when—

    Shimel: So, you inherited it?

    Anderson: Yeah, so, I inherited it. But I actually am a pretty early strongDM customer from my last job at Greenhouse Software, and so, I’m very familiar with that aspect of it. We used it for similar purposes back then. Back at Greenhouse, we had a lot of support personnel that were—and kinda data quality engineers that were using the strongDM platform to access our databases within AWS. And similar here, we want to have—we try to keep as much, the access as restricted as possible. We believe in the principle to release privilege, and separation of duties.

    Shimel: Sure.

    Anderson: So, with that, we need to have our networks deeply, deeply isolated. The databases live kinda deep into the network, not even having access to the outside world. And with that, the only way to give somebody in support access to that database traditionally would have been giving them VPN into that environment and then them having to actually install the different tools and having to manage authentication and access control. And even then, what would happen is, we would also lose visibility into what they did on that database. Like, what queries did they run, what data did they see? Because it’s not even necessarily a kinda everyday type of thing for someone to have access to the data itself. We tightly, tightly control who has access to what data, and using a tool like strongDM is pretty much a requirement for that.

    Shimel: Yeah. I mean, look—and I’ll try to put it in layman’s terms for our audience who maybe aren’t as familiar with this stuff. When you’re using a VPN, they call it a tunnel, right, a tunneling tool. Because really, what you’re doing is, you’re punching a tunnel through, whether it’s your firewall in your infrastructure, and it’s an encrypted tunnel at that, right? So, everything that takes place within that tunnel is encrypted.

    And so, when I connected to a database via a VPN, you may see that I did connect—oh, yeah, that’s Alan’s client and he connected to the database. But in terms of what data was in that tunnel and what—you know, you really don’t, you don’t have visibility there, by its very definition, right? On purpose. It’s not a byproduct, that’s how it’s supposed to be. And you don’t—you know, you can…it’s just, that’s how it was designed.

    And so, that doesn’t really play well, you know, in the areas of DLP and you wanna make sure data’s not ________, you know, taken out. It’s a problem. So, now, strongDM helps you solve that, is what you’re telling me, because now we can see, you know, it’s a proxy, but on the backside of the proxy, that goes into the firewall and into the trusted network as we used to call it 100 years ago when I was in security, right? When you go through that into the trusted network, you can still see where Liz went or Alan went or Dave went, because it’s not that tunneled, right? It’s not that encrypted tunnel through there, it’s more of the proxy. I remember when we were NAT-ing firewalls, right, a long time ago, and it was that same thing—at least I could match up this IP to that IP, the behind the firewall versus the public IP, you know, private IP, public IP. And so, you had some of that then.

    Then, on top of it—look, giving people a VPN, with everything going on in COVID and remote workers, you know, and all we’re hitting, and of course they’re not just hitting your database, there’s also SaaS apps that they need to hit and everything. A VPN is—I’m not a big fan of VPNs in today’s world, if you can’t tell, okay? I just—it don’t make sense. I mean, and then, and the whole idea of VPN-ing back into a central kinda office to go back into the cloud also kinda, I mean… You know, a friend of mine, I know a guy named Jay Chaudhry who is, of course, the CEO and Founder of Zscaler—he used to rail from the very time the cloud-first started coming on the scene big, 2006-’07, he was saying back then that VPNs were, you know, the time has come, but here we are, 2020—same thing.

    But, Dave, how easy was it to set up the strongDM proxy, and what kind of visibility is it giving you?

    Anderson: I mean, setting up strongDM is really easy. There’s a couple of pieces of infrastructure that you put into your environment, and that would all depend on how you deploy your infrastructure. So, there’s—I’m trying to remember the exact terminology. Like, a gateway and a—what was that?

    Shimel: Liz, can you help him here?

    Anderson: Yeah.

    Zalman: What?

    Shimel: Can you help him out, here?

    Zalman: I ________. I would never leave my friend hanging—never. [Cross talk]

    Anderson: [Laughter] Yeah, so, you deploy that infrastructure that, basically, that sits in your network and you have, and then it talks back to the strongDM portal and so, the strongDM clients actually know who to talk to, like, what IP addresses and what databases it has access to. You go through the strongDM UI or you can use their API, depending on your preference to set up different databases and set up the credentials in there and all the users and what users have access to what databases and what roles within those databases they have access to. And then there’s a client that runs on the person’s laptop, and that client, they’re like, you’re talking locally to that client and it’s magically on the strongDM back end, like, routing everything around to the right place and makes it extremely streamlined for the end user, because they just have this little control panel down there, like, in the bottom of their screen that lets them connect to the particular database, and it’s really, really ridiculously easy to use.

    Shimel: Very cool. Now, as part of the role in CISO, you’ve always gotta be thinking not if, but when we have an incident, right? I’ve gotta be able to do forensics, I’ve gotta have an audit trail, right, I’ve gotta be able to figure out, what the heck—I have to show people what happened here, did we take reasonable steps, right, and stuff like that.

    What is it, in terms of audit trail and forensics, how does strongDM help you there?

    Anderson: So, it shows us who connected to what resource when, how long they were connected, what they did, what sort of careers they were in, what sort of other kinda SQL comments or whatever the database may be, and be able to produce that in near real-time, as well as have logs to go back to if there was an incident that we would know what data was accessed by a particular individual.

    Shimel: So, that’s kinda the control plane that sits in the cloud, Liz, or that’s local to the client?

    Zalman: The auditing happens through the gateway. So, when the request hits the gateway, it actually deconstructs it in order to provide the audit trail—so, that stays resident in Dave’s network, yeah.

    Shimel: Excellent. So, we don’t have to worry about access to strangers to that.

    Zalman: Yeah, no, it’s his data. We don’t wanna touch it. [Laughter]

    Anderson: Yeah, that’s one of the most attractive things, actually, was the fact that the data stays in our network. strongDM operates the, how things actually get connected, but as far as, like, once you’re in that network, it’s, everything stays within there.

    Zalman: Cool. Alright, sounds great. Dave, one other question. With COVID and everybody working remote, I know—look, I mean, strongDM, from what I’ve seen, has built a…not built, but while there are plenty of people, obviously, suffering as a result of COVID and my heart goes out, I’m sure as you guys, too, to people who have lost loved ones and are sick and have lost jobs and money and all of the bad things that are happening with this. The fact is, you know, with remote workers being more and more common, solutions like a strongDM are thriving, right? Are being rapidly adopted. Not because they’re nice to have, because you gotta have something like that, right? So, I’m wondering, what are you guys seeing at mParticle and a similar kind of thing as you’re going remote?

    Anderson: Yeah. I mean, thankfully, we were really well-equipped for going remote. A lot of the engineering team is distributed to begin with. We had people in Seattle, Florida, Texas, and New York, of course. But we were able to transition to it pretty seamlessly. We just spend a lot more time on Zoom.

    Shimel: Don’t we all?

    Anderson: Yeah. [Laughter] Yes, but having the technology in place for being able to securely connect to remote networks, remote resources is definitely, it’s a requirement nowadays. I mean, especially with—you can’t, you don’t have a perimeter anymore. There isn’t that network, the whole concept of having that network firewall that was sitting there and protecting everything is kinda dead now, especially with, since everybody’s working from home. I mean, and VPNs, as we were talking about before, only give you so much. There’s only so much flexibility you have with how you can protect your network and segment your network to make a VPN be as flexible as a platform like strongDM.

    Shimel: Look, I thought network firewalls were dead in 2007, right? I remember the first time I saw a Jericho—I don’t know if you remember this, Dave, but do you remember the Jericho project? Did you ever hear of that? That, you know, they were the first ones to talk about the de-perimeterization of security and micro-perimeters and personal perimeter and all that stuff. That whole moat and castle setup that the network firewall played in and the VPN was sort of a bastardized child of, you know, that disappeared when we got mobile devices and people started going mobile. Sounds like a Who song—“Going mobile, mobile”—anyway. But yeah, I don’t disagree with you.

    Liz, let me ask you. I mean, mParticle, is this sort of the—it seems like it’s right in the sweet spot for what you guys are doing, then, right? This is the mission.

    Zalman: This is the mission, yeah, and it’s, and actually, Dave, shifting from—I mean, what do you call Greenhouse, ATS?

    Anderson: Yeah.

    Zalman: It’s a form of data management, actually, shifting into customer data. It’s a vertical that I hold dear, because I actually started my career in ad tech, and what he’s describing is what I wanted a decade ago. So, like, I personally love the fact that mParticle is a customer. [Laughter] There is simply no place to store that stuff and then to link it across various touchpoints—it never came to fruition.

    But yeah, a company that is distributed, that isn’t hyper-growth, it has large corporate clients who have, I’m guessing—Dave, tell me if I’m wrong—contractual requirements with respect to security and pen testing in various attestations.

    Anderson: Of course, yeah.

    Zalman: Yeah. [Laughter] Yeah, we do a good business in that area, and it hits all those things.

    Shimel: Very cool. Guys, we’re about out of time. Dave, I appreciate you taking time out of your busy day on the boat to join us here. [Laughter] All kidding aside, man, it actually is a very great socially distanced way to get work done.

    Anderson: Yeah.

    Shimel: Truth be told, I’m supposed to be on a boat tomorrow and I canceled, because I had some stuff come up, and [Cross talk].

    Zalman: Alan, it’s not that strongDM helps Dave sleep better at night, it’s those waves in the harbor, too. [Laughter]

    Anderson: [Laughter]

    Shimel: Yeah, well, that—right, they’ll help you sleep, either way. They’ll help you sleep well, as well.

    Anderson: Yeah.

    Shimel: I’m not gonna go there, though, Liz. You know, leave Dave alone.

    Anderson: It’s also my alarm clock in the morning. [Laughter]

    Zalman: [Laughter]

    Shimel: Yeah, that’s exactly it. You know what, alright, the guy’s on a boat, there’s worse things. It doesn’t make him a spoiled person. I don’t wanna get—you know what, but for all those people who say CISOs are underworked and overpaid, as Dave’s living here on the boat, that’s not true. CISOs are overworked and underpaid.

    But anyway—Liz, thanks for joining us.

    Zalman: Thanks, Alan.

    Shimel: We’ll hopefully have another interview with you soon, maybe.

    Zalman: I think we have one on Friday.

    Shimel: Very cool. Dave, thank you for joining us—great, continued success with mParticle. Sounds like a great business and a great use case here for strongDM, and enjoy—enjoy your time. Stay safe and stay well.

    Zalman: Thank you for having me.

    Shimel: Thank you. Hey, this is Alan Shimel. You just watched another TechStrong TV segment. We’re gonna be right back with another guest.

  • TechStrong TV: ‘The Startup Community Way,’ With Brad Feld

    TechStrong TV: ‘The Startup Community Way,’ With Brad Feld

    Brad Feld, co-founder of Foundry Group and Tech Stars, recently joined us on TechStrong TV to talk about his new book, co-authored by Ian Hathaway, “The Startup Community Way.” Brad is one of my oldest friends and has a lot of great insight into the tech community and the shift in the balance of power in many organizations, and his latest book discusses that at length and more.

    The video is immediately below, followed by the transcript of our conversation. Enjoy!

    Transcript

    Alan Shimel: Hey, everyone, thanks for joining us on this segment for TechStrong TV. I am, like, thrilled beyond thrilled to be joined by an old friend of mine—not that he’s old, but we’ve known each other a very, very long time—my friend, Brad Feld, who really needs no introduction in any kinda tech kinda discussion. Hey, Brad—welcome.

    Brad Feld: Alan, it’s great to be here. Awesome to see you.

    Shimel: It’s awesome to see you, my friend. I haven’t seen you in too long, and I don’t know when I’m gonna see you in person again with the current state of affairs, but I hope it’s soon.

    Feld: I get virtual Alan and you get virtual Brad.

    Shimel: That’s the best that we’re gonna have to do. So, Brad, we have you on here today because your book came out, I guess it was last week it came out officially, right? And it’s called “The Startup Community Way.” It is a sequel or follow on to “The Startup Community” book that you originally authored how long ago? That had to be, what, seven years ago was the first book?

    Feld: Yeah, “Startup Communities” came out in 2012, and along with the publication of “The Startup Community Way,” we came out with a second edition of “Startup Communities” that has some updates to it and some things that I got wrong the first time around fixed. So, it’s nice to freshen up.

    Shimel: Well, we’re gonna talk about those. Yep, and we should mention, Brad, that you have a coauthor in this “The Startup Community Way” book, and that’s Ian Hathaway. And Ian may be less entrepreneurial or less experienced in the VC entrepreneur world, but very experienced in research and kind of doing, you know, looking at this scientifically, if you will.

    Feld: Yeah, he was a really good coauthor, he’s become a close friend, and part of the thing that was good about it was, we do have different frames of reference. So, as we talk through and work through the book and work through different ideas around the book, you know, pressing against each other from different frames of reference really generated, I think, much better ideas and much better writing.

    Shimel: Excellent. So, Brad, I’m gonna make some assumptions, here. First of all, our audience is a very geeky, techy audience, right? We cater to digital transformation, DevOps, cloud-native, open source kinda stuff, and of course, cyber. They know who Brad Feld is. They’re familiar with tech stars, they’re familiar with startups, they’re probably even familiar with the term startup community, which you kinda initially coined with the book, right? So, I don’t want to spend all of our time sort of laying that foundation. They’re familiar with who Brad Feld is as well.

    And if you’re not, I’m gonna tell you really quick. I sold my first company to Brad in 1997. He’ll tell you I was wearing a stupid sports jacket, but we’re not even gonna talk about it. [Laughter] He’s been at SoftBank Venture Capital, Mobius, Foundry Group, started Techstars, one of the kind of forces behind—how do you pronounce it? National Nitwit is—what does it stand for, Brad?

    Feld: NCWIT, National Center for Women in Information Technology.

    Shimel: Yep, and, you know, one of my favorite things you’ve done. But, I mean, beyond—we could go on and on, but let’s not. Brad, I started reading “The Startup Community Way,” and I have some issues, questions, areas I want to jump in on with you if it’s okay.

    Feld: Sure. So, obviously, with your initial “Startup Community,” you had what you coined the Boulder Thesis, and there were four main points in the Boulder Thesis. Number one, though, and sort of primal to me was that, for startup communities to thrive, they need to be led by entrepreneurs, right? These entrepreneurs had to have a long-range kinda commitment to the community, and let’s stop right there for a second.

    Shimel: I noticed in this, in the new book, you kind of made a realization that, in informing that, we set the entrepreneurs up as sort of the alpha predators, as the top dogs on the food chain, right? But in doing so, it might have created a little bit of us versus them between entrepreneurs and the other, I’m not gonna say equal participants, but vital participants in this equation of a startup community. The workers of these companies who go to work at entrepreneurs, universities, government agencies—the community, right? It’s not just entrepreneurs.

    And I think one of the things you’re seeking to address in the book is to kinda ease that tension, the us-versus-them tension, correct?

    Feld: Yeah, that was a mistake I made in the first book, and it was a mistake of language, not of intent or description. So, in the first book, I made the strong assertion that the leaders of a startup community have to be entrepreneurs and, in the absence of a critical mass of entrepreneurs playing leadership roles, your startup community won’t grow and evolve.

    I then labeled everyone else a feeder, and my intention was not to have leaders be one up on feeders—you know, one up, one down relationship—but just different. And I tried to categorize them differently and spent a fair amount of time in the book describing what leaders do and what feeders do. And the miss was, there’s a lot of people who play leadership roles in startup communities who are not entrepreneurs, and in the new book—and I also went back and updated the second edition of the old book—I now call them instigators. And the idea of an instigator is that they are playing a leadership role in the startup community, and that’s a very powerful notion.

    So, essentially, people now are classified as leaders and instigators, and the organizations are feeders, and that’s really important, because the organizations tend to be hierarchical. They tend to have their own agenda in addition to the agenda of the startup community. And the fundamental goal of a startup community, pure and simple, is to help entrepreneurs succeed. And the feeder organizations, part of their goal as organizations are to help entrepreneurs succeed, but that’s not their only goal.

    We also distinguish now between the notion of a startup community and an entrepreneurial ecosystem. A startup community, at its core, exists to help entrepreneurs succeed, and an entrepreneurial ecosystem has, at its core, a startup community, but it’s a much bigger thing, and it engaged all of these other organizations around their goals and how they engaged with entrepreneurship.

    So, I think we’ve done a better job in “The Startup Community Way” of talking about leadership and who provides leadership and the people providing the leadership in the startup community being both the leaders, the entrepreneurs, and the instigators, people who aren’t entrepreneurs, but who are playing a leadership role. And then the organizations, the other actors who contribute to the startup community but don’t control it, don’t try to organize it, don’t try to run it, just participate in it.

    Shimel: Excellent. You know, Brad, there’s a lot of analogies there to what we see in the DevOps world, right? The developers have become the entrepreneurs of the first edition of startup community, where it seems the rest of the DevOps ecosystem revolves around these developers, and look, developers are impossible to hire. They’re, as you know from your companies, they demand a lot of money, they want a lot of say over their environments, their culture, and everything else. They’re kinda calling the shots, and the rest of the world kind of revolves around it.

    But also, a lot more is thrown on these developers’ shoulders in terms of what—they’re no longer responsible just for code, they’re responsible for deployment, they’re responsible to make sure the testing is right, you know, for that whole software factory. They, in essence, run the factory. And a similar kinda thing has happened in DevOps where we say, “Hold on—yes, the developers’ role is a very important role, but so is that of the cyber person, so is that of the SRE, so is that of the tester. And literally, it does take a community, and it’s caused a bit of a realignment, if you will, within how we look at DevOps and cloud native and continuous deployment.

    I wonder, you know, carrying that analogy out, Brad, though, I think a lot of our audience out here, they tend to interchange entrepreneur with technical entrepreneur, and I wanted to talk to you about the role of the business entrepreneur for my own selfish reasons, but you know—and you have a ton of experience on this. When we talk about entrepreneurs, Brad, how much of it is, you know, so a technical entrepreneur, the kind of person who goes on to be the CTO in their startup or in their company versus people who come from the business side of things, right? And what’s the right mix, or what’s a—I don’t know if there is a right mix, but what’s the right formula for when we look at the entrepreneurs within the greater entrepreneurial ecosystem, within the startup community, between technical entrepreneurs and, let’s call them, business-orientated entrepreneurs? Make sense?

    Feld: Well, they’re both—it makes total sense. They’re both essential. And when I talk about entrepreneur, I don’t really distinguish between the two. I think there are many different roles that founders or entrepreneurs play. And, for a lot of people, the word entrepreneur tends to be triggering. Like, it used to be something that was very well understood.

    Today, the word entrepreneur gets used, I would say, almost indiscriminately in a lot of different contexts. And, to your question, I would come back to the notion specifically of a founder. A founder of a company, somebody who is one of the people who helps create the company from the very beginning, and you need a combination. You need technical founders, technical entrepreneurs. You need business founders, business entrepreneurs. Most companies generally have more than one co-founder, but there are definitely successful companies with one founder.

    But generally speaking, if you have more than one founder, especially if you have a combination of a business founder and a technical founder, you can make a lot more progress a lot quicker in many cases. And if you have three or four founders, I generally try to encourage people to have at least an equal number of technical founders to non-technical founders, and preferably, more technical founders than non-technical founders. And, you know, Alan, you’re humble. I mean, you talk about yourself as the business guy, but you have very, very deep technical experience at this point. Even when I met you when you were running your first company in the late 1990s, you had deep technical experience.

    So, the technical founder doesn’t necessarily mean just somebody who writes code, and I like to shift the language to be product-oriented instead of technical. So, if you think about three founders, three co-founders, the idea that two of them are focused on product and one of them is focused on the business, and the product and the business obviously overlap with the customer, and so, all three of the founders are paying attention to the customer, the evolution of what you’re trying to do from the very beginning can move a lot quicker.

    By the way, there are a lot of very, very good technical founders who also have strong business sense in the same way that you’re a strong business person that also has strong technical sense. So, it’s not cut and dried, and you’re not like, “Oh, I’m in this box and you’re in this box.” I try to encourage entrepreneurs to think more broadly about what they’re doing and how they’re doing it.

    Shimel: Excellent. Hey, I’d like to shift a little bit away from the entrepreneur because they get all the press, anyway. I want to talk about something that was really highlighted in your book, and that is the role of, within the community, within the ecosystem, the role of universities and the role of government, the role of these hierarchical groups as you referred to them.

    Let’s talk a little—and I’m gonna bring it home to what I see here in South Florida, for instance, but Brad, you know, (a) it’s an important role they played in this big picture, but what optimally, what can the government do optimally, for instance, to help you—there’s federal, there’s state, there’s local—you know, where do you see it?

    Feld: You have to be somewhat granular, and you also have to be focused on the specific place that you’re at, whether it is local, state, or federal or national governments. Interestingly, in the first book in 2012, I basically punted on this issue. I said, “The best government can do is do no harm to the startup community.” And, you know, I would say that was a combination of me not really having a particularly clear view of what government could have along with me kinda punting and being lazy about digging into it—based on my own experience, my own experience in Boulder, for example, is that the local government basically pays no attention to entrepreneurship and doesn’t really understand how to engage it in an effective way.

    The state of Colorado government, actually, has done a pretty good job, and there have been a number of things over the years that the state of Colorado has done around this and then, you know, our federal government in the U.S. ebbs and flows. Sometimes there are some programs that are incredibly helpful and oftentimes, there are things that either get in the way or are counterproductive.

    So, I’ve come to a place where what I think is important for government at any level to start with is to understand what their goal is. And I’m gonna come back to this statement I said earlier, which is, the goal of a startup community is to help entrepreneurs succeed. So, if government wants to engage in the startup community, their goal should be to help entrepreneurs succeed.

    Now, at a local level, that often means that the best way to do it is an instigator—gonna use that word again—who is a person who works for a local government who actively engages as a leader in the startup community. So, they’re not actually bringing government so much to the startup community, but they’re, in their role in government, they may have a full-time job to help with economic development or developing the entrepreneurial ecosystem or whatever it is. Like, their first step should be to become part of the startup community as an instigator rather than show up as government and say, “Hi, I’m from the government, I’m here to help.”

    Shimel: Mm-hmm.

    Feld: One of the things the government really struggles with is allocating capital. Government has a lot of capital, as we’ve just learned from the COVID crisis. You know, overnight, the federal government allocated or deployed $2 trillion, and it looks like it’s gonna allocate another $1 trillion across their society. And a lot of that money went towards helping, quote, small business, where government thinks of small businesses and entrepreneurial businesses as the same.

    If you use that lens, though, and you look at how that money was allocated, it was primarily allocated through two vehicles, PPP loans and EIDL loans. It was incredibly inefficiently allocated, and as a result, some companies got financial support, others didn’t. And it was done in this very, very sort of explosive way that may have had some very powerful short-term impacts, but it’s unclear on whether it has medium or longer-term impacts.

    One last sort of comment on governments, state [Audio skips] governments over and over again. We need more venture capital here, we need more capital here, and we need to do things to get more capital here. In “The Startup Community Way,” we actually defined capital as having seven different flavors, where financial capital was one. Because generally when people talk about capital, they’re talking about money, and this is another place where governments can really help is to think about what capital the startup community already has that’s not financial capital—what kind of intellectual capital, what kind of network capital, what kind of infrastructure capital exists and what more is needed. And then try to figure out how to use the resources of local or state government to amplify those types of capital that ultimately then is a positive reinforcing loop to attract other sources of capital.

    So, unfortunately, it’s—I think, for government, it’s nuanced, and a lot of times government is looking for a playbook and a solution, like, “I just need to do the following four things and then good things will happen.” And this is essential to “The Startup Community Way” where we talk about startup communities now as complex systems.

    Shimel: Yeah.

    Feld: And one of the things that many organizations have a lot of trouble interacting with—especially government, but not exclusively government—is complex systems.

    Shimel: So, let me talk a little bit about complex systems here in South Florida. I know you’ve been down in Miami a few times, you’ve had a chance to see sort of the Miami startup scene and, you know what, in four or five short years, it’s actually come a long way. You know, it’s the gateway to Latin America and they talk about all that, but more importantly, there are some really concrete programs, the Knight Foundation, a few other organizations as well as local government has instituted it, and we’re beginning to see a startup community take hold there, in my opinion. It’s not bolder, it’s not awesome, but it doesn’t have to be, it’s Miami, and it does it in its own unique Miami way.

    But South Florida is more than Miami, right? You basically have a tri-county or three city sort of metro area of Miami, Fort Lauderdale, and West Palm Beach. Taken together, I forget if it’s the six or seventh largest metropolitan area in the U.S., right, between these three counties—Miami-Dade, Fort Broward, and Palm Beach County. A tremendous amount of universities, we haven’t even talked about universities yet, but we have University of Miami and FIU and FAU here. Lots of universities—universities that are, you know, in your first book when you talked about the role, you know, they do serve as anchors.

    I think what holds us back in the South Florida area, though, Brad, is that we have shoguns, right? I remember when your business card used to shogun, remember those days? [Laughter] But we have shoguns here every 10 or 15 miles, each little town or incorporated village is afraid that the next one is gonna do more, better than them.

    Here in my little neck of the woods, Boca Raton and Delray Beach constantly—they’re right next to each other—constantly banging heads. Boca has the universities, maybe a little more capital. Delray has a great sort of startup scene brewing and they do have local economic development and a number of co-working places and stuff like that. But they can’t seem to get their act together to work—and these are just two little, piddling towns, to tell you the truth, right? If they would put it together, they might have something—but they can’t, they’re too busy competing. And it’s the same thing up and down this coast, right?

    So, you have an area with a lot of universities, a lot of capital, a decent amount of tech talent—I mean, not deep enough, by any means—and certainly, many entrepreneurs. But they’re at loggerheads. How do you—in creating this entrepreneurial ecosystem, how do you overcome this sort of petty jealousy, these shoguns fighting for supremacy?

    Feld: Well, you have to start from a perspective of playing a positive-sum game, and what you’re describing is a classic zero-sum game, where there’s winners or losers.

    Shimel: Yep.

    Feld: And, you know, the ones that we’re used to in terms of zero-sum game and election is a zero-sum game, somebody wins, somebody loses. Sports of events, most of them, zero-sum game—winner, loser, sometimes you tie if you play soccer. But, you know, for most games, there’s a definitive winner or loser. You don’t wanna play a zero-sum game

    You wanna play the opposite of that, which is a positive-sum game where the cliché would be a rising tide lifts all boats, right? You’re helping each other over time sort of building something that’s more and more successful. And, in defining startup community, you can define startup community however you want in terms of geography. You can define it in a little town like Boca or Delray. You can draw a bigger circle around it and call it the Greater Miami Metro Area or whatever you wanna call it.

    By the way, you said something earlier that’s really important is that you don’t need to create or emulate somebody else. Boulder is Boulder, Miami is Miami, Greater Miami is Greater Miami, Boca is Boca—like, you already have an identity as a city. But the key is to try to work with the people who are close to you to build a broader and more robust startup community. And, interestingly, if you’re taking this approach and playing a positive-sum game where you help each other versus you compete for resources and you compete to win or lose in sort of an inappropriate way or an unhelpful way, it doesn’t really matter.

    The very specific example I’d give you is that, does it cost anything to travel from Delray to Boca? Do you have to pay—

    Shimel: You could walk.

    Feld: – you could walk, right? You don’t have to pay a tax, you don’t have to have somebody, you know, stamp your passport to get from one place to another. I mean, you really are part of a—

    Shimel: Not yet.

    Feld: – not yet. You’re part of a collaborative collection of people, and the goal should be that you wanna encourage cross-fertilization between these communities and you wanna encourage amplification of what’s going on and get critical mass around it.

    Now, there’s nothing wrong with local pride, and I can use Boulder and Denver as really good examples of that. Boulder and Denver are both very, very vibrant cities. Boulder is 100,000 people, Denver is 2,000,000 people. They’re about a 30- to 45-minute drive apart from each other. They have independent identities, but there’s an enormous amount of collaboration between the two, and that’s very, very, very powerful.

    Shimel: I mean, so, I’ve done Meetup groups in Denver and Boulder. You know, we started one with the Jump Cloud folks called IT as Code. The first meeting was down in LoDo. But we had people from all over, from Boulder and everyone else drive in, and we had a great meeting at one of the breweries there—good times.

    I’ve started a bunch of Meetup groups here in South Florida, and we’re constantly, “Jeez, we have to do this one in Miami for the Miami people. We need to be down near Fort Lauderdale-Hollywood this time, or out at the university out West there to attract that Broward crowd.” There isn’t that sense of community that the rising tide lifts all boats, and I’m hoping that books like “The Startup Community Way” kind of make their way into the stream here, the mainstream of what these people are thinking about.

    We even see it, Brad, with—so, we have the South Florida Technology Association, then we have the Palm Beach Technology Association. There’s several counterparts in Miami. They even compete at such a—and it’s a petty competition, frankly.

    Feld: Well, they could really change the game in the region by deciding to collaborate, and they can have separate organizations with separate memberships and separate goals even if they’re in the same place because there’s no need for there to be one monolithic thing. In fact, you probably want a bunch of different things. But instead of viewing it as an, “I win, you lose,” they’re all trying to help entrepreneurs succeed. And in the context of that—again, the instigators, the leaders of those organizations, right, those organizations, even if they’re comprised of entrepreneurs, they’re still feeder organizations, right? The organization themselves is a feeder supporting entrepreneurs. The people in those organizations who are playing leadership roles can play a leadership role in the startup community, which is separate from their organization. Their organization is not the thing that’s organizing, managing, running the startup community. It’s just another participant in this.

    And so, changing that frame of reference for humans is hard, because we’re used to competing, and you know, we’re—

    Shimel: No, it’s like “The Highlander”—there can be only one. [Laughter] Right? And it’s a problem—I get it.

    Feld: Well, and changing that is important and, you know, it’s one thing to say it’s important to change; it’s another thing for a bunch of leaders in a startup community to say, “You know what? Enough of this. We don’t need the segmentation, we don’t need the competition. Let’s all pull together even though we’re addressing different things, and we have some overlap. We’re trying to do something together that makes our place better.”

    Shimel: Fantastic. Brad, we’re almost out of time. I wanted to leave you a couple minutes at the end here for our audience watching. If you had the three biggest takeaways from the book that you want people to go home with, what would you say they are?

    Feld: The first is the distinction between a startup community and an entrepreneurial ecosystem and the reinforcement that the goal of the startup is to help entrepreneurs succeed, and you can define everything from there.

    The second is that a startup community is a complex system, and in a complex system, there is no deterministic outcome. There is no playbook. There is no set of rules to get from Point A to Point B. A simple system would be making a cup of coffee. You put beans into the machine, you get coffee out. It might not be a good cup of coffee, but it’s a cup of coffee.

    Shimel: Coffee it is.

    Feld: Coffee it is. A complicated system would be manufacturing a Boeing 787 airplane. Once it’s designed, the rule book’s now really big, but you put parts at the beginning and at the end comes out a Boeing 787.

    A complex system would be raising a child—and you’ve raised two. And you know that on day one of the child, what you tell the child to do and what you aspire for the child to do at age 21 is not what’s gonna happen. Every little thing you do, the child evolves and changes and grows and develops and all that stimuli is positive and negative along the way. And at the end, the child is whatever the child is. But it evolves in a way that you can’t predict. That’s what a startup community is—you cannot predict what that outcome is and you can’t control the outcome.

    The last—and we cover this in the book and there’s several examples. I gave one which was the notion of capital not just being money and defining it as the seven capitals instead of just financial capital. Another would be something we could call the measurement trap. Everyone in a startup community feels the need to measure things, and this is especially true for government, this is especially true for nonprofits like the different associations that you probably described.

    They’re measuring constantly—number of companies created, number of unicorns, dollars raised, number of jobs. These are things to measure, but they’re not the important things, they’re the easy things. And the really important thing that happens in the growth and development of a startup community and complex system is not the parts, not creating more pieces, it’s the interaction between the pieces, interaction between the parts. And measuring that interaction is really, really difficult, but that’s where all the power comes from.

    Shimel: Got it. Love it. Hey, Brad, first of all, thank you so much. I know you’re crazy busy with promo-ings on the book and everything, so thanks for taking the time to come join us here on TechStrong TV. Best of luck with the book. We should mention it’s available on Amazon, it’s on all the usual places where one buys books today. Not going to book stores very much, unfortunately, but yes. So, it’s “The Startup Community Way,” Ian Hathaway, Brad Feld—check it out. It’s available in Kindle and hardcover at this point. I don’t think a paperback is out yet, right?

    Feld: No paperback yet, just Kindle.

    Shimel: Yep, hard book and Kindle. I have it on my Kindle here, I was all ready with my notes—but Brad Feld, author, “The Startup Community Way,” Foundry Group, Techstars, tech entrepreneur extraordinaire, and one of my best friends for a long time.

    Feld: Thanks for doing this, it’s so awesome to see you, and congrats on everything you’re doing with your business now. It’s wonderful to see it.

    Shimel: Thank you.

  • RecruitOps, A Better Way To Fill Technical Roles

    RecruitOps, A Better Way To Fill Technical Roles

    Today at MediaOps, we are really excited to announce the launch of RecruitOps, a new and exciting way for companies to find the right candidates for hard-to-fill technical positions. It’s also a great place to find your next career stop.

    Sitting at the nexus of a worldwide audience of the biggest DevOps, cloud-native and cyber talent pool in the world—and a destination where organizations ranging from startups to enterprises come to stay relevant—devopsy.kinsta.cloud and other MediaOps destinations provide the perfect partner for this mission.

    The Usual Suspects Don’t Work

    For the last three or four years, I’ve been receiving multiple calls every week asking if we can help organizations find talent to fill their open reqs. Finding and hiring good DevOps, cloud-native and cyber talent is difficult and expensive and can be frustrating. Many companies have discovered that job boards and LinkedIn-type solutions create lots of noise, yielding slim pickings of viable candidates. Most candidates are misfits, either skills-wise or geographically.

    Also, traditional recruiters are not only expensive but they also operate in factory mode, often flooding your inbox with resumes of candidates they haven’t actually vetted first. There is a better way to do this—we think we have cracked the formula.

    By the same token, I receive messages on LinkedIn every day from people I don’t even know asking to help them find a DevOps or cyber job. The process of applying and being one of many résumés in a pile is not something they excel at navigating.

    Over the years we have tried job boards and relationships with large job fulfillment organizations. None of them were very successful. They were just not an effective way of matching our large audience of DevOps professionals with the many companies and organizations looking to find the right talent to fill their technical roles.

    RecruitOps: A Better Way

    My co-founder at MediaOps, Martin Logan, has lived this dilemma for years now. His full-time roles have been in building large engineering, product and DevOps teams in the online travel, retail, mortgage and gaming industries. He has tried every method you can think of.

    What Martin discovered was that the most effective method was to work with a small group of recruiters. These recruiters had to be very familiar with the technology and technical requirements of a requested position. They had to be able to talk the technical talk and understand it. More than that, though, they had to understand the culture and environment in which the candidate would work and what it would take to be successful there. This kind of information is best gained by developing a strong personal relationship with the hiring manager and the manager of the prospective technical position.

    That is the model we have built RecruitOps around. Our founding recruiters are people Martin has personally invested months and years in training. They know how to find the perfect fit for your technical roles. They know how to work with your organization and what it takes to be successful. They will not throw résumés at the wall to see what sticks.

    This is not a high-volume, résumé factory. At RecruitOps our recruiters are very familiar with the technical requirements that candidates must possess. They spend a lot of time with the hiring manager and position manager to understand what the perfect candidate must have skills-, temperament- and team fit-wise.

    Our RecruitOps recruiters then spend a lot of time getting to know the candidates before they send them to you. Combining devopsy.kinsta.cloud, Security Boulevard, Container Journal and even the DevOps Institute, our pool of talent for these technical jobs is deeper than just about anyone. We will find you the perfect fit guaranteed, or you don’t owe anything.

    No Risk to You

    Yes, that is another feature of RecruitOps: There is no risk on your end. If our candidate does not work out, you don’t owe anything. There is no money upfront—it’s a risk-free proposition all around. You literally have nothing to lose and great technical team members to gain.

    Does this sound like a better way for you? If so, head over to RecruitOps.com and get started today.

    Likewise, if you are looking for your next career move, head over to RecuitOps and put yourself on our radar. It is the first step in working with us to find you the perfect fit as well.

    In the Middle of a Pandemic?

    I know what some of you are saying: Wow, we are in the middle of a COVID-induced economic catastrophe. Isn’t this an odd time to start a recruiting business? You may be right. But we think this is the perfect time to start RecruitOps. Companies are realizing that there is actually some great talent available. Still hard to find, but more available than six months ago, perhaps.

    Also, organizations that are digitally transforming need help from technical people to make these transformation happen in a secure manner. We are betting smart organizations are adding great talent if they can get it because great talent is always in demand.

    Are you a smart organization looking to add great talent? Head on over to RecruitOps.com.

  • MediaOps Makes the Inc. 5000 List

    MediaOps Makes the Inc. 5000 List

    Here at MediaOps we have two big announcements today. The first is that we have earned a place in the Inc. 5000 annual ranking of the fastest-growing companies in America. We didn’t just make the list—we came in at 1,622, well in the top half of companies on the list.

    The other announcement is that we have relaunched our MediaOps website, at mediaops.com. With updated positioning and messaging, our new site better reflects who we are today and what both our sponsors and visitors want to know about us.

    Both of these announcements are linked in a way that may not be obvious to the casual observer. As the founder of this company, I am extremely proud of what we have accomplished that has resulted in our earning this honor. When I look at our new website and its impressive information about MediaOps, I am even more proud. But I am most proud when I look at the team page and look at the great group of people who make up our team.

    To give you some background for insight, we started this company about seven years ago with devopsy.kinsta.cloud. It was going to be a blog with myself as the primary author. But even then we had plans that maybe there would be more. We chose MediaOps as the corporate name in case we ever did more than devopsy.kinsta.cloud. My partner Martin Logan came up with the name, actually.  But when we went to register the domain, we could not get the Mediaops.com name. Instead, we registered MediaOps.io, figuring it wouldn’t make much of a difference because no one would know our corporate name anyway.

    MediaOps and the MediaOps website shared a common theme. We really didn’t care if anyone knew the name or the website, really; we didn’t have the bandwidth or resources to promote that in addition to devopsy.kinsta.cloud. Parker Yates, our Chief Revenue Officer, and I developed many of the sponsored services we offered, which were centered around devopsy.kinsta.cloud and then its associated properties.

    With the launch of Security Boulevard and Container Journal, we again put whatever resources we had toward establishing those brands in their own right. We never really had a focus on the MediaOps brand and MediaOps website.

    Equally so, we really never thought about MediaOps being a fast-growing company that would become one of the fastest-growing companies in the U.S. Who had time for that? We were too busy delivering the next webinar, the next article, attending the next conference. Our mission was to help grow and establish the communities we lived in.

    Today, MediaOps is a different company than it was seven years ago. We are more than 20 people strong, operate over a dozen different websites and all the other great metrics that go with this kind of success. We began to realize that our hard work was resonating and our sponsors looked to us as a reliable partner in delivering thought leadership, branding and lead generation activities. Our audience has come to expect quality content across all available channels.

    We developed beyond the written word. Our virtual events, video, audio and even comics are different distribution channels to the same audience we serve: DevOps, Digital Transformation, Cyber and Cloud-Native. Taking our audience focus and our means of distribution, we call this the omniverse.

    Our new website at Mediaops.com (we thought it was time to buy and own the domain) reflects all of this and more. Despite the current COVID-19 crisis, MediaOps is well-positioned to build on its success. In the weeks and months ahead, we will continue to make more announcements and bring new activities to the MediaOps omniverse.

    Finally, I want to thank you, our audience, most of all. None of this success would be possible without you. Thanks for the support, thanks for being who you are. Our mission really hasn’t changed: We will continue to bring you the best content we can find via every channel we can use to contact you. That is the Mediaops Omniverse.

  • DevOps Unbound: Exploring Acceleration and Automation, Setting DevOps Free

    DevOps Unbound: Exploring Acceleration and Automation, Setting DevOps Free

    We are launching a new video series Thursday, Aug. 6, called DevOps Unbound. DevOps Unbound will focus on DevOps, automation, CI/CD and testing, featuring leaders in these areas as we explore the challenges and issues software delivery and IT teams face every day. How do we go faster, smarter with better quality? DevOps Unbound!

    The series will premier on our TechStrong.tv streaming network and should start around 10:40 a.m. Eastern tomorrow, August 6th. It will be available on Linkedin Live (on the devopsy.kinsta.cloud page), Facebook Live (devopsy.kinsta.cloud, Container Journal or Security Boulevard pages), YouTube on the DevOpsTV channel and the MediaOps sites. Additionally, the show is available on-demand on our devopsy.kinsta.cloud mobile app and our devopsy.kinsta.cloud OTT channels on Roku, Apple TV and Amazon Fire TV. Finally, all episodes will be available on-demand on Digital Anarchist, our streaming video platform. The series is sponsored by our friends at Tricentis.

    New episodes will run every other week. Also planned is a monthly DevOps Unbound roundtable, open to the public and featuring a revolving panel of experts around a given theme. The first live monthly roundtable will be Aug. 18, around the theme “DevEverythingOps.” Roundtable discussions do require registration; you can register for the first event here.

    Premier Episode August 6th

    The premiere episode features Dr. Grigori Melnik, CPO of Tricentis, and James Bach, the developer of session-based testing and a highly respected expert in testing. We will explore the history of testing and how it has adapted over the years to allow for more automation, help testers and developers be more efficient and accelerate the software release process.

    These are two people renowned in their fields who arrived here from very different paths. Bach is a high school dropout who was bitten fiercely by the computer bug. He was a game developer and then a coder who became one of Apple’s first test engineers in 1987. Dr. Grigori Melnik has a Ph.D. in testing and is a respected authority in both the academic and business worlds.  Though they come from different backgrounds, they have more in common than you might think. It was a great discussion and one I think you will really enjoy.

    Future episodes of the bi-weekly show will feature topics including DevSecOps, open source, cloud-native, CI/CD, SDM, DataOps, observability and more. We think DevOps Unbound will quickly become an essential part of your DevOps information arsenal.

    We are always on the lookout for future topics and guests. If you think you would like to take a giant leap with DevOps Unbound, reach out to me at unbound@devops.com with your idea and we can follow up.

    BTW, DevOps Unbound is just one of several new shows we are premiering on TechStrong TV and Digital Anarchist. Another is CISO Talk, featuring Unisys CISO Mathew Newfield and me. That will be on TechStrong TV this coming Monday. More announcements to come about new, recurring shows.

    We recognize that people want to see video content and at MediaOps/devopsy.kinsta.cloud we are producing lots of exciting new video content. Stay tuned.