**This is a repost - Original was deleted by mistake
Format:
Unlike a traditional talk, this was an open fishbowl discussion, encouraging participants to reflect, challenge assumptions, and engage on equal footing. The central theme: the controversial and deteriorating image of Software Craftsmanship in the broader dev community
(https://smartlink.ausha.co/punkindev/s05e14-liveatlyoncraft-table-
)[Podcast link]
đź’Ą The Current Perception of Craft
- Craft is seen as elitist, dogmatic, even arrogant.
- Some developers actively avoid the term to dissociate from the reputation.
- Outside the conferences, Craft can seem closed, judgmental, and exclusionary.
“We’ve reached a point where people abandon the label just to avoid the backlash.”
đź’Ł How Did We Get Here?
1. Craftwashing & Incompetence
- Some “craft coaches” lacked the skill they preached about.
- Trainees ended up experiencing bad practices, then associating that with “craft.”
- Craftwashing: using Craft buzzwords as a façade, with no substance behind.
- Result: disillusionment, skepticism, and erosion of trust.
2. Communication Failure
- Talking about best practices can easily sound like finger-pointing.
- “You’re doing bad work” → Instant shutdown, especially from people outside the bubble.
- Without context, terms like TDD, DDD, or hexagonal architecture sound opaque or snobby.
- Ironically, not naming them helps.
“It’s like calling someone out on a microaggression — they shut down, even if you’re right.”
3. Resistance to Change
- Many teams don’t want to be told they’re doing things wrong — even if it’s true.
- This resistance gets amplified when the message comes from “the craft guy.”
🔄 Rethinking the Movement
1. Focus on Shared Values, Not Labels
- People might resist “Craft” but still want better software.
- So… who cares what it’s called?
- Focus on impact, collaboration, and technical excellence — not the brand.
2. Choose Your Battles
- Instead of pushing every good practice, push the ones that bring clear, shared value.
- Craftsmanship is not about forcing standards — it’s about co-building better ways of working.
3. Drop the Gatekeeping
- Propose a “Guild” mindset: open, collective improvement of code quality.
- Not about mastering buzzwords — about helping each other grow.
- Reintroduce the soft skills of the Craft: humility, pedagogy, listening.
- We’ve forgotten that part.
“Being a good crafter isn’t just about code — it’s about how you bring people along.”