Free your developers! The simple way to rebalance your DevOps resources

Christopher Lockheardt
Christopher Lockheardt
Senior Content Manager
14 Jan 2021

Many organizations find their resources for creating and improving their products being siphoned off by the need to maintain their products. They’re seeing their developers—in whom they invested a considerable amount of time and money finding, hiring, and training—spending less and less time doing the jobs the organization brought them on to do.

ActiveState’s 2019 developer survey revealed that 60 percent of developers devote fewer than four hours a day writing code. This loss has become an accelerating trend: in 2018, only 50 percent of developers reported spending fewer than four hours a day coding. What tasks are eating into those hours? A survey by Tidelift and The New Stack also conducted in 2019 found that 35 percent of a developer’s day is spent dealing with code maintenance, testing, and security issues.

Shift the balance of power back to dev

Oxbow Labs is a small team of web developers,” explains Winn Jewett, founder and lead web architect of the web dev studio based in Colorado Springs. “We’re not system administrators or hard-core DevOps experts, so keeping a whole suite of websites operational can be a challenge.”

Entrepreneurs like Jewett are driven by a vision to bring new customer solutions to the marketplace. They didn’t build their digital agencies with the idea of becoming glorified IT administrators. But that’s often the position businesses find themselves in once they have a stable of clients using their products. So they go looking in the marketplace for a solution. That’s where they discover Platform-as-a-Service (PaaS).

By partnering with a PaaS provider like Platform.sh, organizations gain access to a cloud computing platform where they can develop, run, and manage their websites and applications while the provider maintains the platform infrastructure. A PaaS can also provide automation tools that further lessen the maintenance burdens on developers. With a PaaS, the balance of power shifts back from Ops to Dev.

More time, more money, more tools

“Over time, the Pixelant team found itself spending more time managing infrastructure than building new features,” says Mathias Bolt Lesniak, in-house TYPO3 consultant for digital agency Pixelant. “[With a PaaS,] our developers don’t have to think about setting up databases, copying data over, and all those kinds of things. That makes it possible to really work specifically on development.”

Freed from tending to infrastructure such as servers and databases, organizations like Pixelant find themselves with more time and money with which to develop and deliver applications. This spike in resources helps them improve current products and create new ones, getting both to market faster. A PaaS also gains them access to all the languages, operating systems, and databases supported by the PaaS infrastructure. This lets them use the tools that are best suited to each project and best understood by each development team.

If you’d like to learn more about how a PaaS offers a much better return on your DevOps investment, come talk to us.