Remove Culture Remove Engineering Culture Remove Examples Remove Weak Development Team
article thumbnail

Nurturing Design in Your Software Engineering Culture

Strategic Tech

In my experience, the culture is better and the results are better in orgs where engineers and architects obsess over the design of code and architecture. In orgs where it’s all about delivering tickets as quickly as possible or obsessing over technology, the culture and results are poorer. My experience is the opposite.

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

A guide to personal retrospectives in engineering

CircleCI

Ourselves: to remind us what we’ve done, and to create an opportunity to reflect on how things have developed since. Our team(s): to give them a broader view of our work, to demonstrate openness about the highs and lows of being a software engineer, and to encourage a growth mindset. Who are personal retrospectives for?

article thumbnail

Turning Domain Discovery into Product and Organizational Improvements with a DDD Exemplar

Strategic Tech

A DDD Exemplar is a project, ideally achievable within a quarter, that results in improvements in a domain(s) and improvements in how teams build products. It lays the foundations for other teams to copy and adapt. It’s a proof-of-concept for how teams build products. Why Thing Get Stuck After Discovery?

article thumbnail

Platform Engineering Essentials: 5 Key Learnings Before You Start

Xebia

Platform engineering can help organizations reduce cognitive load for development teams, and create a significant improvement in developer experience (DevEx) as well as several other areas. Test that the capabilities you want to deliver are actually desired by the teams. Build a pl atform b ased on an actual need.

article thumbnail

Panel Discussion: Teams, Processes, and Practices in DevOps

LaunchDarkly

At the November Test in Production Meetup in San Francisco, LaunchDarkly’s Yoz Grahame (a Developer Advocate) moderated a panel discussion featuring Larry Lancaster, Founder and CTO at Zebrium, and Ramin Khatibi, a Site Reliability Engineer (SRE) and infrastructure consultant. So, I guess I’m a bad expert on process.

article thumbnail

Leading Remote and Distributed Engineering Teams – Top Takeaways from the Panel

Gitprime

Leaders of distributed engineering teams shouldn’t have to work up solutions to these problems from scratch. So we held a panel discussion with three of today’s top engineering leaders to discuss approaches and lessons learned in building, growing, and maintaining remote and distributed teams.