Software Craftsmanship

Today I will talk about the podcast titled “Software Craftsmanship”. This podcast is about agile software development and software craftsmanship. It was an interview with Robert C. Martin, who is a software engineer and author of a lot of books better known as the uncle Bob.

    The first thing we hear is Uncle Bob talking about his experience of being a software architect. We also hear him saying that the worst part is the people that tend to separate architects from software developers. He believes it is weird because architects make decisions about the code and have no familiarity with it.

    Robert Martin, talks in this interview about software craftsmanship and he tells us that is a concept that says that every young coder or developer  needs to have a master because we can not learn coding just with theory, you must help another person to learn, in a project or whatever you want but help someone. This is similar to attending college, here you have classmates that maybe have some issues with a subject and as a good classmate you can help someone and with that receive more knowledge and feedback.

    Robert addresses many ideas in the podcast, he reminds us that Lisp is a very powerful language and that we should learn it, this is not the first time I hear this, in my course of Programming Languages I am quite clear, and I could witness the great power that Lisp has.

    One important idea Bob mentioned was when he exhorts us to continue learning, to invest time in knowing our skills, the scope that our field has, the area in which we have interest, in knowing new methods and programming languages. And also sharing knowledge is way more important.

Comentarios

Publicar un comentario

Entradas populares de este blog

Hidden Figures

Today I will talk about the amazing movie titled “Hidden Figures”. Normally in those times they didn’t recognize all the women were part of important projects and this movie is one example of how they used to hide the work from the matchless Katherine Johnson. I can say that it has become one of my favorite movies.     The film tells the story of three African-American women who worked for NASA in the early 1960s, collaborating in an important space program. These brilliant women achieved incredible goals that seemed impossible because they were women and African-Americans.     What impresses me about these women is their intelligence, their strength, their perseverance and their struggle that allowed them to demonstrate that they were more than capable of being involved in areas that were considered suitable only for the masculine intellect, such as science, mathematics and engineering.     I can identify a little with those great women of that movie, not because of how brilliant t
Leer más

The 4+1 View Model

Today I will talk about the resources related to The 4+1 View Model, two Youtube videos and one article named The Elephant and the Blind Programmers by Grady Booch. These videos and article speak briefly about the 4 + 1 view model, this small model consists of four sections and an additional section that is part +1, which allows us to make a better software architecture. Let me explain these views: - Logical view: This view tells us what kind of objects we are going to build, how they communicate and what kind of data they are. - Development view: It is useful for developers to always know which part is related to what else and how things are organized during development. - Process view: describes the concurrency and synchronized aspects in the software and the process of using the software or doing things. - Physical view: It tells us how the software and the hardware are related. - Use cases or scenarios (+1): They are the explanation on how the system is expected to behave, w
Leer más

Understanding the SOLID Principles

Today I will talk about the Edward Guiness’ book section titled “Understanding the SOLID Principles”. First of all Solid is an acronym that stands for five principles of object-oriented programming and design. These principles help to avoid dependencies between the classes. S-Single Responsibility Principle O-Open/Closed Principle L-Liskov Substitution Principle I- Interface Segregation Principle D-Dependency Inversion Principle Talking a bit more of these principles we are going to explain each one: Single Responsibility Principle: This principle states that one class should only have one responsibility so the changes in that class do not end up affecting unrelated critical features on the system. This happens from a single action to a set of processes. You can take a view that a single responsibility refers to a group of related business processes. The stamina and tolerance determine how far you go Open/closed Principle: This principle talks about that classes should be op
Leer más