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.

Software Architecture

Software architecture is something that is said a lot to us students but we really never had the chance to grasp it, we where always told that having a good architecture is the key to having a software that is easy to debug, read, and cheap to maintain and that this things are good in the long run even if at the beginning having a good architecture and implementing it seems to be expensive in both money and time.

For both buildings and software it is very important to have a plan on how you are going to do things before actually doing them, because this design will be what will maintain things afloat, it might seem that software architecture is not very relevant because it seems possible to build software that  complacently lacks architecture and design and the code can be useful, but designing things before doing them is important, that can make things better and cheaper now and in the future, a good design can mean having software that is cheaper even in the near future because it make it easier to find mistakes, it makes it easier to understand what is actually going to be done in the near future and it ensures less changes in what the code will be doing. Changes are a part of almost everything and they may happen even with a great design and architecture, but it is very different to have to change something because your client changed his mind and having to change something because your lack of design made it difficult for you to see what you were going to do.

A good design can be the difference between something working like it was intended or not and it can make things cheaper to make and maintain so it most be used every time we make a program, specially if the program haves a very big scope.

Moon Machines

The story of a man going to the moon is fairly common , but the part about the software used in order to go is one that I had never heard before, it is interesting to think that there was a time in wich the idea that writting software was not one of the most important or crucial parts of a project is extremely weird now when there is a project writing the software is considered important and is given to a specialized team.

The idea of the importance of software for a project has grown a lot over the years, from being considered a side project that was unimportant like in the moon landing to being the central or even only part for many of the projects done today.

I really liked watching the documentary, the story of the problems that this project had was quite interesting and it was lateral breaking to see how much this people worked for the moon landing to happen even with the price of losing the family in many ocations, I find it very refortifying that at least in this documentary their names and efforts are remembered . The project was very harsh and lives of people where other line(a situation that I never wish to be in). Because of the great affords of the programmers everything went fine and all the astronauts could survive their journey to the moon. Code should always be seen as an important part of a project and I find it somewhat foolish to think that it can be done easily or without much trouble(I guess that examples like this changed that perception a lot). I guess that in the future code will be seen as something even more important that it is today but only time can really tell us that. 

myself

Hi, my name is Jose Angel Prado Dupont my hobbies are playing video games, reading manga and watching Japanese cartoons, currently I`m playing a new game called no man`s sky and I have great hopes for it being really good. The last movie I watched was Lights out witch was an ok horror movie.  I have heard that this class is very hard but I expect to be able to handle it.