IBM Developer Blog

Follow the latest happenings with IBM Developer and stay in the know.

Get your developers onboarded quickly with minimal disruption

We hear from many clients that developer productivity and efficiency continue to be pain points. Cloud adoption can help normalize developer experiences across application stacks and runtimes. The path and steps for your developers to push code should be clear, simple, and easy to implement, even on Day 1.

The modern developer experience provides a unified and normalized practice with modern tools. Developers thrive in the inner loop where unit tests and code come together, and in a penalty-free runtime execution environment where no one gets hurt, no processes take down precious workloads, and no one knows that it took 20 minutes to resolve that pesky runtime error. The inner loop occurs in a developer workspace that is easy to set up, manage, prepare, maintain, and, more importantly, easy to allocate. If a new developer is added to your squad, they can have all of the mechanical things they need to push code changes into the pipeline on their first day.

An important part of the modern developer experience is expressed as Red Hat CodeReady Workspaces, which provides a set of constructs to provision a developer workspace in the cloud where they can perform their inner loop. A save action to a workspace file initiates an inner loop build in their local workspace, and an endpoint for the developer to see their changes quickly.

Trained as developers, we know there is a bit of religion with dev tools, especially an integrated development environment. Sometimes, it’s like telling a cowboy what hat to wear. Did we just hear you clinch your teeth? Giving a developer the ability to iterate through their inner loop locally goes a long way. Red Hat CodeReady Containers is a way to take an optimized Red Hat OpenShift instance with one node and run it locally on a developer workstation. Of course, you can also run your inner loop with a local container engine on your workstation without CodeReady Containers. You have options.

To complement the inner loop is the ability to have a curated set of application stacks that a developer can consume. Application stacks serve as a way to standardize runtimes, runtime versions, references to curated images, and things like default paths. By using open contributions from Kabanero, you can apply a unified governance to application stacks. What does all this mean? You can focus on what you do best, which is code.

Want to see what the modern developer experience looks like? Watch our interactive test drive of CodeReady Workspaces, CodeReady Containers, and Kabanero, and how they all work together in the following demand video webinar.