Fresh ideas
I've got a multidisciplinary background that allows me to think differently to solve various types of problems.
I've got a multidisciplinary background that allows me to think differently to solve various types of problems.
I understand software architecture is often a reflection of teamwork and communication across teams. Architecture needs to reflect practicality for the business over some pure algorithmic platonic ideal.
Study the problem, and general materials to find out requirements, HIDDEN requirements, and divisions of responsibility.
Using AGILE, quickly create MVP software to understand requirements.
Introduce architecture to allow developer scaling, while also segmenting out either tricky or slow code for specialized refactors. This two pronged approach allows development to still occur rapidly because it splits up risk, and allows developers of all experience to contribute without stepping on each others toes.