Who Needs an Architect?

For me it is weird to think about a software architect, it seems a little far fetched to have a guy hose whole job(even if it is just for a little time) is to design the software and not the coding itself, even if it seems weird at first design and architecture are very important parts of doing code and having someone good at it might just be what a project needs to success because changing some lines of code or some functionality a little is very easy, but changing the architecture of a program is hard and some major changes might be needed so it is important to have the architecture fine from the beginning or at least from stages as early as possible, changing it later might be a toll to expensive to pay and the other option might be to loss a good part of the design of the software witch might be bad for both the future of the software and the development so having someone that knows what has to be done as a software architect seems important in the end even if it sounds odd at first.

Software architecture is a difficult idea to grasp(at least for me) because it seems to just be trying to plan everything beforehand, and that sounds difficult and very abstract because trying to see in the future which classes are going to be made and which functions and witch parameters are going to receive etc seems really tough, I generally start coding just having some idea about what the software is going to do and late I just do the classes and functions according to what I need  at the moment, at least right now this seems to work( maybe because the projects I do right now are somewhat small) but I will try to plan stuff more in the future.