Some commentary on a recent survey commissioned from my work, VMware. Unsurprisingly, open source is used by almost everyone. When it comes to what I care about software development, open source is indispensable. In fact, it’s hard to imagine a developer who only uses closed source software, if not whole systems like kubernetes or Cloud Foundry for running their applications. It’d almost be impossible. And, indeed, in our State of the Software Supply Chain survey this year, 2022, 90% of respondents said they were using open source in production.
Here'sa short write-up of the developer toil survey the Tanzu Labs people use to find ways to improve developer experience. If you like it, be sure to checkout the white paper we published on the topic, which includes a starter set of survey questions.
[www.youtube.com/watch](https://www.youtube.com/watch?v=3u31D00mIII) If you're doing anything with programming, apps, or the software you build and use to run your organization, check out the sessions we have at VMware Explore 2022, coming up August 29th to September 1st. (It's the new name for VMworld, same conference, though.) Browse the content catalog, and register if you're interested.
https://www.youtube.com/watch?v=tD5KXh36Svg&list=PLAdzTan_eSPRNuA52_34wh5VTBC-0Rz7U&index=4 Overly ambitious aspirations often fail. Scale back your digital transformation dreams to starts small, learn, grow, repeat. Transcript 06 - Big Bang Releases The sixth reason why changing, how you do software at large organizations usually fails: doing way too much at once, the big bang release. Oftentimes, when you're changing, how you do software at a large organization, you wanna have a big successful release. You've got a lot to change hundreds, if not thousands of teams, and you're investing a lot of time and money and attention from a corporate perspective.
https://www.youtube.com/watch?v=eMyeHiUzH3E&list=PLAdzTan_eSPRNuA52_34wh5VTBC-0Rz7U&index=4 Don’t have real CI/CD in place? Check out the Tanzu Application Platform. Transcript 05 - No CI/CD 14 reasons why your digital transformation strategy probably will go poorly: the fifth reason. You probably don't have true continuous integration and continuous deployment in place. What this means is that you're not only automating the way that you build your software, that you test your software, that you even make the images or the package of the software to be deployed continuous integration.
We've restarted the Tanzu Talk podcast. Check out this week's episode: Tanzu Talk is back! Your new hosts are Coté, Ed, and Ben. In this episode we cover recent news in the cloud native world, plus highlights from the recent Tanzu Application Release. Plus, light discussion of the political climate in Star Trek versus Star Wars as it represents programming philosophy. So far, the format is to cover some cloud native news and then talk about a larger topic.
https://www.youtube.com/watch?v=9x069fTpdi0&list=PLAdzTan_eSPRNuA52_34wh5VTBC-0Rz7U&index=5 Platform Engineering, platform as a product, and so forth. If you’re standing up kubernetes or any cloud stuff for developers, you probably need to change how you think about operations in general. Shift from service delivery to product management. Read more about setting up a platform engineering team. Transcript 14 reasons why your digital transformation initiatives to get better at software may be slowing down. Number four. Often what you do when you're fixing up how you do software in a large organization you're putting a platform in place.
https://www.youtube.com/watch?v=qr1w4Dp5tSA&list=PLAdzTan_eSPRNuA52_34wh5VTBC-0Rz7U&index=6 Figure out where to get started with a developer toil audit. Transcript 14 reasons why your digital transformation is stalling in a large organization: number three. If you're looking to improve the way that you do your custom software in a large organization, you likely have a huge amount of what people call tech debt or legacy software. These are the systems you're currently using that have brought you all the success and revenue that you have, and now they're too old and they really can't be changed.
https://www.youtube.com/watch?v=FIN2lVklWlc&list=PLAdzTan_eSPRNuA52_34wh5VTBC-0Rz7U&index=7 Read more in my free book. Transcript 02 - Security 14 reasons digital ,transformation fails in large organizations: number two security. There's many things your security staff is gonna wanna do when it comes to making sure the software you build and run is secure. One, they're gonna need to build up a risk profile to understand the new technology you're using the deployment frequency, all the types of risks that can occur.
The charitable guidance on what “shift left” means is: operations and security people working closer with developers, being friendly with them, and vice-versa. More or less it’s that lean idea of “move the decisions closer to where the work is actually done.” The phrase has gotten blown up to mean more than the original DevOps think (have developers put in work to make their apps run better in production, and have ops people work with developers to do so) to mean any activity that’s working closer with “developers” rather than in some waterfall-like, impersonal process before or after developers.