Exploring software system which you are currently working on

If the project which we are working on uses new technologies which we don't have expertise on the skills using those technologies, I believe most of us follow same learning path (so that we learn what is required immediately and filter and postpone other information for later stage). 

Important aspect to remember is that a particular technology might become obsolete, but fundamental building blocks like frameworks, patterns, [responsibility distribution between components] last long. Once understanding on basic blocks sinks, building new skills would be not that difficult.

To appreciate the existing system architecture & design of each part and to abide by those rules, we might need to understand the non-functional requirements that forced the current design. The existing generic architectural patterns & design patterns also can be categorized based on the non-functional requirements they cater to. Realizing the patterns in the existing system, would help us abide by the vision of architect (for longevity ) while maintaining the software.

 


To understand and appreciate any new system, we need to have strong base. Both Strategic ( OO Principles, Design , Architecture , Development Processes,) and Tactical ( Algorithms ).

For old developers strong strategic base would be more desired, and for young developers strong tactical base would be desirable.

.....