Page with SmartSlider3

This page is using SmartSlider3 – its slower than Homepage custom slider (transition effects can be the same in 95% cases), we use Swiper for most of our work – we say one slider to rule them all , because one JS slider can create Sliders, Carousels with custom transitions, effects and looks.

“It worked in staging!” says the dev team. And the ops team replies: “it must be a code issue.”

Accordion

Development

Developers and ops people sometimes have different perspectives on why a deployment went wrong. Was it the code? Or the infrastructure? In the end, it’s the user that suffers, and that user doesn’t care about why your product was broken. They just want it to work, so they can do their work.
It really did work in staging

Everyone on the team wants to get things right the first time, deploying a quality product with every feature release. That’s why development teams adhere to deployment best practices. They write tests. They write code. They test that code in staging environments that mimic the production environments that code will run in… as closely as possible.

Sometimes humans miss things

A slightly different network configuration here, an older version of a PHP extension or NPM module there, and suddenly the places where code is being tested before launching it to the world aren’t quite perfectly in sync. And the code that ran fine in QA falls down in production.

It gets worse when teams meet bottlenecks. For example, a limited set of environments, or worse, a single staging environment that code has to pass through. Who hasn’t done a ‘hotfix’ to resolve a critical problem in prod (without the same testing process we’d normally use) because we couldn’t wait to send it through QA or staging environment in use by others?

It really was a code change

• Or maybe it was a different version of the XYZ mo
• Though software development has come a long way
• Though software development has come a long way
• Or maybe it was a different version of the XYZ mo
• Though software development has come a long way
• Though software development has come a long way

SHORT: Text + Image

Text + Image

LONG: How to drive DevOps alignment

Eingebettet in die vom Gletscher geformte Landschaft entstehen fünf Einfamilienhäuser, sechs Doppelhäuser und ein Mehrfamilienhaus mit sechs Mietwohnungen. Zwei Einstellhallen bieten Platz für Insgesamt 26 Fahrzeuge

LONG: It really was a code change

Developers are measured by the features they ship. Ops is measured by uptime and performance. The most important person, the user, doesn’t differentiate between who’s at fault if the product/site/service/experience you’re offering them falls short of their expectations.

How do we solve for the user’s concern and deliver features they want, and reliability they expect?

Aktuelle

How to drive DevOps alignment

It’s time to stop working in silos

Development and ops need to take a unified approach to managing change. The scripts and tools that manage infrastructure should be subject to the same process and rigor, and managed as a system, instead of independent parts.

Video Elegant

At a glance, you should be able to tell when a version of a runtime was updated, or an application code update was made.

Showcase
How do we solve for the user’s concern and deliver features they want, and reliability they expect?

Showcase

Gallery

Downloads

At a glance, you should be able to tell when a version of a runtime was updated, or an application code update was made.

Team