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
Autonomy over Command and Control – without autonomy there is no learning, improvement, innovation or ability to adapt to changing circumstance. Alignment – instead of telling people what to do for both product features and product architecture, focus on getting teams to align to a common product goal.
Cloud-native architectures, fueled by large-scale workloads including big data and machine learning, are creating growing challenges for IT in the configuration and optimization of supporting infrastructure. At Hyperpilot, we witnessed these challenges in every public and private cloud customer we engaged.
When I joined Discover® Financial Services in 2021, the company was executing its Runway: Mission 80,000 Feet vision to transform the engineeringculture toward product-centricity. This has helped to empower the company’s technologists to create a single agile way of working, while allowing them to innovate faster, together.
Higher-level languages, automation, low-code and no-code development platforms, and better programming environments have been gradually reducing the need for IT staff to perform low-level, routine tasks for years so they can take on more innovative challenges. That might continue to work for a few rarified geniuses, he adds.
Are you aiming to improve Developer Velocity, as measured by the Developer Velocity Index (DVI) (1), which correlates with faster revenue growth, higher shareholder returns, increased innovation, and improved customer satisfaction? Alternatively, are you fostering a collaboration mindset, emphasizing knowledge sharing and collaboration?
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.
What I’m really doing is changing the engineeringculture at OpenSesame. Culture doesn’t change easily. OpenSesame had a pretty innovative approach to career development before I joined. It involved a spreadsheet where engineers would gather evidence of their skills. Bigger than a breadbox, anyway.
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 is a summary of the 2022 software trends podcast.
Another hurdle to decision making is when technology leaders feel that the skills needed to deliver big changes don’t exist within the organization like the lack of DDD, architecture, or cloud skills. Choosing where to focus is a balancing act: delivering new products, fixing legacy software, and improving engineeringculture.
Netflix’s engineeringculture is predicated on Freedom & Responsibility, the idea that everyone (and every team) at Netflix is entrusted with a core responsibility and they are free to operate with freedom to satisfy their mission. All these micro-services are currently operated in AWS cloud infrastructure.
Leaders must inspire their workforce to innovate and create change through encouraging ownership, trusting their teams, and displaying ethical, authentic, and cooperative behavior. We examined the current level of DevOps maturity across various dimensions, including collaboration tools, enterprise architecture, and organizational structure.
This should include asking questions like: What is the system architecture? Legacy applications create pain points because they hold the organization back from innovation in other technologies as well. This could include changes to the database’s software, architecture, data schema, or security practices. Considering new ideas.
As the company outgrew its traditional cathedral-style software architecture in the early 2000’s, the leadership team felt that the growing pains could be addressed with better communication between teams. In other words, a bazaar-style hardware architecture was vastly superior to a cathedral-style architecture.)
Autonomy over Command and Control - without autonomy there is no learning, improvement, innovation or ability to adapt to changing circumstance. Alignment - instead of telling people what to do for both product features and product architecture, focus on getting teams to align to a common product goal. Database, Business Logic, UI).
For instance, if I feel that a design of an application or a pipeline would benefit from new technology or architecture, I have the freedom to explore and innovate without excessive red tape. Typically in large corporations, you’re tied to strict and redundant processes, causing a lot of fatigue for engineers.
To me, this story is what DDD is really about: developing the design mindset of a modeller to drive product innovation and enable continuous delivery of value, involving frequent collaboration with domain experts. Innovation is inventing new ideas, new domain concepts, and new domain terminology.
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). The goal is to strike a balance between staying up-to-date and maintaining stability in your project.
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