Should Architects Still Write Code? Balancing Hands‑On Work and Strategic Value

Whether an architect should write code sparks heated debate, but the answer isn’t universal; it hinges on the purpose behind coding and the organization’s characteristics.

In technology‑driven companies where core value lies in algorithms (e.g., ByteDance), deep code involvement is essential. Conversely, in delivery‑oriented teams such as many banking tech groups, focusing solely on coding limits an architect’s contribution.

Most delivery‑focused organizations benefit from a multidimensional "business + technology" skill set, and technical expertise should extend beyond low‑level implementation to high‑level solution design.

For architects, especially in large enterprises, value comes from embedding themselves in the most impactful teams, mastering domain knowledge, and often taking on development management responsibilities, thereby creating a unique "domain business + development management + architectural technology" advantage.

Purely technical architecture without business context leads to limited growth and can cause the role to become detached from real impact.

Key recommendations for domain architects:

Define the architect’s core value and purpose within the domain.

Act as a bridge between strategy and execution, translating high‑level plans into actionable tasks and feeding frontline feedback upward.

Secure concrete responsibilities and resources to drive architectural initiatives, ensuring authority, accountability, and support are aligned.

By aligning personal value with organizational goals and actively participating in both business and technical processes, architects can maintain relevance and avoid becoming isolated “air‑borne” roles.