The first question at the end is why are architecture and development teams separated? One answer is that some architects can't write software. I've worked with some very good architects who cannot write code. But the best of both worlds is to be a coding architect.
It's a bit naive to assume all developers are accepting even when you present them with the facts. Some just don't want any changes to occur because they're scared. They're scared that if they can't learn this new way of work they'll be out of a job. Somehow these people are the most trusted senior developers in the company and it'll be really difficult to get the rest onboard. I also don't understand why we still feel like architects live in their own corners, while developers are working away. Architects should be embedded in teams, or work with multiple teams daily, so they are a part of the development.
It really made me happy when heard 2000 users as where errors arise! My first SaaS handled that much user with no difficulty
The first question at the end is why are architecture and development teams separated? One answer is that some architects can't write software. I've worked with some very good architects who cannot write code. But the best of both worlds is to be a coding architect.
25:00 does "Test-Driven Architecture" exist yet? 😄
It's a bit naive to assume all developers are accepting even when you present them with the facts. Some just don't want any changes to occur because they're scared. They're scared that if they can't learn this new way of work they'll be out of a job. Somehow these people are the most trusted senior developers in the company and it'll be really difficult to get the rest onboard.
I also don't understand why we still feel like architects live in their own corners, while developers are working away. Architects should be embedded in teams, or work with multiple teams daily, so they are a part of the development.
cool