S/W Design and Architecture

So Ernest Cline does an excellent job, building up the expectative in Ready Player One, about WarGames. The first time I heard about this movie was in the book Ready Player One, I did not understand the reference about this movie, it's supposed to be one of the favourites movies of one of the main characters. I was born in 1996 so this movie was a bit old for me. Being a guy who likes geek stuff this was so awesome for me.  A professor of mine who is one of the professors who teaches me compilers told the class that this movie was one of the main reasons for him and most of the people he knows to study a major related with computer science. So we were watching a piece of history. At first, I was so amazed to watch those old computers, they were so big and yet for the age so powerful. I was intrigued by how they have all this set up they need to have to program. But not only I was intrigued by the computers, but I also was surprised about how a 14-year-oldish boy can almost start

Having working software is not enough. We need to have well-crafted software. This is one of the many interesting points  Uncle Bob  focused on his interview in the  software engineering radio podcast . He is a software engineer who co-wrote the Manifesto Software and leads “Uncle Bob Consulting LLC” and “Clean Coders” companies where he hosts videos based on his experiences and books, also he writes and consults codes. He became an architect and designed for a while but after that, he left it because it wasn`t his thing, despite this, he thinks that  architects shouldn’t be separated from the coders because  if they will separate them, architects make important decisions but they don’t know how to react because they aren't coding experts. (If all the team Will be architects, they should make wise decisions) Then Bob starts to explain about software craftsmanship which is an approach to  software development  that emphasizes the coding skills of the  software developers  

For me, the design isn't dead, for XP the good design will appear if you listen to your code. Like I had said before I like the references between architects and programmers, and here it appears again. For a more simpler and cleaner code, you may split into teams and those teams will have only one job. The idea of coding in blocks it's something that will help you a lot when coding. It will save you some money in the future, as we know, a change in the analysis phase will cost a hundred time less than in the production phase.  YAGNI (you ain't gonna need it) Every coder have heard at least one time this phrase, maybe if you're starting to code it won't have any sense, but as you start coding more and more you will find this phrase your best friend. XP focus in the present rather than in the future (sometimes) they will advise you to code what you will need that iteration. Don't code what you will use for n-iterations even if it's free. Why did I write in

First of all, I think all kind of enterprises wether is small or big need an architect. I think the author was a little confused or maybe not, but surely he confused me in a way. In his quest for discovering the true meaning of "an architect", I discover mine. I agreed with the second definition he gave “architecture is the set of design decisions that must be made early in a project.” Trough time one thing I have grasped is that mistakes in code or in life cost even more while time pass. The only answers I have read in my classes is that think twice, code once. The idea of having a software architect is amazing, he'll help to achieve a deeper level of abstraction. This concept that I have just mentioned "think twice, code once" maybe sounds pretty obvious, and maybe an architect has more important concepts than these, but for not architects, I think it can help to understand what an architect does. He gave the design and helps with future loopholes it may enc