The Power of Aligning Engineering and Operations with Dave Mangot
The Business of Open Source15 Heinä 2020

The Power of Aligning Engineering and Operations with Dave Mangot

Some of the highlights of the show include:


  • The difference between cloud computing and cloud native.
  • Why operations teams often struggle to keep up with development teams, and the problems that this creates for businesses.
  • How Dave works with operations teams and trains them how to approach cloud native so they can keep up with developers, instead of being a drag on the organization.
  • Dave’s philosophy on introducing processes, and why he prefers to use as few as possible for as long as possible and implement them only when problems arise.
  • Why executives should strive to keep developers happy, productive, and empowered.
  • Why operations teams need to stop thinking about themselves as people who merely complete ticket requests, and start viewing themselves as key enablers who help the organization move faster.
  • Viewing wait time as waste.
  • The importance of aligning operations and development teams, and having them work towards the same goal. This also requires using the same reporting structure.


Links:

Transcript


Announcer: Welcome to The Business of Cloud Native podcast, where we explore how end users talk and think about the transition to Kubernetes and cloud-native architectures.



Emily: Welcome to The Business of Cloud Native. I'm your host, Emily Omier, and today I am chatting with Dave Mangot. And Dave is a consultant who works with companies on improving their web operations. He has experience working with a variety of companies making the transition to cloud-native and in various stages of their cloud computing journey. So, Dave, my first question is, can you go into detail about, sort of, the nitty-gritty of what you do?



Dave: Sure. I've spent my whole technical professional career mostly in Silicon Valley, after moving out to California from Maryland. And really, I got early into web operations working in Unix systems administration as a sysadmin, and then we all changed the names of all those things over the years from sysadmin to Technical Infrastructure Engineer, and then Site Reliability Engineer, and all the other fun stuff. But I've been involved in the DevOps movement, kind of, since the beginning, and I've been involved in cloud computing, kind of, since the beginning.



And so I'm lucky enough in my day job to be able to work with companies on their, like you said, transitions into Cloud, but really I'm helping companies, at least for their cloud stuff, think about what does cloud computing even mean? What does it mean to operate in a cloud computing manner? It's one thing to say, “We're going to move all of our stuff from the data center into Cloud,” but most people you'll hear talk about lift and shift; does that really the best way? And obviously, it's not. I think most of the studies will prove that and things like the State of DevOps report, and those other things, but really love working with companies on, like, what is so unique about the Cloud, and what advantages does that give, and how do we think about these problems in order to be able to take the best advantage that we can?



Emily: Dive into a little bit more. What is the difference between cloud computing and cloud-native? And where does some confusion sometimes seep in there?



Dave: I think cloud-native is just really talking about the fact that something was designed specifically for running in a cloud computing environment. To me, I don't really get hung up on those differences because, ultimately, I don't think they matter all that much. You can take memcached, which was designed to run in the data center, and you can buy that as a service on AWS. So, does that mean because it wasn't designed for the Cloud from the beginning, that it's not going to work? No, you're buying that as a service from AWS.



I think cloud-native is really referring to these tools that were designed with that as a first-class citizen. And there's times where that really matters. I remember, we did an analysis of the configuration management tools years back, and what would work best on AWS and things like that, and it was pretty obvious that some of those tools were not designed for the Cloud. They were not cloud-native. They really had this distinct feel that their cloud capabilities were bolted on much later, and it was clunky, and it was hard to work with, whereas some of the other tools, really felt like that was a very natural fit, like that was the way that they had been created. But ultimately, I think the differences aren't all that great, it just, really, matters how you're going to take advantage of those tools.



Emily: And with the companies that you work with, what is the problem or problems that they are usually facing that lead them to hire you?



Dave: Generally the question, or the statement, I guess, that I get from the CIOs and CTOs, and CEOs is, “My production web operations team can't keep up with my development teams.” And there's a lot of reasons why those kinds of things can happen, but with the dawn of all these cloud-native type things, which is pretty cool, like containers, and all this other stuff, and CI/CD is a big popular thing now, and all kinds of other stuff. What happens, tends to be is the developers are really able to take advantage of these things, and consume them, and use them because look at AWS. AWS is API, API, API. Make an API call for this, make an API call for that.



