Remove Culture Remove Document Remove Engineering Culture Remove Systems Review
article thumbnail

Thoughts on organizing architecture

Xebia

Gone are the days of making well-thought documents who are reviewed and tested by colleagues in the organization. The character and way of working of the architect function has a huge impact on the engineering culture. Clearly this benefits the speed of delivery and flexibility in choosing solutions.

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. . The charter (aka what site reliability engineers should care about). I’ll share it here. .

Insiders

Sign Up for our Newsletter

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

article thumbnail

Thoughts on organizing architecture

Xebia

Gone are the days of making well-thought documents who are reviewed and tested by colleagues in the organization. The character and way of working of the architect function has a huge impact on the engineering culture. Clearly this benefits the speed of delivery and flexibility in choosing solutions. Code test. <?php

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? Who are personal retrospectives for?

article thumbnail

How We Define SRE Work, as a Team

Honeycomb

It is a living document after all! But looking at the responsibilities we were taking around vendor negotiations, voluntarily cross-pollinating silos and impacting engineering teams roadmaps in anticipation of scaling needs, we decided to rework that whole category into a broader “system-level” perspective. What changed?

article thumbnail

Functional vs non-functional software testing

CircleCI

Unit tests for an API application might make requests against the system deployed in a testing environment and compare the responses against documentation. Many healthy engineering cultures avoid relying heavily on user acceptance testing due to its unreliability, cost, and time consumption. Integration testing.

article thumbnail

Engineers New to Honeycomb, What Did You First Notice About How We Do Things Here?

Honeycomb

There’s also a strong debugging culture. There’s also a wonderful culture of documenting everything in living documents, so it’s easier to find things if I have questions. We’re hiring across many departments (just so happens we have spots for new engineers, too)! The energy is infectious. At Honeycomb?