Remove Engineering Culture Remove Organization Remove Software Engineering Remove Software Review
article thumbnail

Nurturing Design in Your Software Engineering Culture

Strategic Tech

There are a few qualities that differentiate average from high performing software engineering organisations. I believe that attitude towards the design of code and architecture is one of them. In orgs where it’s all about delivering tickets as quickly as possible or obsessing over technology, the culture and results are poorer.

article thumbnail

Transforming to an Engineering Culture of Curiosity With a Modern Observability 2.0 Solution

Honeycomb

tool, Pax8 faced hurdles in fostering a culture of ownership and curiosity due to user-based pricing limitations and an impending steep price increase. Pax8’s platform engineering team was keen on modernizing the company’s cloud commerce platform, but they were hitting obstacles with their traditional observability 1.0

Insiders

Sign Up for our Newsletter

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

article thumbnail

Simulation Theory, Observability, and Modern Software Practices

Honeycomb

In the context of software development, particularly with observability 1.0’s s favorite three buzzwords (logs, metrics, and traces), we can draw several analogies to understand software development and debugging. In software, bugs and unforeseen issues represent this remainder.

article thumbnail

On Not Being a Cog in the Machine

Honeycomb

I’ve got a ton of personal reasons for joining Honeycomb that may not be worth being all public about, but after thinking for a while, I realized that many of the things I personally found interesting could point towards attitudes that result in better software elsewhere. Someone who can work in both software engineering and automation.

article thumbnail

DevOps vs. SRE: What’s the Difference Between Them, and Which One Are You?

OverOps

The official definition of DevOps is “a software engineering culture and practice, that aims at unifying software development and software operation.” The concept of Site Reliability Engineer (SRE) has been around since 2003, making it even older than DevOps. JVM State: Threads, environment variables.

DevOps 145
article thumbnail

A guide to personal retrospectives in engineering

CircleCI

This post was written by Stig Brautaset, CircleCI Senior Software Engineer, in collaboration with Cian Synnott, CircleCI Senior Staff Software Engineer. Retrospectives are a well-established resource in the software and systems engineering toolbox. What is a personal retrospective? What went badly?

article thumbnail

How We Define SRE Work

Honeycomb

I had shared my initial experiences and impressions in this post and thought it would make sense to check back in now that I’ve had the opportunity to spend time learning about the team, the culture, and the code base more in depth. . Lead and influence practices in the organization that lead to greater operational experiences.