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. Softwareengineering 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?
Codereview is a key step during the software development process — it’s when people check a program by viewing and reading parts of the source code. But despite its importance, not all developers are pleased with the way traditional codereviews work. Image Credits: Codacy.
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. The option to see how the same prompt would result in results si de by si de using different mo de ls is very helpful when you are trying to integrate AI into your own software.
In less than a year after raising $25 million in Series B funding , technical assessment company CodeSignal announced a $50 million in Series C funding to offer new features for its platform that helps companies make data-driven hiring decisions to find and test engineering talent. This round brings CodeSignal’s total fundraising to $87.5
There are a few qualities that differentiate average from high performing softwareengineering organisations. I believe that attitude towards the design of code and architecture is one of them. In orgs where it’s all about delivering tickets as quickly as possible or obsessing over technology, the culture and results are poorer.
InnerSource can be defined as the application of open-source software development principles within an organization’s internal software development processes. It draws on the valuable lessons learned from open-source projects and adapts them to the context of how companies create software internally. What is InnerSource?
It’s well-established that there’s a severe shortage of experienced software developers. In a February poll by Infragistics, more than half (53%) of software developers and IT professionals said that the biggest challenge this year will be recruiting developers with the right skills. million by 2030.
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 systems engineering toolbox. Let’s Talk Engineering is always such a pleasure to attend.
The path of a softwareengineer is one of constant learning. Before joining CircleCI, my years of experience led me to believe that I was an engineer with a firm understanding of the technical aspects of the craft, as well as what is considered good practice. We learn things from concepts and processes to languages and tools.
When you think of software testing, what comes up first? Both software testing methods are vital to writing and maintaining a high-quality production codebase. Both functional and non-functional testing are crucial components of a comprehensive software testing process , building extra confidence at each application layer.
Even if you’ve never heard the term “innersource” to describe how teams build their software, you’ll probably still recognize some of the principles behind it. They’re powering code at the world’s most influential companies, and they might even be important practices on your team. Innersource isn’t a novel concept.
Definition of Done – a team needs to agree that executing these tests is part of delivering changes and when changing code, new tests should be added. principles of testing (popularized by the book Clean Code by Robert C Martin ). From a process perspective, you should aim to ensure they are executed before the code is merged.
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.
Using common software, functionalities can be purchased and integrated with the click of a button and the availability of a credit card. No long debates with other engineers about the envisioned solution. Value-stream teams have been given more autonomy and possibilities to select, purchase and integrate hardware and software.
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). Develop software and write fixes to help improve the reliability of our systems in order to let engineers focus on their primary tasks.
I’ve got a ton of personal reasons for joining Honeycomb that may not be worth being all public about, but after thinking for a while, I realized that many of the things I personally found interesting could point towards attitudes that result in better software elsewhere. Someone who can work in both softwareengineering and automation.
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.
The rollercoaster of 2020 highlighted the competitive advantage that well-oiled software delivery teams provide. 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. Think of Amazon’s Two Pizza Rule.
Using common software, functionalities can be purchased and integrated with the click of a button and the availability of a credit card. No long debates with other engineers about the envisioned solution. Value-stream teams have been given more autonomy and possibilities to select, purchase and integrate hardware and software.
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.
Getting Stuff Done Days (GSDD) is an initiative used by many top companies to improve the quality of the software development and boost a proactive, continuous improvement-based engineeringculture in their organizations. Take time to review the existing work and refactor properly if needed. Excellence. Productivity.
The overall theme is high-performing engineering teams are generally the ones that humanize the process. Whether you’re trying to increase productivity or release better-quality code, the biggest piece of advice is to lead with empathy. . Fostering a healthy engineeringculture. Engineering Manager, Slack . “It’s
If you have been in a scrum team (or even an agile software development team), you most certainly have had or heard about sprint retrospectives or gone through them. They often happen after the team showcases the work done during the sprint reviews or demos. The original intent behind retrospectives is to help the team […].
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. developers do, because it’s the things you interact with every day. Team: Growth.
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.
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.
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. To do this effectively, we need a culture of confidence around the code that we take to production. Formatting and linting.
From rolling out major product additions like CircleCI Insights and private orbs , along with educational resources like our developer hub and State of Software Delivery Report that includes the first CI/CD benchmarks for high-performing engineering teams, it seems like every day there is something new to look forward to.
Is it any surprise that studies are showing 83% of software developers are feeling burnout? That was certainly the case at Slack where releases were delayed due to a high rate (50%) of flaky tests. Deploying observable code is simply less stressful/risky because teams will know quickly if there are any issues.
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.
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. This is why we highly encourage all teams to instrument their code to emit telemetry data. .
My purpose as a Developer Advocate is to help software teams with their work, and that work can have positive ripple effects. We’ve doubled the size of the company this year, with growth on all fronts: engineering, product, design, marketing, sales. Engineering. No Q4 code freezes for us. no oversharing or prying).
For example, in a cross-functional team that is working on a new product development, one member may be actually responsible for market research while the others work on coding, testing and product’s implementation, etc. For example, the UX designer may closely work with the developer to ensure the software’s interface is user-friendly.
My purpose as a Developer Advocate is to help software teams with their work, and that work can have positive ripple effects. We’ve doubled the size of the company this year, with growth on all fronts: engineering, product, design, marketing, sales. Engineering. No Q4 code freezes for us. no oversharing or prying).
That graph should represent social relations which can be enriched with information about normal engineering practices that each person and their team perform, such as periodic sprint cycles, regular post-incident meetings, or widely adopted standards and tools. Making a change requires people who will advocate for that change.
Mapping out your business’s domain landscape has many benefits: knowledge sharing, generating product ideas, providing the foundation for software architecture, aligning on requirements, but a common challenge is… “where do we start?” business, software, teams), it’s discovery structure. Q: What if the high-level structure is wrong?
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. It takes a village.
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 did a bunch of stuff at different code paths.
Look for software with features like skills assessments, robust candidate profiles, and integrations that allow for background checks. Evaluate software features: Candidate sourcing and management: Does it allow you to tap into diverse talent pools and manage candidate relationships effectively?
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.
Lean was introduced to software a couple of decades ago. The Nature of Software “Do not go where the path may lead, go instead where there is no path and leave a trail” -- Ralph Waldo Emerson It’s May 27, 1997. I show that these models derive from opposing assumptions about the nature of the software-debugging task.
tool, Pax8 faced hurdles in fostering a culture of ownership and curiosity due to user-based pricing limitations and an impending steep price increase. Pax8’s platform engineering team was keen on modernizing the company’s cloud commerce platform, but they were hitting obstacles with their traditional observability 1.0
Charity once said an off-hand sentence that became a mantra for my transition into the VP of Engineering role: “Directors run the company.” My priority number one had been to “run engineering well.” A successful startup engineering team has to say no to tantalizing opportunities constantly. Now it had to be something else.
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