I've been a full-stack developer for about 6 years, and lately, I've been focusing more on cloud architecture as my team transitions workloads into AWS services like ECS, Lambda, and RDS. I'm aiming to move from just being able to deploy applications to being capable of designing whole systems effectively.
Although I enjoy writing code, I've found myself spending more time on reviewing Infrastructure as Code (IaC), tackling IAM problems, and debugging pipelines instead of actually creating features. To prepare for an upcoming internal architecture interview, I've been using coding assistants like Claude and Beyz to conduct small design sessions, which have helped me simulate system designs and discuss trade-offs like choosing between ECS and Fargate, or explaining cost optimization to non-technical folks.
However, I'm struggling to strike the right balance between staying deep in coding to keep my skills sharp and shifting my mindset towards strategic thinking for distributed design. How do you manage to maintain your technical edge while transitioning into architecture-heavy roles? Do you allocate time for side projects or pursue certifications to stay engaged with the actual coding? I'd love to know what has worked for you.
1 Answer
It's interesting to consider whether you truly want to become a full architect or if you're realizing that modern software development often involves more integration than just coding. In many cases, even simple projects require some level of solution architecture, especially in cloud environments where much of the work is about integrating existing SaaS and open-source solutions. In that sense, the coding versus architecture debate can be a bit misleading.
I totally get that! I find myself spending more time on IaC and working on diagrams nowadays than actually writing code.