Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
I think it comes naturally after working on it if you have an eye for optimization and high level designs.
I would say the first step would be to document and to understand the architecture(s) and whys of decisions.
The next step would be to do risk and feasibility analysis on projects, to do recurrent post mortems and to detect bottlenecks (financial, time, ressources, etc.)
Just throwing ideas away.
How to get good at solving problems.
My managers says that I should consider scalability, dev efforts, Operational costs etc. I am really new in this, I really need to figure out a lot of things by understanding architecture and then there are added quality parameters of the solution, where can I read all this? How to get good at this? I know one of the solution is to actually work on it, can I still get some other resources to understand things better?
question