Skip to main content

Everyone should be an architect

In the world of software development, the role of the architect often looms large. Yet, what if I told you that architecture is not just the domain of a select few, but rather the responsibility of every member on the team?

Let's delve into why this shift in perspective is crucial for the success of your projects.

Gone are the days when software architecture was solely the concern of a designated architect. In today's landscape, it's imperative that every team member, from developers to testers, possesses a solid understanding of the architectural principles guiding their work.

As an architect, your primary aim should be to ensure that everyone comprehends the architecture as thoroughly as you do. Each member should be equipped to answer the fundamental "why" questions about the architecture, breaking down barriers that often lead to miscommunication and inefficiency.

Too often, we see organizations where the architect stands as the solitary guardian of the system's architecture. This isolation not only stifles collaboration but also hinders the development team's ability to fully grasp the architectural vision.

The result?

Ivory tower architects struggling to bridge the gap between their ideas and the practical realities faced by developers.


Imagine a scenario where every developer possesses architecture skills. Communication becomes streamlined, with team members adeptly navigating discussions around architecture models and design decisions. They're empowered to align their work with overarching architectural goals, making informed choices that uphold the desired quality attributes of the system.

Furthermore, developers, being intimately familiar with the codebase, serve as invaluable sources of insight for architects. Even seemingly minor details in the code can have profound architectural implications, underscoring the importance of a collaborative approach to architecture.

In this paradigm, developers understand when to adhere to the established architecture and when to advocate for necessary changes. By fostering a culture of shared ownership over architecture, teams can navigate the inevitable challenges of software development with agility and confidence.

So let's challenge the notion that architecture is the sole purview of architects. To design and build better software we’ll have to embrace a collective mindset where every team member plays a pivotal role in shaping and maintaining the architectural integrity of your software.

Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.