And for developers, they're really comfortable in that environment. Making an API call is kind of a no brainer. And then a lot of the operations teams are struggling because that's not normal for them. Maybe they were used to clicking around in a VMware console, and now that's not a thing because everything's API, API, API. And so what happens is the development teams start to rocket ahead of the operations teams, and the operations teams are running around struggling to keep up because they're kind of in a brand new world that the developers are dragging them into, and they have to figure out how they're going to swim in that world.



And so I tend to work with operations teams to help them get to a point where they're way more comfortable, and they're thinking about the problems differently, and they're really enabling development to go as quickly as development wants to go. Which, you know, that's going to be pretty fast, especially when you're working with cloud-native stuff. But I mean, kind of to the point earlier, we built—at one of the companies I worked at years ago—what I would say, like, a cloud environment in a data center, where everything was API first, and you didn't have to run around, and click in consoles, and try to find information, and manually specify things, and stuff like that; it just worked. Just like if you make a call for VM in AWS, an EC2 instance. And so, really, it's much more about the way that we look at the problems, then it is about where this thing happens to be located because obviously cloud-native is going to be Azure, it's going ...

Jaksot(267)

ATO special episode with Peter Farkas

ATO special episode with Peter Farkas

In this special episode recorded at All Things Open, I talk with Peter Farkas, CEO and co-founder of FerretDB. We talked about about MongoDB and the license change fiasco and why Peter wanted to build an open source company and never considered building a non-open source company. The biggest 🤯 in this episode was about enforcing what it means to be open source; in particular, FerretDB positions itself as a truly open source alternative to MongoDB, and has received threatening letters from MongoDB as a result. How do you enforce it when a company claims to be open source but does not use an OSI-approved license? How well do the average users actually understand the license implications, and if a big company says they have an open source license even though it’s source-available, not open source, how much will people understand the difference? If you want another perspective on the enforcement of advertising around open source licenses, listen to the episode I recorded with Stefano Maffulli, also at All Things Open.

12 Marras 202416min

Selling Peace of Mind with Bhaskar from YottaDB

Selling Peace of Mind with Bhaskar from YottaDB

This week’s full-length episode is with Bhaskar, founder of YottaDB. This episode was recorded on-site at All Things Open last week, and we covered a wide range of topics. Including:How the open source ecosystem, and the open source business ecosystem, has changed over the past 30+ years.Who can responsibly self-support an open source database, and who really needs to have someone to call if things go wrong. The spectrum of professionalism among open source developers How YottaDB started out as a project developed inside a larger company that was in financial services; and Bhaskar decided to spin it out as it’s own company.The challenge articulating the value of support contracts, especially for software that is reliable. Bhaskar says he is selling peace of mind more than anything else; and he works with customers to avoid incidents — because ultimately avoiding an incident is a better outcome for everyone than a quick recovery from an incident. How to convince people that they are actually not as good at managing open source databases as they think they are. We also talked about conference strategies: according to Bhaskar, the way he’s decided which conferences to exhibit at is a series of trial and error — and by the way, this is something I’ve heard from many people. Yes, you have to think about where your customers are, not where your friends are, but sometimes you don’t know ahead of time which conferences are going to have the best ROI. I’m working with YottaDB right now on how to differentiate themselves in the crowded database market — and we talk about that process a bit right now. If you’re having trouble standing out in a crowded market, you might want to work with me.

6 Marras 202429min

ATO Special Episode with Tatiana Krupenya of DBeaver

ATO Special Episode with Tatiana Krupenya of DBeaver

This special episode of The Business of Open Source with Tatiana Krupenya, CEO of DBeaver, was recorded on site at All Things Open 2024. It’s a short conversation, so we addressed one main question: What is the difference between running an open source company versus as proprietary software company? Tatiana says the difference is big — and it’s complicated. The bottom line: Your OSS can be your main competitor, and your customers have to really see the value in your commercial offering if you want to make sales. ## If you aren't sure how to talk to your potential customers are about why they should use your commercial offering, you might want to work with me.

