Tip Category: Coding

  • Write the spec first

    —

    by

    About to have Muse build something? Don’t let it write code yet. Have it draft the spec first: what gets built, what changes, what stays untouched. Read the spec, fix the thinking, then say go. Five minutes of spec saves an hour of debugging.

  • Show the error, not just the code

    —

    by

    Paste the actual error message plus the ten lines around it. Muse debugs ten times faster with the error than with a vague “it is broken.” The error is the address; the code is the neighborhood.