Is Design Dead?

-
There are some interesting things that I found after reading the article written by Martin Fowler "Is Design Dead?" which I would like to discuss through this blog entry. First, I found interesting the way that Martin refers to the different aspects of working in a project and about extreme programming. He says that extreme programming is used to improve the team development whether it is in a company or in a team, he also refers to the "client" as a part of the team because of the consultations made to the client all the time by this you ensure that the client is happy with the work that the team is doing, I think that this type of programming is good because this causes the teamwork faster and better and provides the client with better results of the project. 

Then, I found also interesting the part of the planned design, I found this interesting because I had no idea of how it was done, Martin says that the planned design is made through listing all the issues that may occur in the project and by this we will try to avoid them, he also says that the UML plays an important role in this type of design. 

What I also found interesting and I consider as the most important thing of the article is that the perfect practica come with agile practices and planned design. Doing things fast just by doing them is not what extreme programming means, it is desired to have in mind that we will need in the project before the development because sometimes if we start to develop without a plan we will make things that we will probably later won't use and that means wasting time. I think that good development consists of good planning and best programming practices.

References: 

- Fowler, M. (2004, May). Is Design Dead? Retrieved February 09, 2019, from https://martinfowler.com/articles/designDead.html

Comentarios

Publicar un comentario

Entradas más populares de este blog

Microservices

-
After reading the article "Microservices", there are a few things that I would like to discuss, we must start first by defining what does a Microservice is. A Microservice architectural style is an approach to developing a single application into modules, each one running its own process and communicating with each other, so when an update is needed the process of implementing the changes is easier.  One interesting thing is the way the Microservice style is compared to the monolithic style where a monolithic application is built as a single unit. A monolithic server is a natural way to approach building such a system. Explaining in a simple way, a monolithic application puts all its functionality into a single process and scales by replicating the monolith into multiple servers; while a microservice architecture puts each element of functionality into separate service and scales it by distributing these services across servers, replicating as needed.  A Microservice
Leer más

Understanding the SOLID Principles

-
The following blog entry will explain the SOLID Principles based on the book Ace the programming interview: 160 questions and answers for success.  SOLID stands for 5 widely accepted principles of object-oriented programming and design, these are the S ingle Responsibility Principle, O pen/Closed Principle, L iskov Substitution Principle, I nterface Segregation Principle, D ependency Inversion Principle. These principles will be explained through this entry.  - Single Responsibility Principle: This principle says that a class should have only one responsibility. It should have only a reason or a class of reasons that cause it to change. This principle might cause a problem for programmers because deciding what a single responsibility means can be a difficulty. A single responsibility refers to a group of related business processes or it could be broken down in its constituent parts, with each part designated as a responsibility. - Open/Closed Principle: This principle s
Leer más

Ethical Reflection on Ready Player One

-
Everything that has a beginning must have an end and this book is not the exception. During the course of S/W Design and Architecture, we read the book "Ready Player One" by Ernest Cline and I would like to make an ethical reflection of this book through this blog entry. I would like to start with two quotes:  Morrow wrote in his autobiography that he’d left GSS because ... he felt that the OASIS had evolved into something horrible. “It had become a self-imposed prison for humanity,” he wrote. “A pleasant place for the world to hide from its problems while human civilization slowly collapses, primarily due to neglect.” (p. 120)  (Halliday speaking) “I created the OASIS because I never felt at home in the real world. I didn’t know how to connect with people there. I was afraid, for all of my life. Right up until I knew it was ending. That was when I realized, as terrifying and painful as reality can be, it’s also the only place where you can find true happiness. Beca
Leer más