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

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

Is Design Dead?

On today’s entry we are going to talk about the article “Is design dead?”, which talks about how the design has been changing through the years and how the good practices were developed in order to create a good design. Is no lie that for all the people that develops software, is kind of difficult to come up with a good design because of the lack of and standards to create it, other areas may have standards or even a methodology, but not us. Because of these needs, developers have created a bunch of good practices, not to create, but to reach a good design probably in a 85% of success. For example, a good practice is a that the code we create has to be modular in order to make corrections or complete alterations in a easier, this changes may occur for many reasons, manteinance, update the information or just to simply chage the entire code to something more efficient, the same goes to the design, but the problem is that a design is more difficult to modify when is already d...
Post a Comment
Read more

Software Architecture

On today’s blog we are going to review a chapter from Pete Goodlife’s Code Craft, which is all about the basic theory of software architecture, where among the topics there is like the definition, reasons of why we should use it and lots of characteristics, of course it includes examples. One part of the text talks about the high level view, which is when the details of how was it created or implemented doesn’t appear, the only thing we can see is the essential internal structure of it and the most fundamental and important characteristics of its behaviour, which can come in-handy for many thing like identifying the key modules of all the software, identify and determine the nature of all the most relevant interfaces in the software, identify how and which components communicate with each other and to clarify the correct roles and responsibilities of the subsystems The chapter also talks about other 4 views for the software architecture, one of them is the conceptual view, ...
Post a Comment
Read more