5 Marras 202413min

Behind the Scenes of the Open Source AI Definition with Stefano Maffulli

Behind the Scenes of the Open Source AI Definition with Stefano Maffulli

This week on The Business of Open Source, I spoke with Stefano Maffulli, Executive Director of the Open Source Initiative, about the definition of open source and… the definition of open source AI. We recorded this episode on-site at All Things Open, so there’s a little bit of background noise. We talked about why OSI felt like it needed to develop a definition of open source AI, how “open source” is enforced, and the thought process behind the definition that the OSI ultimately published. We talked about open data quite a bit — different kinds of data, what kind of information and data is important to researchers and professionals in the AI space, and if there’s a way to include AI models that are trained on proprietary data in the definition of open source AI. If you are interested in open source AI, definitely check out this behind-the-scenes discussion of how, and why, this definition was published — and what the future likely holds for defining open source AI.

30 Loka 202432min

Price Anchors of Zero Dollars with Anais Concepcion and Paul Fitzpatrick

Price Anchors of Zero Dollars with Anais Concepcion and Paul Fitzpatrick

This week on The Business of Open Source, I spoke with Anais Concepcion and Paul Fitzpatrick , the co-CEO of Grist Labs and CTO of Grist Labs. We talked about managing growth of users versus growth of revenue, moving to an open source approach for technical, not technical, reasons, and open-source related product management questions for open source companies. Some really interesting themes we talked about:Moving from a SaaS first approach to also focusing on enterprise sales. Why they did that, what other sales channels that opened and what questions it also forced the company to addressUser personas versus buyer personasThe situations in which Grist is the best option — which incidentally I could not understand from the website or the project documentationThe relationship between the open source project and both enterprise sales and SaaS sign-ups. How open source has been critical for a strategic relationship Grist has with the French government, which has been important for increasing product development velocityGiving up ‘darlings’ or features that they really want to develop but that they don’t think would drive revenueThe difference Anais sees between running Grist and running non-open-source companies — one of the most interesting differences is that users often have a sense of ownership over the project that you just wouldn’t see in a fully proprietary How open source true believers often work in large companies and control budgets, and should not be underestimated. Why trying to sell based on features — including telling yourself that if you just had one more feature, you’d unlock all the sales — was a big mistake. Are you struggling with price anchors fixed around zero dollars, or can’t figure out how to manage the push and pull of developing open source and building a business? You might want to work with me.

23 Loka 202442min

Getting people to use the features you already have with Eric Holscher

Getting people to use the features you already have with Eric Holscher

This week on The Business of Open Source, I spoke with Eric Holscher, co-founder of Read the Docs. We had a really far-ranging conversation that included talking about why documentation is often so bad, why documentation should be a priority, but also Eric’s experience building Read the Docs and Write the Docs. This episode was interesting because it’s both about building an open source company and also about the importance documentation for software projects in general and open source projects. Some things we covered included: What is documentation? Is it a marketing effort, is it a part of the project itself? Eric talks about how good documentation for an open source project is a clear signal of a level of seriousness for the project. How Read the Docs was really started to support open source projects, and that is part of why there’s no enterprise installs — either you use the open source code on your own, or you use the hosted product.How Eric sees building in the open as a way to help other people become better software engineers, but that ‘helping companies use Read the Docs for free’ is not the reason he wanted to build an open source company, and he’s still not sure how to feel about the fact that this happens. You don’t get bonus points for being open source or bonus points for being bootstrapped — it won’t prevent a potential customer from using a competitive product because it has a feature that Read the Docs doesn’t have. How open source in general — and even documentation in general — can help build brand value, but it is super hard to quantify and put in a slide in a board meeting to justify an investment in open source. The decision to build Read the Docs as a business stemmed from the pressure that Eric got from having a successful open source project. How they tried very hard to avoid accepting advertisements, but they should have started doing so much sooner because it turned out advertisements is well-aligned with the things they want to be working on. The difference in risk between being open source for a database company versus an app-level open source project like Read the Docs; for Read the Docs one of the risks is the brand damage associated with people running the OSS on-prem and doing a bad job. Are you the founder of an open source company and struggling with figuring out how to manage the relationship between the project and product? You might want to work with me. Enjoy the show? Help it reach more people by leaving a review and sharing with your friends.

