Skip to main content

Being a software architect

 Being a software architect is a very difficult job. Few people can balance between business requirements and system design.

You need to know the story of the system, what it can do, and it is worth updating it. If you failed to do that, you will end up with a Frankenstein of a solution.

Therefore, when someone says that they receive an opportunity to be an architect just because they did poorly in their previous position, I am getting worried and most of the time I am right to be afraid.

The architecture is horrible, and the design is equally bad. Usually, those people come to you and ask you to propose things, but rarely listen to you.

So, the best thing to do is to state your opinion but let them burn and learn from the mistakes. After all, it was not your decision to make them an architect and fighting with the system and culture should be saved for really significant problems.


Popular posts from this blog

The messy meeting

When you know there will be a messy meeting and there is nothing you can do about it, the best thing to do is to avoid it. Messy people produce messy meetings, and they take the time and the energy of everyone who is part of it. That is why instead of being part of this drama, find a better team and better meetings to invest your precious energy.

The recovery day

 What to do once all the presents are opened? Should we just move forward with our goals? As I wrote about recovery day after flying long distance. It is important to plan a recovery day after the holidays. This is your guilty free time.

New year preparations

 I stopped preparing for things since August this year. I decided to go with the flow. With no plans for the New Year, today I received an invitation to a party. Seems like not having any plan was the best plan in the end.