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. 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.
What I’m really doing is changing the engineeringculture at OpenSesame. Culture doesn’t change easily. I’m hoping this will help direct people to new behaviors, which will in turn start to change the engineeringculture. Associate SoftwareEngineers Associate SoftwareEngineer 1s are at the start of their career.
PDF) Culture Changes The purpose of the new career ladder is to help change the engineeringculture at OpenSesame. Just as the ladder sets new expectations of engineers, the management track sets new expectations for managers, with material about managing the system rather than just managing the work.
DevOps teams work autonomously and embrace a softwareengineeringculture, workflow, and toolset that elevates operational requirements to the same level of importance as architecture, design and development. It involves cultivating multidisciplinary teams who take accountability for the entire lifecycle of a product.
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. Better solutions for modern architectures. I can’t wait to build the future of softwareengineering with all of you.
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.
In a modern softwarearchitecture, a lot of the work will be performed by services that access other services, and each service needs its own identity and its own set of privileges. Similarly, Tim Hope said that open source is critical in building an engineeringculture and developing systems. What Is Technical Health?
What are some of those key design and architecture philosophies that engineers at Netflix follow to handle such a scale in terms of network acceleration, as well as content delivery? And for me, the big part of the success of growth was actually a step above the pure engineeringarchitecture. Makes sense.
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.
VPs of Engineering from frontend backgrounds are relatively rare, and it’s partly because the most pressing technical challenges a startup faces are often around scaling, reliability, and backend architecture.
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.
Softwareengineers are not typists who translate requirements into software. Softwareengineers contribute to designing the products and features they are building. I hope you also enjoyed my highlights, but I would still recommend reading the whole story in the book.
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. How do you lay out architecture and things? Well, one, if you count me I guess.
Documenting decisions Keeping a record of why certain technical decisions were made can provide crucial context for future development, ideally through Architecture Decision Records (ADRs) or Request for Comments (RFCs). However, true engineering excellence lies in the art of doing small things really well.
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