Remove Culture Remove Engineering Culture Remove Performance 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. 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. So we need to make it part of everything we do.

article thumbnail

Astro emerges from stealth to connect Latin American developers with US tech companies

TechCrunch

Astro , a startup helping companies to build and manage developer teams with talent from Latin America, today exited from stealth with $13 million in Series A funding contributed by Greycroft with participation by Obvious Ventures and other unnamed investors. million by 2030. based tech companies.

Insiders

Sign Up for our Newsletter

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

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. .

article thumbnail

Functional vs non-functional software testing

CircleCI

For many developers, unit tests and integration tests are often top of mind. Your team’s testing practice should assess the entire application, observe the larger story of how it operates when functioning correctly, and raise alarms when deviations are found. It can quickly consume your team’s engineering bandwidth.

article thumbnail

DevOps

The Programmer's Paradox

I was working for a big company that had a strong vibrant engineering culture. The different teams were scattered all over the planet, so coordinating all of the efforts was vital. When we were happy with how our code was performing, we’d give the code to the QA group. We were doing very complex, low-level work.

DevOps 45
article thumbnail

A guide to personal retrospectives in engineering

CircleCI

Assessing our own performance as individual engineers - and telling the story of that performance to our colleagues - is difficult, and gets harder as we grow in our careers. Taking a relatively formal, personal system with us from role to role “frees” us from local performance management systems. What went badly?

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.