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
As a software engineer 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. By Ben Linders, Joy Ebertz, Pablo Fredrikson, Charlotte de Jong Schouwenburg
Staff engineers can influence behaviors during and after incidents by modeling transparency and questioning assumptions to strengthen engineeringculture. In retrospectives, staff engineers can improved model root cause analysis to improve underlying cultural issues.
In this article, Tariq King describes the metaverse concept, discusses its key engineering challenges and quality concerns, and then walks through recent technological advances in AI and software testing that are helping to mitigate these challenges.
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. An optimal Developer Experience will depend a lot on the company the developer is working for.
The article explores optimizing test execution, saving machine resources, and reducing feedback time to developers. Test suites may be computationally expensive, compete with each other for available hardware, or simply be so large as to cause considerable delay until their results are available. By Gregor Endler, Marco Achtziger.
For engineering leaders, the Great Resignation has made it clear that maintaining employee satisfaction should be a top priority in the coming year. By Lilac Mohr.
Machine learning is a powerful new tool, but how does it fit in your agile development? Developing ML with agile has a few challenges that new teams coming up in the space need to be prepared for - from new roles like Data Scientists to concerns in reproducibility and dependency management. By Jay Palat.
This article is a summary of the 2022 software trends podcast. 2022 was another year of significant technological innovations and trends in the software industry and communities. The InfoQ podcast co-hosts met last month to discuss the major trends from 2022, and what to watch in 2023.
This article presents how to use data science to detect wastes and impediments, and concepts and related information that help teams to figure out the root cause of impediments they struggle to get rid of.
There’s an increasing concern about the energy use and corresponding carbon emissions of generative AI models. And while the concerns may be overhyped, they still require attention, especially as generative AI becomes integrated into our modern life.
In the summer of 2021, we published an article on preventing developer burnout and tech culture’s historical tendency to glamorize being “so busy.” Mental health is at the forefront of everyone’s radar, and Allstack is here for it. But our interest in the topic is more than a passing trend.
Have you ever wondered about systems based on machine learning? In those cases, testing takes a backseat. And even if testing is done, it’s done mostly by developers itself. A tester’s role is not clearly portrayed. Testers usually struggle to understand ML-based systems and explore what contributions they can make.
Arjan kept asking me for an article for the XPRT. The last topic I would like to address is our main theme for the upcoming period: Creating EngineeringCultures for our Customer. Asking for Xpirit-feedback during a dry-run is also one of the things I try to motivate new colleagues for. magazine and was persistent.
Establishing SRE in a software delivery organization typically requires a socio-technical transformation. Operations teams need to learn how to provide a scalable SRE infrastructure to enable development teams to run their services efficiently.
Chander Damodaran of Brillio noted that, “the culture of sharing solutions, frameworks, and industry-leading practices” has been a crucial part of Brillio’s journey. Similarly, Tim Hope said that open source is critical in building an engineeringculture and developing systems. That’s an important statement.
Promoting InnerSource cultivates a culture of openness and transparency, resonating throughout the organization and enhancing company culture and employee morale. Summary This article explores InnerSource, a practice that brings open-source principles to internal software development within organizations.
This article delves into enriching the collaboration topic by emerging the contextual systems and the need to find the purpose underneath the context. Putting the pieces together needs collaboration to create a shared understanding of what the purpose of the domain is. Because of that, I decided to write about it and explain it more deeply.
This article helps you challenge your automated testing and to improve upon it in a more continuous fashion. . Either tests do not provide enough confidence or companies take a very traditional approach, resulting in releases either introducing substantial risks or becoming costly.
In this article I will discuss the pros and provide a few questions you should ask before implementing it. In her 2017 OSCON presentation , Netflix’s Dianne Marsh describes the Paved Road as ‘ A concept, formalizing a set of expectations and commitments between the centralized teams and our engineering customers ’.
Choosing where to focus is a balancing act: delivering new products, fixing legacy software, and improving engineeringculture. In Reality… I’m not advocating that you follow every step in this article in order and propose a DDD exemplar.
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.
In this article I would like to show you what I learned while building that Slack bot. You can find more information in the Verifying requests from Slack article. At this location there is only a limited number of parking spots, and we want to avoid colleagues arriving at the office with their car without an available spot to park.
It seems every week there is an article or blog post decrying the lack of women and people of color in software engineering, 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.
This article described how I came up with the charter for the SRE team, which we bootstrapped right around then. The SRE team is now four engineers and a manager. I recently wrote an article about how we manage incident response at Honeycomb , and I’d love for you to read that too. Last year, I wrote How We Define SRE Work.
A Cosmos service This article will explain why we built Cosmos, how it works and share some of the things we have learned along the way. Background The Media Cloud Engineering and Encoding Technologies teams at Netflix jointly operate a system to process incoming media files from our partners and studios to make them playable on all devices.
Interested in reading more about engineering management? Read my article on Becoming a VP of Engineering. Sometimes, using a label that speaks directly to the business value of a type of work can do wonders to help both sides find a way to move forward. The post Anything But Tech Debt appeared first on Honeycomb.
In this article, I’ll do a deep dive on some of these processes and tools, how we use them and why they help us. They are a fundamental piece in our engineeringculture, since they give us the confidence we need to ship to production often with a lower risk of introducing regressions. Project templates. Automated tests.
Check out my presentations and articles. Perhaps the most important aspect of discovery is embedding it in your culture and making it a continuous activity for leaders and for makers. Unfortunately, making continuous design & discovery part of your engineeringculture cannot be achieved in a single workshop.
I landed deep in the heart of a reasonable engineeringculture. It took them a long time to go from alchemy to engineering. The article said that software also started as an art, and has some scientific basis, but it will eventually follow the same path to engineering. Early on I moved away from the cowboys.
Whether you are a team lead, product manager, or a chief product officer , this article will give you the insights you need to leverage the power of cross-cultural collaboration in your company. Get to know more about the Spotify engineeringculture. What is a сross-functional team?
In the Harvard Business Review article “Building the AI-Powered Organization”, [16] Tim Fountaine, Brian McCarthy, and Tamim Saleh contend that a successful move to digital involves aligning a company’s culture, structure, and ways of working. They create an engaging engineeringculture. They obsess over customers.
Software engineering productivity cant be measured. Martin Fowler wrote an article in 2003 titled Cannot Measure Productivity. Theres more details here than I can explain today, but you can use the QR code to find a detailed article, including the documentation we use for the skills. This is a big cultural shift!
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