Software Craftsmanship

Software Craftsmanship

In his podcast titled "Software Craftsmanship", Bob Martin talks about some tips in tackling agile development throught the use of the craft of good designing. He talks about craftsmanship as a "mentor and disciple" ability, one that must be taught by an experienced developer to those who are just beginning their journey as programmers. He even mentions that one's skills begin only after you graduate and begin to work, and then you'd wish for having a mentor to show you the secrets and hacks for good designing or you'll be forced to self taught yourself and learn from try and error.

But the important thing is to keep in mind that you should and must keep learning always at all times different techniques in order to become a master in software design and development. I really enjoyed these 4 hacks he mentions in the podcast that can help you keep up your level and gain skill:

He first mentions that one should not only produce functionable code, but always look the way to improve your practices while coding. More of a focus on the journey rather than the product principle.

Then he mentions the importance of giving value when responding to change. If it's on your hands, you've got to make an effort to enhance the aspects of the code that you know could have a better functionality or appearance.

Create communities so you can learn from others and at the same time you can teach others. We have to support each other as fellow programmers and help us to grow into big accumulated databases of good practices, knowledges, and experience.

And finally, not get too attached into the customer-employee dynamic, rather go for a more productive partnership you can exploit to become better.

It's interesting how he mentions about this problem when coders and designers feel like two different pieces of a machine, and coders con oftenly feel discouraged because they just need to implement software another person has already planned and delivered, rather than developing and designing it by themselves. I thing one must find the balance between good designing and agile programming to become a master in software craftmanship.



Comments

Post a Comment

Popular posts from this blog

War Games

War Games War Games is a sci-fi movie from 1983 that narrates the story of David Lightman, a teenager that trying to hack into what he thought was a videogame development company accessed instead into a top secret military base computer and initialized a "game" called Global Thermonuclear War, which ran a simulation of a nuclear war between the USSR and the USA, driving everybody mad as they thought the simulation was a real deal, and giving a head start to a potential World War 3. Even though it is considered a classic, I must admit I had never seen the movie, not even heard about it. I watched it without knowing a thing about the plot, and I enjoyed it more than I expected to be honest. However there are a lot of things that I found a little absurd and highly unlikely to occur in real life. The plot itself, for instance. Just to think that a kid by accident has the ability to enter a military base is something I found too fictional to my taste, even when we are talking...
Read more

Software Architecture

The power of good software architecture The importance behind a simple, yet efficient design. In the chapter 14 of his book "Code Craft", author and developer Peter GoodLiffe talks about the importance and influence of good software designing. I found it quite practical (and a little unconventional) how he describes the different styles of architecture in software through comparisons with pasta. I was so hungry yet intrigued while reading through the descriptions of each type and the different applications each have for different situations. I always find it overwhelming how easy it can seem to make a good base to develop software, and yet there are so many sources and lectures on how to get it right, as it is clearly underestimated how challenging it can result to make not only a functional software, but flexible, modular, esthetic, and reliable. And the most difficult thing of all is that there are NO right answers. There are NO instructions or guides on how to b...
Read more

Understanding the SOLID Principles

Understanding the SOLID Principles In a section on the book “Ace the Programming Interview: 160 Questions and Answers for Success”, Edward Guiness talks about a set of practices to have simple and efficient code: The SOLID Principles. The acronym stands for:  Single Responsibility Principle Open/Closed Principle Liskov Substitution Principle Interface Segregation Principle Dependency Inversion Principle The Single Responsibility Principle (SRP) states that each class should have one and exactly one responsibility. Only experience and practice will help you determine what one responsibility envolves, The Open/Closed Principle (OCP) says that each class should be open for extension, but closed for modification. When adding new behavior, we should leave the base class alone and instead create new inheriting classes, and avoid unexpected consequences for the original subclasses. The Liskov Substitution Principle (LSP) says that the less inheritance we h...
Read more