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. Those people are your influencers.
Astro , a startup helping companies to build and manage developer teams with talent from Latin America, today exited from stealth with $13 million in Series A funding contributed by Greycroft with participation by Obvious Ventures and other unnamed investors. based tech companies. million by 2030.
As a softwareengineer or individual contributor, the next step in your career can be to become a principal engineer. The path to becoming a principal engineer at companies can feel unclear, which can inhibit individual engineering careers.
Softwareengineering productivity cant be measured. Our company is fully remote, so he invited me to come to his house next time I was in his city so we could discuss it face-to-face. But our company is relatively small. the FAANG companies. for most companies. So I told the truth. Lets dig in.
At its essence, a DevOps culture involves closer collaboration and a shared responsibility between development and operations for the products they create and maintain. This helps companies align their people, processes, and tools toward a more unified customer focus.
And indeed, in most companies we can see that there’s a requirement for just one of these positions, with an overlap in responsibilities and abilities. The differences and lack of communication between these teams often impacted the product, which in return affected the end users and company. Companies want to move faster than before.
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 softwareengineering teams. We’ll never lose sight of what it means to build a tool that, in turn, streamlines processes and enriches engineeringcultures.
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.
Our engineeringculture embodies the essence of open source, and it’s a small contribution to the community ? As hackathons are becoming increasingly popular, companies and organizers are coming up with many out-of-the-box ideas for swags. by Anagaha, SoftwareEngineer from Suki).
Someone who can work in both softwareengineering and automation. I put “engineer” in scare quotes because as a Canadian who is not certified as an engineer, I can’t advertise myself as such even though that was my role for a U.S. company whose career ladder I do not control. .
How will you make sure engineers adopt the tool successfully? How will you measure and communicate the ROI, including outside of your immediate team and to leaders around the company? Rework Rework or refactoring is probably the category most associated with “tech debt” in softwareengineering.
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. What is a personal retrospective?
Today’s article is about the role of a Principal Engineer as many people still have doubts who is this person and what is his/her responsibilities in a company. Here I would like to share with you the outcomes of the “Path to Principal: Defining the Modern Principal Engineer” panel discussion that I had a chance to attend.
It seems every week there is an article or blog post decrying the lack of women and people of color in softwareengineering, or on the other side defending the gap. At LaunchDarkly I have experienced similar intellectual honesty, one of the many facets of our outstanding engineeringculture. Diversity Theatre.
Dhevi joined Netflix in July 2020 and is one of many Data Engineers who have onboarded remotely during the pandemic. In this post, Dhevi talks about her passion for data engineering and taking on a new role during the pandemic. One great thing about working with data is the impact you can create as an engineer.
The charter (aka what site reliability engineers should care about). In most companies, it feels like all SREs will fill in a role that more or less fits these categories: Own the reliability roadmap. It is intended to be a living document that we can modify as we see fit, but so far it hasn’t changed too much. I’ll share it here. .
.* I understand why: the stakes for public comment become higher as you move up the ladder, every social media post has the potential to be interpreted as a subtweet or request, and your highest-priority work is often deeply entangled with confidential company and personnel matters.
finding good softwareengineers takes so long and requires so much effort… but it doesn’t have to. If you like the ideas in the post, then why not come and join me at Navico and help us to build a highly-innovative engineeringculture and a brilliant place to work. to be an elite tech company?—?for
Nick Travaglini, Senior Technical Customer Success Manager at Honeycomb, captures this evolution well: “The engineering landscape has evolved from a focus on technical hurdles to a broader emphasis on team coordination and collaboration. See how Pax8 transformed to an engineeringculture of curiosity with observability 2.0.
An optimal Developer Experience will depend a lot on the company the developer is working for. This article discusses why and when changes to developer needs will occur, how to get ahead of them, and how to adapt when these changes are necessary.
According to Deloitte research of 2022, 83 percent of “digitally maturing” companies reported using cross-functional teams. 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.
This is your host Sachin and today I have with me Sergey Fedorov, The Director of Engineering at Netflix. As you all know, Netflix is a media services provider and a production company that most of us have been binge-watching content on for while now. Welcome, Sergey! We’re delighted to have you as a guest on our podcast today.
He then grabs our attention by telling us the scale of the opportunity (and a bit of name-dropping): When Intel wants to build a billion-dollar factory, they need a loan that is too big for any single lending company to take on, so the lenders form a syndicate that pools its resources to support a facility.
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. Along with the title question, we also asked about their prior companies, how we differ, and what surprised them most about working here. This time, we asked!
Interview with Samuel Setegne Samuel Setegne This post is part of our “Data Engineers of Netflix” interview series, where our very own data engineers talk about their journeys to Data Engineering @ Netflix. Samuel Setegne is a Senior SoftwareEngineer on the Core Data Science and Engineering team.
But as the engineering manager there, I grew a team from zero. A team of me to a team of about somewhere between 20 and 25 softwareengineers. All focused on trying to level up Indeed’s front end engineering capabilities. A company called Fresh Books. And I think every company is trying to do that too.
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. Everything’s running great and you get bought by a company and they’re like, “What’s your process?”
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.
While helpful in pinpointing known-unknowns, it impeded the team’s ability to explore the workings of the software, particularly in uncovering unknown-unknowns. It also fell short in supporting an engineeringculture of ownership and curiosity within the organization, exacerbated by the pricing model.
If every company is a technology company, then every healthy company must have a healthy relationship to technology. We hope that their answers will help companies to build their own strategies for digital transformation. We asked the CTOs how the companies prepared themselves for both old and new vulnerabilities.
One of the great things about editing all of our deep-dive EC-1 startup profiles is that you start to notice patterns across successful companies. While origin stories and trajectories can vary widely, the best companies seem to come from similar places and are conceived around very peculiar themes. for 10 months.
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.” Early in my career, I had the experience of working for a company where everything felt broken but it wasn’t clear why.
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