应用程序架构师应该编写代码吗? [英] Should application architects write code?

问题描述

这是一个双方都有意见的常见问题.赞成的人会争论:

This is an often-asked question that has views on both side. Those in favour will argue:

• 要为编码人员设计一个系统，您必须了解如何编码(和编码)
• 如果不了解底层发生的事情，就无法设计系统
• 架构不仅涉及广泛的笔画设计，还涉及在代码级别适应不断变化的需求

另一方面，

• 架构是一个高级角色，不应关心实现细节
• 编码是一种面向细节的、头朝下的功能，与风险管理和架构的广泛视野性质不一致
• 架构是关于技术风险管理而不是实施
• 建筑是关于领导力的.从后面带头很困难

根据我的经验，架构师不应花费大量时间编码，而必须主要通过首席开发人员沟通、审查和站会与代码库保持联系.如果您花费大量时间进行编码，您就会忽视高级问题，并且无法有效管理技术风险.

In my experience architects should not be spending a lot of time coding but must keep in touch with the code base primarily through lead developer communication, review and stand ups. If you spend a lot of time coding you lose sight of the high level issues and become ineffective at managing technical risk.

推荐答案

即使您反对编码的论点是有效的，我认为开发团队尊重您和您的设计决策也很重要.如果您与他们一起承受架构决策的后果"，那么他们质疑他们的可能性就会大大降低.

Even if your argument against coding is valid, I think it's important for the dev team to respect you and your design decisions. If you "suffer the consequences" of your architecture decisions right along with them, then they're much less likely to question them.

我一直看到架构师与编码方面脱节，而他们的开发团队知道这一点.他们没有得到太多尊重.

All the time, I see architects who are out of touch with the coding side, and whose dev teams know it. They don't get much respect.

这篇关于应用程序架构师应该编写代码吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！