We need a software architect in the project what this position is about what does it mean our just title what I’ve seen before and most of the projects is that software architect is a programmer who is getting the highest salary who is working on more complex problems who is the most respectful guy in the crew who is staying without for a long time I believe this is all true this is how it should be but Software Architect I think is much more than that I think that the Software Architect position is about two important aspects the first one is responsibility second one is authority responsibility means that the software architect is personally responsible for the technical quality of the product where develop delivering it means that we’re blaming him for any problems who may have we can compare him with the movie director when the movie sucks we’re not going to blame the cameraman for making some mistakes we’re always blaming the director for the whole movie the same should happen in the software project when the site goes down in the middle of the night it’s a personal fault of a Software Architect if we have a security vulnerability and we’ll lose some sensitive data it’s a personal fault of an architect if we have a code which was written by someone it’s not maintainable anymore and we just lose a lot of investments it’s a fault of a Software Architect this is what personal responsibility is about on the other hand its authority software architect has to have enough power to enforce any technical decisions he wants to make we can compare him with the with the captain on the ship the captain always has a final say in any decision made on the ship the same on the software project if we have an argument between two programmers of which technology to use the Software Architect makes the final decision if we have a meeting a technical meeting discussing what’s the right way to go in our product and which which technology to implement Software Architect listens to everybody and makes a final decision so there are two aspects again it’s a responsibility and authority a good architect of course will delegate them both to the crew he’s managing so of course this responsibility will be delegated to other members to other programmers or designers and a team and of course the authority will also be delegated to the members of the team but the book that but the top of this pyramid has to be the Software Architect so if you manage to do it in your project if you manage to have an architect which who is personally responsible for the result and account and has enough authority to make any decision then your project will benefit a lot from this position so my answer to the question is like the question do we need a Software Architect and the team is yes we need this role we need this position but only if we can make this position fully responsible for the result and powerful enough to make all the technical decisions try the new project let me know how it works thanks
