This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
There are a few qualities that differentiate average from high performing softwareengineering 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. I highly recommend his writing on the topic.
The official definition of DevOps is “a softwareengineeringculture and practice, that aims at unifying software development and software operation.” The concept of Site Reliability Engineer (SRE) has been around since 2003, making it even older than DevOps. The Differences Between DevOps and SREs.
I’ve spent the last decade building and operating large-scale production systems with all sorts of teams, in all sorts of environments. Over the last few years, I’ve tried to find ways of making better, more operable systems. Someone who can work in both softwareengineering and automation. Fostering Human Processes.
This post was written by Stig Brautaset, CircleCI Senior SoftwareEngineer, in collaboration with Cian Synnott, CircleCI Senior Staff SoftwareEngineer. Retrospectives are a well-established resource in the software and systemsengineering toolbox. What is a personal retrospective? What went badly?
The charter (aka what site reliability engineers should care about). Take a long-term, holistic view of the system. Adapt work so that people feel comfortable and confident running our systems, propagate good practices, and ensure we do these things sustainably. Lead incident practices. Provide tools and assistance.
He describes “some surprising theories about softwareengineering”: 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 softwareengineers manual work, their first instinct is to automate it.
In the context of software development, particularly with observability 1.0’s s favorite three buzzwords (logs, metrics, and traces), we can draw several analogies to understand software development and debugging. In software, bugs and unforeseen issues represent this remainder.
Any significant shift in an organization’s softwareengineeringculture has the potential to feel tectonic, and observability (o11y for short)—or more specifically, Observability Driven Development —is no different. At Honeycomb, we work to build functionalities to enable you to be the best systems “detective” you can be.
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. It therefore feels like a more adequate fit to our function.
But to give credit where it’s due: it’s natural for startup founders to look for ways to get more out of their team, and yet it doesn’t seem to be as natural to recognize successes by granting new titles and roles. A knack for systems thinking, paired with equal interest in both human & technological systems.
The challenge The working members of your CoPE face a daunting challenge: By joining, they agree to the task of modifying a complex, adaptive system which is subject to financial, human, legal, and other constraints that have placed it in a locally optimal position. For the organization, things are going pretty well, all things considered.
Softwareengineer. As a rule, a softwareengineer uses coding skills to develop and design software solutions that meet the project’s requirements. A QA engineer usually collaborates with a product manager to make sure all the quality standards are met throughout the product life cycle.
It’s great to have your endorphins rise when you make a split second decision while driving, but not so great when you’re collaborating with others or triaging a potentially complex systems problem. At Honeycomb? The same process takes maybe an hour. Q: What are some bad habits you had to unlearn from other companies?
Softwareengineering productivity cant be measured. The old career ladder emphasized understanding advanced technologies and building complex systems. The new one emphasizes teamwork, peer leadership, ownership, and XP engineering skills such as test-driven development, refactoring, and simple design. So I told the truth.
That’s fascinating because it touches on so much of what you know and I’ve been in softwareengineering for a couple of decades now, a couple of days, decades, but sounds like couple of days. Yoz: There are some kinds of failure that you’re not going to know about because they don’t involve system failure.
It's about paying attention to the minutiae that, when combined, create a robust and reliable system. Outdated dependencies can expose your application to known security vulnerabilities, potentially compromising your system's integrity. They may also lack performance improvements or bug fixes that could benefit your project.
We organize all of the trending information in your field so you don't have to. Join 49,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content