Software Craftsmanship

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 themselves. It is a response by software developers to the perceived ills of the mainstream software industry, including the prioritization of financial concerns over developer accountability. The problem begins when a software developer starts working after college they know very little about what is going to be done on the job so they have to learn in their Jobs by themselves so, Craftsmanship helps young coders to become a master about software, you learn from other people by helping them do, not by studying in lectures and books. Software that works is fine, but the software that works and can't be maintained or can't and understood is a frightening thing to have on a system, and unfortunately most of the systems out there are in an unfortunate state of disrepair, and this disrepair is hidden from the users.
 

Comentarios

Publicar un comentario

Entradas más populares de este blog

WarGames

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
Leer más

Ethical Reflection on Ready Player One

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) I deeply agree with this quote, I believe that the world would hide its problems inside Oasis, we can see that the world it's collapsing when you see the conditions in which Parzival was living on, he was living in a kinda dump. I'd love to test the Oasis and see how VR has grown. For me VR it's an incredible technology we can take advantage of, currently, I'm taking a class of VR and I can say I'm really impressed how much it has grown, it's really like if you are in another world. Sometimes I forget where I am and nowadays VR it's not as developed as in Ready Player One, so I understand how easy it can get to lost in the game.  I
Leer más

Understanding the SOLID principles

These 5 principles are great advice discovered by Robert Martin also known as "Uncle Bob", the same we heard a podcast blog entrance ago. His acronym makes it easier for learning his principles, whenever we're developing object-oriented programs. The 5 principles are listed down below: S ingle Responsibility Principle (SRP): States that any class should have only one responsibility, although the author at some point says that there could be some classes that have 2 responsibilities. As the author continued with his explanation it confused me a little bit, because he contradicts himself. Maybe it could be clearer with the practice, as it's with all things in life.  O pen/Closed Principle (OPC): States that a class or a function should be open for extension but closed for modification. It attempts to counter the tendency for object-oriented code to become easy to be broken.  When adding new behaviour you need to leave alone the base classes instead you
Leer más