liveBook · Manning

Software craftsmanship

As explained in Vibe Engineering

Software Craftsmanship is a software-development movement emphasizing well-crafted code, individual responsibility, and mastery of programming practice.

Software craftsmanship emphasizes well-crafted code, individual responsibility, and programming mastery. In AI-assisted development, its central challenge is preserving human judgment when models produce code faster than teams can verify it. section 1.8

Disciplined practice matters because generated code is unevenly difficult to trust:

  • Use models for scaffolding, boilerplate, and common patterns, while treating edge cases, integration, security, performance, and verification as human responsibilities. section 1.8
  • Improve specification quality rather than assuming a different model will remove the need for judgment; model-generated review can share the original model's blind spots. section 1.8
  • Treat ownership as understanding and validating the whole system, not merely producing individual parts. section 1.8

How Vibe Engineering covers it

How deep it goes
Identifies responsibility boundaries and verification risks but stops short of prescribing specific workflows, tools, or tests.
Examples
Uses scaffolding, boilerplate, common patterns, edge cases, integration, security, and performance as contrasting AI work categories.
What you can do after
Evaluate AI-assisted systems by specifying clearly, recognizing blind spots, and retaining responsibility for integration and verification.
How it connects
Connects software craftsmanship with software engineering, language models, specification quality, verification, and human judgment.

This explainer was generated by Manning's knowledge graph from the text of Vibe Engineering. The section links point to the parts of the book it draws on.