There's a risk to being known as a "Craftsman".
Among peers, being known as a Craftsman is a Very Good Thing. We like to work with people who care about what they do, and who produce good, solid, well-crafted code. Those are the people I want on my team.
Outside of our circle of peers, however, the term can carry very different, sometimes negative, connotations. To the person up the food chain who is funding a project, "craftsman" can be heard as "Oh, no. They're going to burn through cash endlessly polishing instead of delivering a product." This isn't entirely unfair. Lots of projects have been burned one or two programmers who couldn't seem to finish anything, and often times they waived the banner of craftsmanship as a defense. To a higher-up who doesn't have the time or attention span to sort the situation out, this leaves the term "craftsman" tainted.
In my experience, calling oneself a "pragmatic craftsman" defuses the taint. Higher-ups hear "pragmatic" and like it. To them it means good things, like maybe that you can actually finish and ship without running way over budget.
But more than calling yourself pragmatic, you have to be pragmatic, at least when taking someone else's money. It's part of the inner game of Craftsmanship.
In reply to (dws)Re: Permanence and Programming as a "craft"
by dws
in thread Permanence and Programming as a "craft"
by Hero Zzyzzx
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |