Skip to main content

Software Craftsmanship


On today’s blog we are going to review our first podcast named Software Craftsmanship, were Bob Martin talks about two things mostly, the software craftmanship (kind of obvious but ok) and some software techniques, during the whole podcast Bob is asked about the relation between and some of the characterises of each one that we are going to discuss later on.

The term Software Craftmanship refers to a software development technique based on the fact that when someone finish the college and then get its first formal job, the things that are actual work they are really different to the things learned in school. Now this explanation is really accurate because what we learn in the college is just the tip of the iceberg, that is why is so difficult at the beginning of a job to actually be settle down and adapt to the work rhythm the company has. This technique has an interesting approach on how to develop the skills, because normally we learn them by trial and error, but according this approach we develop them or even obtain them by the tutoring of the more skilled programmer.

This technique is very common nowadays, in fact I think that every area technically does it, the capacitation, this technique is the equal to a capacitation in any other job; because of this many companies doesn’t use more the waterfall technique, because the technology is constantly changing, there are new updates mostly every 2 or 3 months.

I cant say I loved the podcast, but can’t also say that I hated it, is just an interview to understand better a technique that can help everyone in the industry, is more like a very good advice for everyone out there having a hard time in the work, or at least that is what I think.

Comments

Post a Comment

Popular posts from this blog

Who needs an archiect?

I n this blog entry we are going to talk about an article written by Martin Flowers entitled, “Who needs an architect”, were it talks about software architecture (kind of obvious don’t you think) and the architect's role in a software development team. To be honest, a didn’t get the author’s purpose of the article, but I think I have got the general idea, so I can review this properly. On the article the author gives many two explanations the software architecture, one of them is quoted by someone else which basically says that a high level concept of a system is only visible (or significant) to developers, now, for me this is really abstract, because I don’t thing it applies to all the projects of this topic, but the second one which is given by the author himself says that the architecture is a a shared understanding of the system design by all of the expert developers involved in the Project, now this makes more sense to me because we can understand that not only the d...
Post a Comment
Read more

Ethical Reflection on Ready Player One

Todays blog is the last one!!!!!! It has been quite a journey, but as everything, its time to end this. On today’s blog we are going to talk about a book, Ready Player One, written by Ernest Cline, this is the book that everyone in my class has been reading during the semester, and it was really, really good, I actually enjoyed it a lot. The plot is quite simple, it talks about a kid called Wade Watts, in a world were the actual real world is kind of a huge disaster for not saying other words, but in the book exist another world, a virtual one called the Oasis, were technically everyone plays it, because it was a whole new world, not only a videogame, in there people can have jobs, meet people, study in schools. The creator of the Oasis was James Halliday, and I say was because in the book he is dead, and after his dead he created 3 easter eggs that, when a player has the three, that player will own the oasis, and be the richest person in the world, and that is the goal of our dear...
Post a Comment
Read more

Microservices

On today’s blog entry we are going to talk about the Microservices architecture. This architecture has an approach where when we are developing a single app, we develop it as lots of small services, each of them running on its own process and communicating with each other with something that can bind them together. Now I have already used microservices without knowing I was actually using them, perhaps this architecture is quite intuitive for best practices or something like that, but anyway the author of the article gives some characteristics about this which are the following: ·          Componentization via Services: The components of the microservice need to be gather into libraries that will be used later on by the microservice to communicate with remote parts of the whole program. ·          Organized around Business Capabilities: This characteristic refers that we need to create divisions, e...
Post a Comment
Read more