Programming, despite advancements like AI coding tools, retains its dual nature of captivation and agony, a sentiment echoed in Frederick P. Brooks Jr.'s fifty-year-old "The Tar Pit." Brooks likened large-system programming to beasts trapped in tar pits, where struggling against countless, simultaneously surfacing problems pulls projects deeper. Programming offers the joy of creation and usefulness, akin to building with pure thought-stuff, but demands an agonizing perfection where a single error can cause failure.

The transition from a simple "program" to a "product" requires extensive testing and documentation, costing at least three times more. Further complexity arises when a program becomes a "component" in a "system," demanding adherence to interface specifications and resource budgets, adding another threefold cost. A program serving as both product and component can cost nine times more than a standalone program, yet this integrated functionality is often the true goal.

The craft's joys include the sheer delight of making, the pleasure of creating useful tools, and the fascination with complex, puzzle-like structures. Programmers also experience the joy of continuous learning and working in a medium of pure thought. However, the woes are significant: the necessity for absolute perfection, where one wrong character halts execution, and the frequent responsibility exceeding authority, as programmers often lack control over their working conditions or objectives. Dependence on poorly designed or documented external programs further exacerbates these challenges.