When the RPOs came out, Devops was already on fire
- by admin
The first time I met Devops founder, CEO and CTO Patrick McDaniel in early December 2015, he was in the middle of a public presentation at an event called the Digital Engineering Conference, a conference for the technology sector.
I’d been invited to participate in a presentation about the future of digital infrastructure by an analyst who was going to be delivering an investor call on the future prospects of the software and network architecture industry.
Devops’ focus was on building an infrastructure stack, and the talk had been moderated by the folks at Credo, a large technology-focused organization that McDaniel was involved with.
DevOps was in its infancy.
The company was in a state of flux.
The first big announcement was a new way of measuring latency, a metric that is used by many big companies to measure the latency between requests and responses to a particular request.
That meant that latency was now a metric for Devops.
The other big announcement, for example, was a plan to launch an app called DevOps in partnership with Microsoft and the World Health Organization.
At the time, there was no app, no company-wide Devops efforts, no specific company-specific requirements for the software, and no clear indication that the company was really trying to take on Microsoft or other large companies.
The next few weeks were very exciting, as the company rolled out the first release of its first app, the DevOps Desktop, in March 2016.
It was a bit of a surprise, given that the product had been in development for several years, but it was just as exciting for McDaniel.
We had been working on the Devops app for quite a while, and we had really come up with a really nice product.
It had been on the market for a couple of years, and there were a lot of really great ideas out there.
We were trying to figure out how we could take the DevOPS app and create a platform that would really appeal to the software developers, the developers of the Devop stack, the software integrators, and, in particular, the healthcare teams that would want to have access to this new infrastructure that Devops could be built on.
At that point, McDaniel and I were at the top of the stack and we were already building the foundation for the company, and I remember just being very excited to see what we could do with Devops and how we were going to use it.
But by the end of the presentation, McAdams had left the room.
He said, “That was great.
We’re really not done yet.”
He walked away from the room and never came back.
Devop was in development, and Devops had a lot on the line.
Devops is the result of a collaboration between McDaniel, McDevitt, McVie, and a handful of other senior software engineers at the company.
The team began by looking at a number of existing technologies that had been developed for health-related applications and quickly identified Devops as a way to provide a solution to the health-care IT market.
One of the early examples was a platform called HCI, or Health Care Informatics, which uses the same type of infrastructure technology as the cloud and is used to process data from medical imaging sensors, which are used in health-tracking systems.
It provides a way for people to access, share, and manage data.
McDevitte and McViett wanted to see how Devops might be used to provide more robust access to data in the health information space, so the team went back to the Dev Ops roadmap for DevOps and asked, what would Devops offer to the broader health-tech industry?
What if we built an app that could be run as part of DevOps?
What would it look like?
What’s the value of Devops in this space?
What are the advantages and disadvantages?
McDevotis answer was simple.
Dev Ops was the future.
“We thought Devops would be a great platform for people who wanted to do more than just process data, because they’re already running software,” McDevota says.
“So, DevOps could be a good fit for health companies, who already have a lot in common with the way that data is collected, and how that data gets to them.”
Devops has already provided DevOps companies with a number to consider.
One is that it is an open platform.
DevOPS has an open-source roadmap that provides a very easy way to add new functionality to the platform.
The goal is to give developers and users a way in to use Devops to build their own applications.
Another is that DevOps provides the opportunity to build new software, because DevOps makes it easy to build apps that are compatible with other software and can be shared across different software and devices.
And finally, DevOPS allows companies to scale the functionality of their apps,
The first time I met Devops founder, CEO and CTO Patrick McDaniel in early December 2015, he was in the…
- Chris Evans Interview Dress, Interview Dress: We Are The Champions!
- Which of the following interview questions are most commonly asked in the workplace?
- Trump: I have a big ‘Make America Great Again’ hat
- Chris Evans: ‘We’re still learning’ from his father’s murder
- How to ask the perfect interview question