Software Craftsmanship

-
After listening to the podcast called "Software Craftmanship", an interview with Bob Martin, I found many interesting things that I would like to discuss with this blog entry. First, I found interesting the idea of making sure that you work with someone else when doing software development, why? Because sharing different ideas, information and tips for better software development, also it is important and needed to get feedback of the project or development, you will also need to interact with the client so every part of the project is fulfilled.

There is no need to be part of a big software enterprise to complete the previous mentioned, you start learning this since school, sharing your project with someone who dominates this is helpful for the development of the project. 

But now let's talk about the main topic of the podcast, a Software Craftmanship. According to Bob Martin, a Software Craftmanship is someone who includes the improvement of the traditional agile model

 needs many things, some of them are what we've just mentioned, but he also needs an IDE to code, but a well-known IDE by the Software Craftmanship so he has no problems when coding. He also needs a repository where all the changes in the project code will be placed so every team member can see them. And finally, a Software Craftmanship needs a programming language, if we consider the time the podcast was made it was needed to learn a programming language but this need has changed through the years and I consider that nowadays you have to learn at least two or more programming languages. 

I think that the job of a Software Craftmanship is very important in the development of the project, but I also consider important the thing that it is more efficient to take the code as the driven document and the documentation to explain all the aspects of the code even if they are clear or not. 

 References: 

 - Software Engineering Radio. (2009, November 30). Episode 150: Software Craftsmanship with Bob Martin [Audio blog post]. Retrieved February 17, 2019, from http://www.se-radio.net/2009/11/episode-150-software-craftsmanship-with-bob-martin/

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