Builder FAQ — Practical Answers for Makers

$ faq --honest

Is AI actually good enough to build real things?

Yes — with the right expectations. AI excels at:

• Scaffolding: Getting you from zero to a working draft in minutes
• Iteration: "Make it smaller, add a chamfer, change the color palette"
• Translation: Converting between formats, languages, mediums
• Research: Synthesizing information across domains

AI struggles with:

• Precision engineering: Tolerances, material science, safety-critical design
• Artistic nuance: It can imitate style but not create genuine emotional resonance
• Long-term consistency: Multi-day projects require careful context management
• Real-world physics: It approximates but doesn't simulate

The sweet spot: AI generates 70-80% of the work, you contribute judgment, taste, and domain knowledge for the remaining 20-30%. The combination is stronger than either alone.

Do I need expensive hardware?

Depends on the medium:

You can start every single category for under $500 if you already have a computer. GPU is the main bottleneck — if you don't have one, use cloud AI services (many have free tiers) instead of running locally.

What about running AI models locally vs. cloud?

Local (your computer):

• No ongoing cost after hardware purchase
• Complete privacy — your data stays on your machine
• No internet required
• Limited by your GPU
• Setup can be technically involved

Cloud (API or service):

• Works on any hardware
• Latest models immediately available
• Pay per use — can be cheaper for light use
• Requires internet connection
• Your data goes to third-party servers

Recommendation: Start with cloud (ChatGPT/Claude free tiers). Move to local once you know what you need and have the hardware. For image generation specifically, local is dramatically cheaper after the initial GPU investment.

How do I organize projects that span multiple mediums?

This is the real skill that separates productive builders from chaotic ones. Use a consistent structure:

~/projects/project-name/
├── README.md           # What, why, how
├── DECISIONS.md        # Key choices and reasoning
├── prompts/            # Prompts that worked
├── src/                # Source files (any medium)
├── output/             # Generated artifacts
├── reference/          # Inspiration, specs, research
└── .git/               # Version control everything

Key rules:

1. One project, one folder — never scatter related files
2. README in every project — future-you forgets fast
3. Version control text — Git handles code, markdown, prompts, SVG
4. Separate source from output — source is what you edit, output is what you generate
5. Name files descriptively — headphone-mount-v3-stronger-hook.stl not final_final_v2.stl

Which AI model should I use for what?

Don't get locked into one model. They have different strengths and they improve monthly. The best builders use 2-3 models depending on the task.

How do I avoid losing work to AI hallucinations or mistakes?

1. Version control everything — Git commits are free insurance
2. Test early and often — don't write 500 lines before running the code
3. Verify critical outputs — measure 3D prints before committing to full prints (do a test fit piece)
4. Save working states — when something works, commit/tag/backup before changing
5. Don't trust blindly — AI confidently generates wrong code, wrong dimensions, wrong facts. Verify.

Is AI-generated content copyrightable?

The legal landscape is evolving (as of 2026):

• Code you prompt and edit: Generally treated as your work in practice
• AI-generated images: Copyright status varies by jurisdiction. US Copyright Office requires meaningful human authorship
• AI-assisted work (human-directed, AI-augmented): Strongest copyright position
• Pure AI output (no human creative direction): Weakest position

Practical advice: Always add meaningful human creative input. Edit, curate, combine, and refine AI outputs. Keep records of your creative process (prompts, iterations, decisions).

What's the cheapest possible way to start making things with AI?

$0 budget:

1. Sign up for ChatGPT free tier or Claude free tier
2. Install VS Code (free), OpenSCAD (free), GIMP (free), Audacity (free)
3. Use DaVinci Resolve free for video
4. Use Obsidian for notes
5. Use GitHub free for version control and storage
6. If you have a GPU: install ComfyUI for image generation

You can code, design 3D models, edit audio, edit video, create images (if you have a GPU), take notes, and manage projects — all for exactly zero dollars.

$200 budget (adds physical making):

• Everything above + Bambu Lab A1 Mini ($200) + a roll of PLA ($20)
• You can now go from prompt to physical object

How do I keep improving as a builder?

• Build in public — share your work on GitHub, Printables, YouTube. Feedback accelerates learning.
• Read other people's prompts — prompt libraries and shared ComfyUI workflows are goldmines
• Pick one medium and go deep — breadth comes naturally. Depth requires focus.
• Document everything — your DECISIONS.md file is your growth journal
• Revisit old projects — refactor code, reprint with better settings. Iteration is the skill.
• Stay current — tools change monthly. Follow 2-3 good sources, not 20.