Remove AWS Remove Culture Remove Engineering Culture Remove Software Engineering
article thumbnail

The Future of Observability is Bright as Honeycomb Announces $50M in Series D Funding

Honeycomb

The future of observability has never been more exciting, and this latest round ensures we can continue to invest—with conviction—in improving the lives of software engineering teams. Engineering teams are recognizing observability as a distinct and emerging practice, and are hungry for a truly differentiated product like Honeycomb.

article thumbnail

Technical Health Isn’t Optional

O'Reilly Media - Ideas

Open Source and a Culture of Sharing. The rise of open source software in the 1990s has undoubtedly transformed IT. While vendor lock-in is still a very real issue, the availability of open source software has done a lot to liberate IT. Remember: an attacker only needs to find one vulnerability that escaped your attention.

Insiders

Sign Up for our Newsletter

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

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. If you give software engineers manual work, their first instinct is to automate it.

article thumbnail

Cross-Functional Teams in Product Development: Definition, Principles and Examples

Altexsoft

For this, companies need to carefully design their teams, set clear goals and processes, and cultivate the culture of mutual trust and communication between employees with different expertise. Software engineer. For instance, one chapter can consist of software engineers or designers. Increased employee engagement.

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. We have a tight relationship with AWS, but we don’t throw stuff over the wall—we try very hard to understand the different aspects of our complex infrastructure. There’s also a wonderful culture of documenting everything in living documents, so it’s easier to find things if I have questions.

article thumbnail

Panel Discussion: Teams, Processes, and Practices in DevOps

LaunchDarkly

That’s fascinating because it touches on so much of what you know and I’ve been in software engineering for a couple of decades now, a couple of days, decades, but sounds like couple of days. Like you need tools that respect that responsibility, that respect your time. I guess is what I would say. That’s great.