Software craftsmanship


What I liked most about the podcast is the realistic approach that Bob Martin, with all his years of experience, takes on our work context. The tools, the way how we work evolved, how should we do it, how we make it to the professional field, the professional relationship with our customers, etc. I liked how he takes the fact that programmers used to look at cascade developing as a sort of bible or default go to in order to make code and then when we evolved to extreme programming, like the best practices of SCRUM, sometimes abusing some practices like pair programming, ignoring others, like debugging and making mistakes since nothing is set in stone.

The truth is that, as “Uncle Bob” says it, we arrive to our first job without knowledge about the real word. The college gives us a general idea, but only practice is what gives us the true knowledge. We are no longer in a controlled environment, you do not know what can go wrong and how to act. In this case, I think that the dynamic programming approach that a software architect has, plays an important part, since it is a senior with the experience entitled to teach the younger ones what he she knows , and is someone that has not stopped working on code. That last part is important since the speed that the programming world is evolving makes it hard to keep track if you do not practice.

Another thing that I liked is how Martin does not consider the programming language as an essential tool for a programmer.  We have the IDE, the version control, bug tracking and even unit testing but not the programming language. Since there are lots of programming languages I think he considers more important the procedures and tools that help you write a good reliable program in an easier way, that the means to an end that represents the language. In this last part of the podcast he makes the relation between all this options and knowledge available to one of my favorite parts about our field: that you must not stop to learn whenever you can and be updated about what happens outside, since it is such of vital importance in order to be a good programmer. Quite a great podcast that shows a complete picture of the programming environment.

Comentarios

Publicar un comentario

Entradas populares de este blog

Ethical Reflection on R.P.O.

Being RPO a book I really loved and enjoyed from the very first time I read it, I think we can rescue one or two things besides the entertained story and the wholesome references. I hope that those who read the book can see them and think at least a little about those topics. In the book, we have this society that has seek refugee of the reality inside a virtual world called Oasis, because for them, reality was not as interesting, or in some cases reality was really a terrible place to be. There is also this world with almost all the resources wasted and in consequence a lot of people living either in an extreme poverty, or being miserable with the little income they had, which pushed them further into Oasis.   Our reality being not as bad as this world inside R.P.O. nowadays this imaginary situation where people aisle themselves is similar to what we tend to do with technology and social media. We tend to create this image we want other people to see on this media and we...
Leer más

An Introduction to Metaprogra... what?

During my first years studying programming, I always considered that creating a program that wrote programs was something quite confusing and complicated. I consider this article to be something useful and simple to introduce the concept of metaprogramming, even if I got lost at some point of the way and did not completely grasp the whole idea. The professor is right in that a metaprogram is usually considered as something complicated and a little bit mystified. It was quite helpful that the example for the introduction to this topic was given in ruby, since it is a very simple yet powerful language that is dynamic and lets you concentrate in the concept rather than in the language syntax, almost like it was pseudocode. What was left not so clear to me is how code modification during runtime can be considered as metaprogramming. Since it is something so exclusive of certain languages and until this course I had not been introduced to it or used it, I’m not very familiar with ...
Leer más

Microservices

It is not the first time I have heard of Microservices, but I never had the time to really get into the subject. In particular, I believe that the Monolithic helps to visualize the reason of why microservices have been a hit, rebuilding and relaunching a whole application each time something changes. It may not seem something crazy… if we are talking about a small app, but when you really think about it in the real and productive world this can be quite difficult and that’s when microservices come in to save the day. The main advantage of a microservice style is that it makes everything modular, so you don’t have to go through the process of deploying the whole system with every change that is made, but it is not the only one. It also allows you to create several small cross functional teams, and what really caught my attention is the view that this style has over software and products, not just over projects. It makes more sense to me to think about software as a product that ev...
Leer más