Software Design and Architecture

Bob Martin (also known as Uncle Bob) starts the podcast by saying that architecture is an activity that we need to do because of all the benefits that this activity carry with them; nevertheless, he mention that the only thing that he does not like about software architecture is the separation that exists in the world between coders and the architects (the leaders of the projects), those who made the important decisions. This thing raises the question: But why this is bad?; the answer to this question (at least in my opinion) is that this kind of practice is bad because not in all projects the software architects are involved enough in order to make the best decisions about x or y topic. So, I think that good architects are the ones that propose the idea to the coding crew and both of them, make the best decision based on all the different perspectives that exist, because the perspective of the architect will not be same as the perspective of the coder crew. In this topic, Bob Martin s

I  think it is pertinent to cite the catchphrase of Auguste Gusteau (character from Ratatouille Disney film) "Anyone can cook". Now, why I start the entry of this blog with that catchphrase, the reason is simple in the film Hidden Figures the director show to all of us that anyone, any person (it does not matter its race, the skin color, the nationality) can do any task in this world. Specifically, the movie told us the story of 3 black women that works at the NASA as colored computer machines, then this woman starts to grow up in the field. One of them, her boss encourages her to study engineer (she had all the knowledge and expertise of an engineer but the simple fact that she was black she did not have the right to study in a school of white people in order to attend the courses in order to become a NASA engineer. The second of them, she was working as manager of the colored computer machine, she asked to her employer to be the manager of that area (she was workin

Summary First Period The topics that will be covered in the exam of the first period are the next ones: What is architecture? Object Oriented Basics. Patterns covered in the first period. Refactoring. Code snippets like the ones of the quizzes (Study them, they will not be covered in this blog entry). Bad smells in code. What is architecture? Architecture of a complex system is a function of its components as well as the hierarchic relationship among these components. Now we also talk about components, but what is a component. A component is an encapsulated part of a software system that serves as a building block for the structure of a system and it has the following properties: They are deployable entities. They are usually not a complete application. They might be used in unanticipated combinations. They have a well defined interface. Object Oriented Basics There are some concepts that we need to remember when we talk about Object Oriented Programming

Like the author said, the answer to the question "Is Design Dead?" is no. But the important thing is all the information and arguments the author uses to let us know how the design is not dead (even if you work using XP paradigm). As we know, Xtreme Programming is a developing paradigm that focus all the effort on coding and not documenting like in RUP or Waterfall model. But even in Xtreme Programming it is necessary to know how to design and do it well enough with the purpose of doing things easier. Xtreme Programming encourages its users the value of simplicity; for example, two of the greatest rallying cries in XP are the following slogans: "Do the Simplest Thing that Could Possibly Work" and "You Aren't Going to Need It" also known as YAGNI. Both slogans teach us the lesson of do the least work that actually works and if you do not need a requirement in that phase do not develop it until you really need it. In my opinion design is one