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

Man on the Moon

The third episode of Moon Machines, titled  Navigation Computer  tells us all about the process of building the Apollo Guidance Computer. It amazes me the amount of work that goes into a project of this size, and it has always surprised me how many people don't care about space travel, or even the amount of people who, despite seeing all the people involved and all the hard work, still deny the moon landing ever happened.  I also found it really interesting how seemingly unorganized MIT's software team was while working on this project. This isn't meant as a jab at them, but the fact that one of today's most prestigious institutions didn't have a well-defined plan speaks of how much project management and software development in general have evolved in such little time.  However, it's also funny to see how little things have changed in that regard, in the sense that even today, the amount of work that goes into developing software is grossly underestimated (even...
Post a Comment
Read more