Remove Engineering Culture Remove Metrics Remove Open Source Remove Systems Review
article thumbnail

5 Ways to Increase Release Velocity with Observability

Honeycomb

Observability provides the ability to see inside your complex and distributed systems to know exactly what’s happening in real time. That was certainly the case at Slack where releases were delayed due to a high rate (50%) of flaky tests. Also, Honeycomb and the open source framework OpenTelemetry (OTel) are truly better together.

article thumbnail

Shipping Node.js at Netlify

Netlify

services: the Netlify CLI , the build system and the serverless function bundler are just a few examples. Despite the sheer number of repositories we maintain, and especially considering that some of them are open-source projects with daily contributions from the community, you might be surprised to learn that our team is relatively small.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

What it’s like to be a backend engineer at Netlify

Netlify

When we talk with engineering candidates, it’s pretty easy to explain what our frontend and Node.js But did you know that a big chunk of Netlify’s engineering team is in the backend? As an engineer based in the EMEA (Europe, Middle East, Africa), I usually start my work day earlier than folks in the Pacific time zone.

article thumbnail

Chaos Engineering at Datadog

LaunchDarkly

The goal was to simulate a loss of a system so that they could build this adaptive environment, so that they didn’t really have to worry about resiliency as much. This is near and dear to us and so we want to make sure that we’re building resilient systems. Then finally, we’re looking at the distributed systems.

article thumbnail

Grown-Up Lean

LeanEssays

I then make a sustained argument from the Linux experience for the proposition that “Given enough eyeballs, all bugs are shallow”, suggest productive analogies with other self-correcting systems of selfish agents, and conclude with some exploration of the implications of this insight for the future of software.