The term "craftmanship" is nowadays used mostly for the arts, or for hand crafted goods, nobody would really think about a programmer "crafting" code, much less a software architect.
Regardless of if software is considered an art, a science, or a craft, we cannot deny that most code we produce, inherently has something of ours in it, let's call it a personal touch. Software Craftsmanship begins with pride for one's work, much like an artist's pride, but it also comes from an idea of "whole".
A software architect cannot stay on the sidelines of the way code is being developed, they must be first and foremost coders. Otherwise, how could anyone be able to feel pride of the code that is being produced in one's project?
Software Craftsmanship also carries the notion of improving any and all code the coder participates in. "Leave the camp tidier than how you found it", as the boy scouts say. This is how craftsmanship defferentiates itself from old regular Agile Development.
This concept contains the core of several others, such as speedy development, quality assurance, Software Architecture, and proper refactoring, all based on the principle of "love for the craft".
No hay comentarios:
Publicar un comentario