Software design and architecture

What I liked most about the podcast is the realistic approach that Bob Martin, with all his years of experience, takes on our work context. The tools, the way how we work evolved, how should we do it, how we make it to the professional field, the professional relationship with our customers, etc. I liked how he takes the fact that programmers used to look at cascade developing as a sort of bible or default go to in order to make code and then when we evolved to extreme programming, like the best practices of SCRUM, sometimes abusing some practices like pair programming, ignoring others, like debugging and making mistakes since nothing is set in stone. The truth is that, as “Uncle Bob” says it, we arrive to our first job without knowledge about the real word. The college gives us a general idea, but only practice is what gives us the true knowledge. We are no longer in a controlled environment, you do not know what can go wrong and how to act. In this case, I think that the dynami...

It might have to do with the way we were educated by our professors, but I have never thought of software design as something dead or that is dying. The article made a very complete explanation why this is not something true: design is not dying, I agree with the article that design is evolving. As the article states it, going into the extremes of both positions can be something risky, Extreme programming as its prosecutors paint it and with a wrong execution can effectively lead into that glorious spaghetti not understandable code that is difficult to change, to work with and to grow. On the other hand, planning everything and trying to strictly adhere to the original design does not make room for changes that you learn when you are coding that must be made in order to achieve better results and to get to the goal, also if you try to get out a working code as fast as you can, a full old-school planned design is not the best way to go. What the article states, we experienced ...

I think that the article’s author did a great job for setting a basis for a definition of architecture and for software architecture. I consider that the approach of defining architecture as the part of the design that is considered important, and as something that is difficult to change at later stages of the development. I consider this an accurate approach, since one of the parts we try to define at this stage of our majors is the language we will work on since we are not so versed yet in that field. That being said, this helps to separate between software architecture and the definition of planning and designing of software development. Considering architecture as something more specific than the design helps understand what the past lecture for the blog tried to tell when defining software architecture and its types. On the other hand, I quite disagree with the textual approach they took when specifying who determined what is software architecture. I don’t think that onl...

Software planning and design was not something we gave the importance it has when we started programming, creating and developing small projects for our courses. It was only when we started making greater projects that we became aware of one of the statements the chapters make: having a mess spaghetti or subway-like it’s going to make it hard for you to know what you did, how to fix an error, where it was or to add more functionality. What I take from the lecture, besides the types of software architecture and how it resembles pasta, is how awfully important it is to plan and create a design in the early stages of how your project is going to be implemented to have clarity and help the detection of errors or lack of requirement fulfillments. Just what happened to us last semester when we had to redesign the whole project midway into the semester. Still I had not come up with the term software architecture and if it was not for that lecture, I still would be confusing it with othe...

To be honest I didn’t have an idea of how important the whole Apollo project was to the software world and vice versa.   I was already aware to a point that it had helped the computer hardware industry to develop great achievements and progress on the technology to be used because of the challenging requirements, but I did not expect it to play such an important part to the software engineering development as it was presented in here. It was shocking how the project pushed the software development so far it had to evolve. To fit the requirements of complexity and size, they laid the ground for preemptive scheduling and process priority that is used now in our computers. The gyroscopes we nowadays have in lots of our devices. The project was also important in the aspect that it brought up some of the most important issues about software development we have to these days, like how they began not knowing what to do, that requirements were needed, the importance they had to assig...

Hello there.I'm Desirée. I don't have an idea of what to expect of the course. I hope i like it. In my free time i like to play video games, listen to music, read, draw, dance and sports. The most recent books I have read are Fire and Blood from Song of Ice and Fire, The Last wish and Sword of Destiny from the Witcher collection. Some series I've been watching are The Big Bang Theory, The Nanny, Friends and You.