Skip to main content

Software Craftsmanship

 For this week, we listened to the 150th episode of Software Engineering Radio, featuring Robert Martin, aka Uncle Bob, aka (by me) the author of Clean Code. In this episode, Bob talks about architects and the role they should play in software development, and he shares some tips on how you can become a true craftsman yourself. 

First thing first, Bob believes that an architect (and in my opinion, any other non-coding role in the field) should be somehow involved in the coding process, because it makes no sense to put someone in charge who will not be responsible and won't have to live with their choices. I fully agree with this, and it's why I believe that the practices he talks about afterwards and in his other work is essential if you want to pursue any career in the field. 

Craftsmanship is often used to describe a piece of work where it's clear that a lot of time, effort, and knowledge went into its creation, and it's no different for code: the final product should reflect the experience of the people who worked on it, and in software's case, should correctly and elegantly solve the right problem. 

Bob also provides some tips on how to become a craftsman, mentioning the help of source control, IDEs and the tools that come along with them (or sometimes by themselves), such as debuggers, unit testers, shortcuts, etc. 

In my opinion, Bob gives a lot of good advice, and I'm constantly implementing his teachings in my day-to-day work, but I don't fully agree with his idea of spending so much time to perfect our software skills. I'm not saying it's a bad idea for everyone, but I think this field is too focused on being the best or being in a "top" company, for which you need to have a million side projects, and spend all your free time learning new skills (or get a little bit lucky like me), but it's not necessary in order to be successful in the field. 

We have the advantage of having a huge pool of options for where to work, and there's nothing wrong with working a regular 40-hour week, in order to avoid burnout and live your life outside work. If someone wants to spend all their free time working or learning, that's fine, but it's also important to remember that it's not the only road to success. 

Comments

Post a Comment

Popular posts from this blog

Is Design Dead?

 This week, we had to read Is Design Dead? by Martin Fowler. Just by reading the title, the thought of agile methodologies popped into my head, since they do involve design, just not as much as we're accustomed to. And not too surprisingly, Fowler reached a similar conclusion: design is NOT dead, it has just evolved along with us to keep up with today's standards.  Before, design was used to make sure that you knew everything you needed to get done, and it let you find any flaws in your plan beforehand. It was meant as an all-encapsulating process that all future code will be based on. Today, it has maintained its role as a guide, as to not make the developer feel totally lost, but with today's fast-paced work environment and ever-changing requirements, with the help of methodologies such as Extreme Programming, it has evolved to become more dynamic and easier to change.  For my personal opinion, I've had experiences (both academic and professional) where a bit of desig...
Post a Comment
Read more

Why is an architect?

  This week's (very short) article, Who Needs an Architect?, Martin Fowler explains to us the different definitions of architects that exist in the software world. The first and most common definition, which Fowler disagrees with, says that an architect is (s)he who helps identify what the most important parts of a project are, in order to give it structure. However, it is also mentioned that these parts are usually the most important because they are the hardest to change, so an architect's job should also include reducing the amount of these parts. Following the logic, by this definition, an architect's job is to reduce the amount of architecture.  The second proposed definition, which I also think I agree with, is that an architect's role is more like a guide's. His purpose is to help the team become better by using his expertise, and communicating with as much of the team as possible in order to remove their blocks. I think the word architect  still fulfills thi...
Post a Comment
Read more

Microservices

 This week, we read an article called Microservices  by James Lewis and Martin Fowler, which did a great job explaining the differences between monolithic applications and those that run on microservices (and the ones that use a little bit of both). They explained the advantages and pitfalls of implementing any of these methods, and they conclude that while microservice-based applications seem promising, it's still too early to tell whether they'll be better than monolithic ones. Luckily for us, this article was published in 2014, and we're far enough in the future to know that they are, in fact, more widely used today. Before reading this article, I was already aware of these different types of applications, and I knew that the market had a preference towards microservice applications, but I hadn't realized how much this change had affected how businesses are run today. From personal experience, I belong to a cross-functional (XFN) team that dabbles in many different p...
Post a Comment
Read more