Jonathan Saring Podcast Transcript
Jonathan Saring joins host Brian Thomas on The Digital Executive Podcast.
Welcome to Coruzant Technologies, home of the Digital Executive podcast.
Brian Thomas: Welcome to the Digital Executive. Today’s guest is Jonathan Saring. Jonathan Saring is the co-founder of Bit, a cutting edge platform that redefines software development through composability and ai. With a commitment to building the future of enterprise technology, Jonathan has successfully led bit to become a vital resource for over 250,000 developers and countless Fortune 100 brands.
His role as an advisory board member for multiple startups in the RD space, along with his experience as an angel investor, positions him as a thought leader in the tech community.
Well, good afternoon, Jonathan. Welcome to the show.
Jonathan Saring: Thank you, Brian, and thank you for having me here today.
Brian Thomas: Absolutely. I appreciate it, my friend. We’re doing a podcast internationally today. I’m in Kansas City in the United States, and you are in Tel Aviv, Israel, which is always fun. Jonathan, I’m gonna jump into your first question.
Bit has become a go-to platform for over 250,000 developers. What gap in the software development world did you see that inspired you to build this?
Jonathan Saring: So I think that the, the most basic reason that we set out on this journey was that software development today is just playing hard. It’s complex and it gets worse as you scale it and as more technologies emerge and the needs of the products that people build for their customers are getting more and more complex, and the speed of delivery required today from organizations.
Even small organizations, let alone enterprises, becomes very challenging in the way that we develop software today and today. Many teams need to deliver more applications, more user experiences, more features, and they need to do it faster. They need to do it more efficiently. They need to cut down time to market, and at the same time, they have to ensure that the.
Quality of the software that they’re creating is of the highest standard, and that the experience is consistent across every application, feature or touch point that they build for users. And that is incredibly hard today. And the reason that it is incredibly hard is that the tools and the infrastructures that we use were built for projects.
If you think about it, everything that we use today to build software, the basic foundations, the way that we build software is all about projects. If you look at GIT or CICD products and so on, when an organization, for example, needs to build, you know, hundreds or thousands of features. And compose them into a huge number of applications and experiences and trying to build them and deliver them in projects and maintain them in projects becomes closer to impossible as you scale.
And that pain, that underlying problem or gap, is becoming painful in more and more areas of software development and eventually impacts the end experience of users. But Composability solves all of that. So the basic idea was that instead of building, you know, these software silos, which in turn build organizational silos, we can lean into composability and build software in components.
Build modular software, build software where you can build features, you can build applications, you can build complex backend functionalities, and you can turn them into building blocks into pieces of Lego for the organization or for, for everyone you wanna share it with. And you can use them to build anything you want.
That was not possible. When we started this journey, and I think that the pain is so great that even if you are, you know, just encountering a very specific instance of it. For example, we’re trying to make the design consist the UI consistent across the organization. Or we’re trying to improve the speed of delivery of a new feature.
Or for example, how do we make sure that we can create a feature that all our applications will use and we can easily, you know, update everyone with changes? And those kind of problems led more and more people to seek solutions that will allow them to build differently. And building differently means building composable.
So our goal was to build the tools. That will let, and I’m talking pre AI era developers build and organizations and teams build composable software together. And basically that’s, that was the major change. That was the major shift. And I think that the market was, I. The industry, the people building software, were actually not only ready for it, they already begun this process.
If you look at organizations today, you see a lot of APIs, for example, which are the interface of composable design and are by definition, reusable. And something that many different entities in the organization can can work with. And you see libraries and packages that now consist according to latest report, 60 to 70% of the average organizational code base.
You see microservices in the backend. You see components in the front end. So the technology itself was already leaning into composability. There was just no tooling, no platform or infrastructure that will allow this form of software development. I think this is where bit came in because we were the ones that said, okay guys, it’s okay.
The pains that you’re feeling are real, and now let’s try to think differently and solve them by not creating them in the first place. Let’s build with Lego. That was the main thing. We see a variety of use cases for companies to start with, and now when AI comes into the game, I think that the combination of AI and composability.
Is an exponential game changer for the way that we build software.
Brian Thomas: Thank you so much. I appreciate that, Jonathan. I loved how you talked about this idea of being more agile using modular type applications with composable design to really scale, be more efficient. Still have the quality and just be faster at that development.
So I appreciate that, Jonathan. Jumping into your next question here, if you could briefly share, you’ve been vocal about composability being the future of software. Can you break down that composable software really means and why it matters so much right now?
Jonathan Saring: Yes. Thank you Brian. That’s a great question.
So why, right now, I’ll give you a practical example. I’m a big fan and I’ve heard that you’ve, you’ve been working on technology infrastructure for the health industry before, am I right? Correct. Correct. Alright, so I remember that one of the first, today on the platform, you can find dozens of Fortune 100 companies from across all industries.
You can check the logos on our website, but you’ll see names like at and t and Red Bull and Moody’s, and many others. They’re pursuing the composable transformation. Gardner recently stated in one of the latest reports that organizations that will adopt composability and lean into it will outpace competition.
But 80% in the next five years, that’s already happening. And as we mentioned, that technology being built is already using API’s, libraries, and packages. And if I go back to the healthcare example, I remember one of the first enterprises to onboard. The composable development platform and use it practically and instantly after onboarding was one of Canada’s largest healthcare organization.
And there was a very smart architect that said, okay. He was asked by leadership to double the number of applications that the organization is going to deliver in that particular year, mainly due to the covid crisis, which transformed really accelerated digital transformation for healthcare organizations because they had to provide healthcare services through applications and digital interfaces, and so they had to double the number of applications.
Given the same resources and they had to cut down the price of the cost of developing each new application and had to make sure that everything is consistent and that everything is standardized and of the highest quality. And so that was at the time before bit, I think nearly an impossible task. And what they did was to embrace a different kind of thinking a little bit and try to think what are the experiences that they’re going to build?
And then they built all these experiences with bit as components as building blocks, and they used these components to compose all the applications that they needed. And one year later when they ran the study, they found that they delivered just a little in the first year alone, which means including building the components, which is a one-off investment, they are later reusable, so you don’t need to build them again.
You can iterate, compose, build new ones, but building all of these components from scratch. In that year, and they more than doubled the number of indications cut down by 60 something percent, the cost per app, and increased the consistency by over 80% basically because they were just reusing the same Lego piece everywhere, so they didn’t even have to work to make sure that it’s consistent.
So that’s a very strong, I think example of why now, of why the need now and today, more and more organizations are facing this exact need. So if we’re going back to technology, they’re already working and thinking composable. Everyone is trying to become compostable because it’s just, it makes more sense, right?
If you go into a car factory, you don’t see a team building my car and a team building Brian’s car and a team building Joe’s car or Deborah’s car. You see a team building with a domain ownership over a domain like wheels or engines or electricity or whatnot, and they’re building components and they’re serving them to the assembly line to the rest of the organization, which is a little bit like building microservices and serving API.
So software. This is much more efficient because it’s faster, it’s cheaper, it’s consistent. Delivery time is much faster. If you wanna update a component, the update goes to all of your products and software should be built the same way. And now the world has changed twice. Once because composability has become a simpler option.
It was hard. It was very hard before bit because you had to implement, you know, all kinds of stuff and your own solutions and integrate all these tools. And even then and now composability becomes a much simpler choice. You already have all these APIs and packages and libraries, and you already have all these features and you wanna build new ones.
Just build them like pieces of Lego, build them as components. So I think that this is the moment in time that we’re seeing this transformation already happening. And the second thing is that AI has dramatically changed the future and even the present. We’re already seeing a drastic impact on the present of software development, and I think that this future, this combination of composability and AI is going to radically change the way that we’re seeing software being developed by people from indie hackers to entrepreneurs all the way to the world’s largest.
Enterprises. I think that we are in that moment in time right now.
Brian Thomas: Thank you so much, Jonathan. I appreciate that and I love the example, of course, I’ve been in healthcare a lot of years, but you know the fact that you come into a large healthcare organization and cut down the cost by 60% while keeping the quality consistency at 80%, you doubled the apps.
You’re able to do this using composability or your platform bit, which is awesome. So thank you for sharing that. Jonathan, my next question for you, bit has gained traction with Fortune 100 companies. What are these large enterprise doing right or wrong when it comes to adopting composable and AI driven technologies?
Jonathan Saring: So Brian, I think this is maybe the most hardest question in the world. I think in our world right now of software development. How is AI going to change the way that we’re building software as people and as as organizations? So if we look at what’s happening today. We’re basically seeing two types of AI for software development, for building applications, or any type of software.
The first type is co-generation. I think Cursor is a great example. It’s an incredible product. Like once you try it, it’s very hard to go back to, uh, what you had before. It really helps you write more code faster, makes the process easier. It even makes it more fun. But at the same time, tools that help us generate code also create huge problems for the organizations.
Firstly, developers are now able to create a lot more code, so the number of re-implementation and duplications. Across your code base, and if we’re looking at a big organizations, you’re looking at hundreds of thousands of different products or projects, and now it becomes nearly impossible to track or maintain and update all of those AI generated instances.
Of functionalities of features across the code base, the rate in which the code base grows becomes exponential. So all these problems that we already had before composability are now becoming five times or 10 times or a hundred times worse. Because you’re creating more code. You’re creating the same code everywhere, and then you’re left with a huge code base that is largely AI generated, which also means that you’re not consistent and you are not sure about quality, about standards, even about which text you use.
Am I testing this React component with this testing technology or with another, what’s the standard of the organization? So it’s very easy. It becomes much easier to lose complete control over your code base, and it becomes more and more hard. Let’s imagine that you are using AI to create some feature payments.
A header yes. Something simple, right? For your applications, and now you have an unknown number that grows every day of implementations of this functionality across your code base. You don’t know where, and now you wanna make an update to all of them. Good luck. That’s just not going to happen. And the second type of AI for software development that we’re seeing is tools that let you build software or applications without coding.
This is now referred to as Vibe Coding, which I’m sure you’ve heard of. And everybody’s talking about that. And you’re seeing tool like Lovable and Bold and other tools that are now letting. Hopefully everyone use simple natural language to create applications, to add features, to add functionality, and the thing is that these vibe coding tools that we’re seeing today are not the solution that organizations need, or even a single entrepreneur that’s going to build a big company needs to build software with ai.
Not to write code, not to generate code, but to build software. First of all, the architecture, you know, you’re just getting, you’re really getting big one chunk of code. You’re not going to build the next Airbnb on top of that code. Secondly, you know, it does not build full real systems and applications.
You basically have no backend. Some tools offer pre-made integrations or. Make your own integration to databases such as Super base and others, but it does not have a real backend to it. So you are pretty much unable to build, you know, full blown platforms. You can’t really build a big company with these tools.
If you try to use them within an organization, they are completely out of context of the organization We talked about. The fact that the organization is already becoming composable. You have APIs, for example. These tools are completely unaware of the APIs that you have in your organizations. They cannot use them, access them.
You use them to, you know, write or get information. And so what you’re building is really kind of an isolated out of context prototype that is not part of the organization’s code base or system or technology. Lastly, the quality of code that they generate is not something that you can really, you know, use in production.
If you are a serious organization, you need very high coding standards. You need code that is tested, linked, documented, so on. And that is just not the case right now with the code. That is tools create. So that pretty much turns most of the tools into prototyping tools at best. Within organization. While I think the future holds a lot more for natural language, AI software development for organizations, the potential of what organizations and, you know, larger enterprises, even small startups, can do with this is a hundred times larger if we just build it right in the way that fit their needs.
That is what we’re doing at BIT right now. That is Hope ai, which I’ll maybe tell you a little bit more about nfte. We are working on building and we are already releasing in the next couple weeks, the first GA version of an AI that is composable. So the way that all of these problems are solved, it’s not by building, you know, a better ai.
Is by building an AI that builds composable software. And if you go to Hope AI on Bit Cloud a website, you can ask Hope Ai. Next week. You can ask Hope AI to build ready. Or to build booking.com and it will design a complete architecture for you. Bit can scan, if you are a big organization, you’ll need a five minute chat with us for that, but Bit will become familiar with all the existing APIs, packages, libraries in your organizations.
You can set your standards. It will create the feature or the application that you requested, and it’ll create an architecture that is composable. You don’t need pre-made integrations. You can write software, you can create new integrations inside and outside organization to internal or external tools on APIs.
The code quality is of the highest enterprise grade standards. It comes with test coverage, LinkedIn documentation, everything you need. It can be consumed in any way, each component into any project, and it can be shared with the rest of the organization, and it builds complete systems, including backend and everything.
So now everything changes. It because now, for example, the organization can, you can ask, even if you are a huge enterprise, right? And you want a new app, just ask for the app that you want in a single prompt, and it will reuse the components you already have. It will access. And use the APIs in your organization.
It’ll lay down an architecture that you can see and review before you build it for a composable design of the feature application that you want. And then it will build all the components for you. And it can even take your design, for example, and your visual language so you’re not limited even, you know it.
It comes down to stuff sometimes that is just. Simple as that, right? The design is not limited to some pre-built library that this specific tool chose to use. You can use your own design. You can ask for any design you want, and eventually you can start building new features, new applications, update existing one, and collaborate on your technology within the organization in context with the highest quality code, complex capabilities, backend, everything.
And it’s all being done essentially using natural language. So when AI meets composability, then we get a nuclear exposure in what becomes possible.
Brian Thomas: That’s awesome. Thank you for sharing. I appreciate you unpacking that and you did a breakout. Some of the issues today with having co-generation type software, right, like cursor, obviously you’ll end up having a lot more applications you need to manage.
It’ll be a headache. Also the big hype right now around vibe coding, right? No code, low code platforms like Lovable, et cetera. You’re not gonna be able to scale an enterprise company with that. Absolutely agree. Jonathan, looking ahead, what’s your boldest prediction about the future of software architecture or developer tooling?
Think that you’ll surprise people.
Jonathan Saring: I think that the role of developers and other professionals and executives and stakeholders in the organization are going to completely change, and that’s not a bad thing. We should not be worried. We should not be afraid on either side of this change. I think that ai, when it meets composable to composable technologies like Hope and Bit will let everyone become partners.
In this, uh, process of software development. So now we can literally build together. I can review your things, you can review my things, I can use your things, you can use my things. We can all share, we can become partners and a lot of the broken communications and the challenges of collaboration. Are going to go away.
This is going to be something that is much better for everyone and I think that we’re going to see it in two, three years from now. I think this is one of our personal aspirations and goals and bit, and we’re gonna make it happen. We’re all going to witness a change and everyone can be a builder, and that’s a good thing for everyone.
Brian Thomas: Awesome. Thank you so much. And I truly think that as well, the future is truly building together when we can leverage bit and composable software with ai. That’s just awesome. So thank you. I’d like to focus on the future and what’s emerging out there. Jonathan, it was such a pleasure having you on today, and I look forward to speaking with you real soon.
Jonathan Saring: It was my pleasure, Brian. Thank you for having me today.
Brian Thomas: Bye for now.
Jonathan Saring Podcast Transcript. Listen to the audio on the guest’s Podcast Page.
