Remove Architecture Remove Engineering Culture Remove Software Engineering Remove Weak Development Team
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

Observability for New Teams: Part 1

Honeycomb

Any significant shift in an organization’s software engineering culture has the potential to feel tectonic, and observability (o11y for short)—or more specifically, Observability Driven Development —is no different. This is why we highly encourage all teams to instrument their code to emit telemetry data. .

Insiders

Sign Up for our Newsletter

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

article thumbnail

The Rise of the Front-End Developer

LaunchDarkly

On May 21, for the Test in Production Meetup on Twitch , Yoz Grahame, Developer Advocate at LaunchDarkly, moderated a panel discussion featuring Rebecca Murphey, Senior Technical PM at Indeed, and Ben Vinegar, VP of Engineering at Sentry. Prior to taking on the tactical project manager role, I was in a senior engineering manager role.

article thumbnail

Grown-Up Lean

LeanEssays

He describes “some surprising theories about software engineering”: I discuss these theories in terms of two fundamentally different development styles, the "cathedral" model of most of the commercial world versus the "bazaar" model of the Linux world. However, the open source world figured out a better way to develop software.

article thumbnail

Technical Health Isn’t Optional

O'Reilly Media - Ideas

This proactive approach reflects an important shift from older reactive approaches to security, in which you deploy software and hope nothing bad happens. In a modern software architecture, a lot of the work will be performed by services that access other services, and each service needs its own identity and its own set of privileges.