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
It was September 2023, my CEO was asking me a question, and my position as Vice President of Engineering was less than three months old. Software engineering productivity cant be measured. This is a talk about what you do, as VP of Engineering, when somebody asks for the impossible. How are you measuring productivity?
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. I highly recommend his writing on the topic.
This post was written by Stig Brautaset, CircleCI Senior Software Engineer, in collaboration with Cian Synnott, CircleCI Senior Staff Software Engineer. Retrospectives are a well-established resource in the software and systemsengineering toolbox. Let’s Talk Engineering is always such a pleasure to attend.
Test automation is not a project or a one-off—it is part of the development lifecycle and should be seen as its own system that needs to evolve over time as the requirements and system under test change and mature. Delivery pipelines and source code management systems help—for example, you can gate pull requests on a failing test.
It is great to be among so many talented people who know all the nuts and bolts of GitHub and work closely with GitHub engineers on new and existing features. These edits are applied directly in the editor, and you can quickly review them in the full context of the surrounding code. It also provi de s a way to auto-fix comments.
This post is part of a short series about my experience in the VP of Engineering role at Honeycomb. In February of 2020, I was promoted from Director of Engineering to Honeycomb’s first VP of Engineering. Not the plan I didn’t join Honeycomb with the goal of becoming an engineering executive.
At the time of writing this post, I have officially been at Honeycomb for one year as a site reliability engineer (SRE). The charter (aka what site reliability engineers should care about). Take a long-term, holistic view of the system. How site reliability engineers shape their work. I’ll share it here. .
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 software engineering and automation. is pivotal.
The official definition of DevOps is “a software engineeringculture 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. So why did Google need to create its own definition?
No long debates with other engineers about the envisioned solution. Gone are the days of making well-thought documents who are reviewed and tested by colleagues in the organization. Architects should be dynamic, understanding the purpose of management with the organization and the engineering challenges of the development teams.
No long debates with other engineers about the envisioned solution. Gone are the days of making well-thought documents who are reviewed and tested by colleagues in the organization. Architects should be dynamic, understanding the purpose of management with the organization and the engineering challenges of the development teams.
The overall theme is high-performing engineering teams are generally the ones that humanize the process. Fostering a healthy engineeringculture. Engineering Manager, Slack . “It’s It’s hard to have one piece of practical advice because a team of engineers is a living, breathing entity. “It’s
How do you turn complicated, far-flung systems like our widely-distributed system of humans into teams? As engineering leaders, we’re like the mortar between the bricks: We connect structures, teams, and people. And after all this growth, we were running into challenges around evolving our engineeringculture.
Unit tests for an API application might make requests against the system deployed in a testing environment and compare the responses against documentation. Many healthy engineeringcultures avoid relying heavily on user acceptance testing due to its unreliability, cost, and time consumption. Integration testing.
When we talk with engineering candidates, it’s pretty easy to explain what our frontend and Node.js But did you know that a big chunk of Netlify’s engineering team is in the backend? Meet some of our backend engineers… Bryan Mikaelian. There are lots of experienced engineers to learn from. Team: Growth.
The minute COVID-19 hit and everyone had to become not just remote-first, but remote-only, many engineering teams were forced to reckon with the number of manual processes they had in place. For businesses, the first phase of the pandemic was about systems: updating and building your tech stack so you could operate as fully remote.
Corey Bertram, VP of Infrastructure & SRE at Datadog spoke about how his organization does chaos engineering. He shared his experiences from when he led the SRE team at Netflix, and how thats influenced the way he’s helped the Datadog team put process around chaos engineering experiments. We’re pretty good.
We’ve wondered, in the past, what new engineers think about how we do things at Honeycomb. Meet Elliott and Reid, two of our engineers that recently hit their 90 day mark. What’s your name, how long have you been here, and what do you do, as an engineer? See our open positions, learn more about our culture, and apply today.
The SRE team is now four engineers and a manager. 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.
By implementing gamification, managers can extrinsically motivate employees (for example, with point/reward systems) without touching the hard controls within an organization. Within many organizations, initiatives are started but not completed due to people losing motivation to take the last steps. Progress bars.
services: the Netlify CLI , the build system and the serverless function bundler are just a few examples. These are built on three key principles: Automation : By automating recurring tasks whenever possible, we reduce the margin for human error and free up our engineers to focus on the right things. All flavors of it.
These new terms can help us have more nuanced, meaningful discussions by freeing us from associations with the old system. This failure is partly due to a discrepancy between what people say and what people do. The goal is to change how we change into a more organic, bottom up process. . THE MODERNIST APPROACH. Managers Know Best.
Observability provides the ability to see inside your complex and distributed systems to know exactly what’s happening in real time. That was certainly the case at Slack where releases were delayed due to a high rate (50%) of flaky tests. Observability is more than a platform: it’s a culture shift.
The real vs. simulated systems In Baudrillard’s terms, the authentic experiences and the real have been replaced by symbols and signs ( logs , metrics , traces ). In software development, the real can be seen as the initial design and requirement specifications—the ideal system as imagined by its creators.
This normalized parenting in a way I’ve never experienced in a job before: one point from today's incident review "what went well" section: > [employee] felt empowered to say "I'm parenting" and not step into the incident. Engineering. no oversharing or prying). So many wins in 2020.
Any significant shift in an organization’s software engineeringculture has the potential to feel tectonic, and observability (o11y for short)—or more specifically, Observability Driven Development —is no different. Your systems will naturally grow in complexity and scale, and so should your observability tool’s ability to track it.
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.
This normalized parenting in a way I’ve never experienced in a job before: one point from today's incident review "what went well" section: > [employee] felt empowered to say "I'm parenting" and not step into the incident. Engineering. no oversharing or prying). So many wins in 2020.
Our People (HR) team creates a Clubhouse ticket (project management software) that assigns tasks and due dates for everything ranging from granting the employee system access with IT to giving them branded swag to booking all their core meetings. From all of this, we’ve learned a lot about how we can improve our internal systems.
Step 1: Find the Value Exchange In Escaping the Build Trap , Melissa Perri talks about the system of value exchange. Step 2: People, Personas, and Roles A system of value creation and exchange involves people, each with their own purpose, responsibilities, and jobs to be done.
In the meantime, a developer can work with a QA engineer to identify and fix the bugs or issues that pop up during testing. Software engineer. As a rule, a software engineer uses coding skills to develop and design software solutions that meet the project’s requirements. Quality assurance engineer.
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. I guess is what I would say. That’s great.
Applicant tracking system (ATS): Manage applications efficiently, track candidate progress through the hiring pipeline, and organize communication. Applicant tracking system (ATS): Look for features that streamline resume screening, interview scheduling, and offer management.
While reading the book, I had an interesting realisation that doing small things really well can also lead to engineering excellence. What is engineering excellence? Engineering excellence, in the context of software development, is the relentless pursuit of quality, efficiency, and effectiveness in every aspect of our work.
Data Engineers were tempted by the pressure of the moment to give up on testing all together. Nevertheless, Data Engineers started to suffer from repetitive work, having to wait for the data to be loaded, or for the output to be validated. In many cases, these tasks ended up on the shoulders of the Data Engineers themselves.
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. Furthermore, no interactions or data exchanges were allowed except through API’s.
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