For me there are only developers. An "architect" is just a developer with more responsibility of the full view of the system. If a developer doesn't know about architecture, doesn't add to the conversation, and doesn't take decisions, either they are a shy junior (that needs encouragment/experience) or a drone that I don't want to work with. If an architect that doesn't code tells me how to do my job, it indicates that I am working on the wrong place.
Writing code is writing a design. Is choosing what is the most appropriate tool, datastore, caching system, being distributed system or not.
An architect is an experience developer. If you loose your developer skills, then you are loosing design skills. Your architecture becomes detached of reality. And then becomes responsibility of the other developers to fix or hack around it.
What is the meaning of "enterprise code". Is the actual code not enterprise code?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
For me there are only developers. An "architect" is just a developer with more responsibility of the full view of the system. If a developer doesn't know about architecture, doesn't add to the conversation, and doesn't take decisions, either they are a shy junior (that needs encouragment/experience) or a drone that I don't want to work with. If an architect that doesn't code tells me how to do my job, it indicates that I am working on the wrong place.
Writing code is writing a design. Is choosing what is the most appropriate tool, datastore, caching system, being distributed system or not.
An architect is an experience developer. If you loose your developer skills, then you are loosing design skills. Your architecture becomes detached of reality. And then becomes responsibility of the other developers to fix or hack around it.
What is the meaning of "enterprise code". Is the actual code not enterprise code?