The Developers focus, the Team quickens
The developers are focused, the team is fast managing development projects to place more importance than the mere creation of value by the people who write, iterate and deliver the code. This is not always the case, and sometimes a junior developer can feel like they are a forgotten asset, an opinion that has no merit. However, the C-suite’s focus on longer-term strategies can sometimes lead to an overemphasis on processes and governance rather than building actual code. And that’s a problem. This problem is not limited to software houses or development groups. False middle layers of management are likely to be found in public and private organizations around the world, and these layers often indicate an excessive focus on planning and management. Isn’t it time for companies whose lives depend on the quality of their software output to focus more on leading developers? In today’s competitive IT environment, skilled developers are a resource that is not cheap, nor is top talent readily available. Maximizing the value of the development organization should be at the top of priorities for the business to operate at maximum efficiency. If you ask many developers about efficiency and productivity, the people in charge may be surprised. Developers say they spend just 11.5 hours a week, which equates to about 40% of their time coding new features and improvements. The rest of the week is spent on non-coding activities such as maintaining internal tools, setting up pipelines and automation, waiting for CI pipelines to start, waiting for builds and tests, or setting up the development environment. When you add third-party solution integration into the mix, such as database, security, API management, developer productivity time is much shorter. In short, there are many other activities, too numerous to list, that are necessary to create working applications. Creating modular developer workspaces allows developers to focus on just a few tasks to achieve a specific set of results, knowing that aspects of the project such as networking, database accounts, and security are managed by complementary microservices. Recently, we’ve seen an explosion of developer-focused content tools, from BASH scripts that sandbox content to IDE/editor plugins that help spin up content. The problem is that few tools eliminate much of the content-specific complexity required to deploy production-ready Kubernetes. Fortunately, a commitment to innovation is at the heart of everything we do at SUSE, and our solutions help developers meet the challenges of content deployment and developer productivity.