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 software engineering 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.
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. EngineeringCulture that focuses on building Quality and Simplicity – build a ContinuousDelivery pipeline that allows teams to deliver value independently of one another.
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.)
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.
As time passed the number of developers more than tripled, the breadth and depth of our use cases expanded, and our scale increased more than tenfold, the monolithic architecture significantly slowed down the delivery of new features. Delivery?—?A Productivity?—?Local
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. EngineeringCulture that focuses on building Quality and Simplicity - build a ContinuousDelivery pipeline that allows teams to deliver value independently of one another.
To me, this story is what DDD is really about: developing the design mindset of a modeller to drive product innovation and enable continuousdelivery of value, involving frequent collaboration with domain experts. It’s the Share Pie story in chapter 8 of Eric Evans’ DDD book.
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