Member-only story
How To Switch From Software Developer to Solutions Architect
Discover how you can start your journey into the world of architecture
“So what?”
The first time somebody asked me that question in a sprint review, I had no idea what to say. I was a junior developer at the time and the question destroyed me.
I stammered. I fidgeted. I looked over to my boss for help. I was truly at a loss for words.
I had just finished demoing my first project from start to finish. I was proud to say that I did this.
But when a stakeholder asked me, “So what?” I didn’t know what to say.
I knew how my project worked. That was it. I didn’t know about how it played a role in the system. I knew nothing about context. I didn’t realize it was important. Requirements were given to me and I satisfied them with my code.
I had no idea that actually writing the code was only a tiny piece of software development.
If you want to go from an individual contributor to a solutions architect, you must learn context. You have to see the big picture. It’s not about writing code. It’s about how systems interact with each other.
Beginning your journey into the world of architecture can be tricky. Where do you start? How on earth can you develop the skills you need to make that move?
It might not be as hard as you think.
Take a Step Back
As a software developer, you’re tasked with writing code to solve a specific problem. Depending on how your stories are written, you may or may not have business context around the change you’re making.
To begin changing your mindset from developer to architect, take a step back. Ask yourself, “What impact is my change making on the app?”
Figure out the pieces that make your app work. Is it composed of multiple modules that all play together? Is it a client/server app? Is it N-tier?
Your goal is to understand how all the pieces communicate with each other. Once you figure out how your app works, try to take another step back.
