|
|
|
|
|
|
by 1ba9115454
2121 days ago
|
|
|
My main learning as an architect for over 10 years. The best architectures come from teams not individuals. If you don't have buy in from the team, you will fail. Listen to them, some will need your help, some won't. The boxes you draw on a white board won't survive 5 minutes when real development starts. Make sure you have used the tech yourself either previously or via a PoC before you recommend it. Complexity is the enemy, make it simple. It's very easy to add complexity but almost impossible to remove it again once it hits production. Production turns software into concrete. Document the team decisions in a architecture decision record. https://github.com/joelparkerhenderson/architecture_decision... This will really help the next set of developer who are trying to figure out why you did what you did. Setup your CI/CD pipeline very early on. Make sure testing is integrated including browser testing if applicable. |
|
|