I Am the Chief Code Supervisor. But I’m Called the Chief Architect of the Project.
- Sunil Dutt Jha
- Apr 30
- 4 min read
The Title Looks Powerful
My title says Chief Architect. Inside the project, people look to me for architectural decisions.
I review code structure. I guide microservices design. I approve API patterns. I check service boundaries. I comment on deployment design. I question performance choices. I guide refactoring. I review cloud patterns, DevOps pipelines, logging, monitoring, and release readiness.
This is important work. But structurally, I am supervising implementation (coding). I am the chief code supervisor. Not necessarily the architect of the project.
Where I Actually Operate
Inside the project, I operate mainly in P5: Implementation Tasks and partly in P6: Operations.
P5: Implementation Tasks means the people and IT tasks that build, modify, configure, or deploy components.
P6: Operations means the business and service operations by people, and IT operations that run, monitor, and maintain the service.
That is where most of my work sits. I help teams build better. I help systems run better. I help delivery move with fewer defects. But this does not automatically mean I have defined the architecture of the project.
Want to read more?
Subscribe to architecturerating.com to keep reading this exclusive post.
