I have wanted to write my first blog post for a long time. The truth is that I usually spend a large amount of my free time researching topics related to software development and I have always left it on the back burner.
Professional Concerns
From a professional point of view, the growth plan I have is focused on having the possibility of performing a role close to software architecture. The truth is that it is a topic that I have been passionate about for a long time, and in the coming years, I would like to have the possibility of performing it.
The Architect Role
There are different opinions on the functions performed by the architect profile. For some it is a profile that ends up moving away from coding, and for others it is the opposite, it is a profile that must have very close contact with the code.
For me, this profile should be performed by someone who has great experience coding, and who even performing that role, stays in contact with the code. Although I also believe that the scope of coding from the architect's point of view is more related to solving problems/needs that teams have.
Key Skills
In order to perform this role, I believe there are certain skills that I have to improve over time:
- Expand technical capabilities, broadening the horizon towards other technological stacks different from those I am used to working with
- Improve leadership and negotiation skills, to be able to motivate and convince of the proposed solutions
- Communication skills to be able to transmit clearly
- Language-related skills. It is difficult to have confidence in the ideas expressed if you do not have confidence in your language skills.
All of them I have to polish little by little. My intention is to share those interesting things that I discover along the way, in case anyone might find it interesting.
I hope you find it of interest!!!