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
People showed up with some of the things they run into, and often, it took us a few minutes to help them out and unblock them on their technical challenges. 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.
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.
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.
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. It didn’t name any specific technology, nor did it necessarily ask for any specific prior titles or education.
Looking at the current technological and organizational paradigm, we can only recognize the world is massively different from 10 or 20 years ago. Gone are the days of making well-thought documents who are reviewed and tested by colleagues in the organization. Do you have the capabilities and time to guide the technical decisions?
Looking at the current technological and organizational paradigm, we can only recognize the world is massively different from 10 or 20 years ago. Gone are the days of making well-thought documents who are reviewed and tested by colleagues in the organization. Do you have the capabilities and time to guide the technical decisions?
The official definition of DevOps is “a software engineeringculture and practice, that aims at unifying software development and software operation.” This can lead to frustration, a set back in deployment and high costs due to delays. So why did Google need to create its own definition? The Differences Between DevOps and SREs.
While I have a lot of strong opinions on how to best bring automation to engineering teams, it’s clear that the most advanced, powerful automation tools need one crucial element to succeed: people. For businesses, the first phase of the pandemic was about systems: updating and building your tech stack so you could operate as fully remote.
VPs of Engineering often have a lot of influence over both company culture and policy, and the decisions our companies make ripple outside of the companies themselves. The whole tech industry would benefit from more perspectives in this role. Working across the stack.
I then make a sustained argument from the Linux experience for the proposition that “Given enough eyeballs, all bugs are shallow”, suggest productive analogies with other self-correcting systems of selfish agents, and conclude with some exploration of the implications of this insight for the future of software.
At Netlify, we use a diverse set of technologies, languages and paradigms to build our product. services: the Netlify CLI , the build system and the serverless function bundler are just a few examples. operating system and Node/npm versions). Along with Ruby, Go, Rust and others, we write quite a bit of JavaScript.
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? As an engineer based in the EMEA (Europe, Middle East, Africa), I usually start my work day earlier than folks in the Pacific time zone.
There’s also a wonderful culture of documenting everything in living documents, so it’s easier to find things if I have questions. R : Multiple people have mentioned to me that it feels like they are able to start healing their scars from other tech companies when coming here. Q: What was the biggest surprise? At Honeycomb?
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. Technical context: cloud instance specifics, region/availability zone, etc. Investigation best practices.
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. The technical writer creates technical documentation that describes the product’s functionality, usage, and so on. Software engineer. Foster open communication among all team members.
Given that I couldnt give my CEO what he wanted without creating dysfunction in engineering, what could I give him? The CEO, chief product officer, chief technical officer, and I met a month later. I said, If we had the best product engineering organization in the world, what would it look like? This is a big cultural shift!
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. As the longer time you spend in it, the more you realize how much more it is about people than about technology. Maybe yes, maybe no.
The goal was to simulate a loss of a system so that they could build this adaptive environment, so that they didn’t really have to worry about resiliency as much. This is near and dear to us and so we want to make sure that we’re building resilient systems. This still technically runs but it’s on its way out.
Industry and specialization: Specific industries may have their own preferred platforms or require niche features, such as technical skill assessments or industry-specific job boards. Applicant tracking system (ATS): Manage applications efficiently, track candidate progress through the hiring pipeline, and organize communication.
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.
In March I wrote the following: Observability is a paradigm on which we can build a safe, healthy, sustainable future for the tech industry. A better tech industry is better for supporting this complex, interdependent society we live in. Though our deploy velocity remained the same, the engineering org has been far from stagnant.
In March I wrote the following: Observability is a paradigm on which we can build a safe, healthy, sustainable future for the tech industry. A better tech industry is better for supporting this complex, interdependent society we live in. Though our deploy velocity remained the same, the engineering org has been far from stagnant.
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