16 Loka 202445min

Open source companies' reputation problem with Chris Holmes

Open source companies' reputation problem with Chris Holmes

Today on The Business of Open Source, I spoke with Chris Holmes, co-founder and CEO of Greymatter. Greymatter is deeply involved in the open source ecosystem and maintains the Go Envoy Control Plane, but Chris is adamant that it is not an open source company. We had a great discussion about why that is, what it means for the company and the conversations he ends up having around open source with his customers and partner companies. Some particularly interesting points that came up:Customers worry that buying Greymatter could force them to buy enterprise versions of open source software — and Chris thinks that this could be a symptom of the fact that many users expect that they’ll end up being forced to pay for something they don’t want to pay forHow open source companies, and open source projects in general, can be viewed as risky if they are only backed by one companyWho is gonna pay for open source? How if you are going to get away from open source projects being aggressively monetized, big companies have to put their money where their mouth is and pay for open source development directlyWhy and how to get started selling to governments. Yes, the sales cycles are longer but the deals tend to be very sticky once you get in — and why Chris actually finds it easier to sell to the military than to large enterprises. What benefits Greymatter gets from being a maintainer of the Go Envoy Control Plane. Struggling with how to get your product strategy right, and find the right balance between your open source project and your commercial offering? Not sure how your user audience and customer market relate to each other? You might want to work with me.

9 Loka 202444min

Building your product with your customers with David Höck

Building your product with your customers with David Höck

This week on the Business of Open Source, I spoke with David Höck, co-founder of Vendure. We talked about switching licenses from MIT to GPL, the ways that Vendure is different from it’s competitors and how architectural decisions can be a powerful differentiator for an open source company. Favorite quote: “You need to build your product together with your clients.” Some specifics we talked about that you should pay attention to: Why they switched to GPL in order to encourage more people to reach out to them and get more visibility into who was using their open source projectOn the other hand, they wanted to make sure that big companies building commercial platforms on top of Vendure’s platform are forced to pay for a commercial license. They also wanted to choose a less-permissive license, but something that was still well-known and wouldn’t cause a lot of confusion among users or potential customersThe difference between being happy with people using your software for free, and being happy with competitors using your software to build a competitive product, without offering any support to the underlying software. Do your customers care about whether you are VC-backed or bootstrapped? We had an interesting conversation about this, because Vendure is bootstrapped. I think we settled on a real important nugget — if your technology is really critical to the company, they will care about your long-term sustainability. Being bootstrapped can help convince potential customers that you are independent and will be sustainable for the long term. The top advantage of open source, David says, is the ability to get fast product feedback from a community. —> I just was talking with someone yesterday about this advantage of an open source strategy, I think it is under-discussed but extremely important. If you’re the founder of an open source company struggling with your product strategy — uncertain how to differentiate between project or product or how to differentiate the entire company in the ecosystem; don’t know what your project is supposed to do for your business; aren’t clear on the target market for your project or product — you might want to work with me. Find out more here.

2 Loka 202440min

Suosittua kategoriassa Liike-elämä ja talous

sijotuskasti
mimmit-sijoittaa
psykopodiaa-podcast
puheenaihe
rss-rahapodi
ostan-asuntoja-podcast
pomojen-suusta
rss-startup-ministerio
rss-lahtijat
rss-rahamania
rahapuhetta
rss-neuvottelija-sami-miettinen
kasvun-kipuja
rss-h-asselmoilanen
rss-turvacast
taloudellinen-mielenrauha
leadcast
syo-nuku-saasta
muutosakatemia-coaching-podcast
lakicast