2 ms·
I'm a "Senior Architect" at my company which involves various daily responsibilities (sometimes coding, sometimes scrum master, sometimes client meetings) but u
by tootie 11y ago
I'm a "Senior Architect" at my company which involves various daily responsibilities (sometimes coding, sometimes scrum master, sometimes client meetings) but ultimately I'm accountable for delivering the final product. The ultimate driver is always to finish the project moreso than to do something cool and find the ultimate gleaming elegant solution. It's almost always best to choose a approach quickly rather than spend weeks and weeks evaluating. Secondly, choosing a cutting edge technology or really anything you're unfamiliar with is a major risk that your timeline probably can't absorb. I don't have all the answers. In fact, I'm probably pretty behind at this point because I'm lucky to spend half my time looking at code. If the youngsters on my team have some new approach that they think will work and can convince me, I will definitely accept it. In fact, there are devs on my team successfully executing with a framework I still haven't bothered to learn. They're cranking it out with excellent results so I'm happy to leave them to it.