# Why Software Architects Should Keep Writing and Reading Code

DevFeed: [Why Software Architects Should Keep Writing and Reading Code](<https://devfeed.tech/articles/the-best-architects-never-stop-coding-26193.md>)

Original publisher: [Read original article](<https://journal.optivem.com/p/the-best-architects-never-stop-coding>)

Author: Valentina Jemuović

Published: 2026-08-11T06:00:37Z

Content type: opinion

Language: en

Sources: [Optivem Journal](<https://devfeed.tech/sources/optivem-journal.md>)

Topics: [coding](<https://devfeed.tech/topics/coding.md>), [Code](<https://devfeed.tech/topics/code.md>), [consistency](<https://devfeed.tech/topics/consistency.md>), [pull-requests](<https://devfeed.tech/topics/pull-requests.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>)

Tags: [code](<https://devfeed.tech/tags/code.md>), [coding](<https://devfeed.tech/tags/coding.md>), [consistency](<https://devfeed.tech/tags/consistency.md>), [developer](<https://devfeed.tech/tags/developer.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [model](<https://devfeed.tech/tags/model.md>)

## AI overview

This opinion article argues that software architects should remain engaged with code rather than treating coding as beneath them. Writing, reading, and reviewing code helps architects understand implementation costs, maintain consistency, and judge whether AI-generated code fits the existing system.

## Source excerpt

You can't feel what your own design costs unless you build something in it. And nobody is going to tell you.