Fail of the Week
What broke, why, and what you changed. About 150–250 words and one photo.
06Builder Spotlight
Send us your build
Made it, broke it, or finally fixed it? Tell us about it in a few sentences and add a photo. Every build we run gets credit and a link back to you.
Put Build: your project name in the subject line.
What to send
- The project name.
- Three to five sentences: what it is, why you built it, and one thing that went wrong or surprised you.
- Links: repo, files, video or write-up, plus the license if it’s open.
- One to four photos you took or own.
- Your credit line: the name or handle you want shown, and the link you want with it.
- A line saying Extra Screws can publish it in the newsletter, on X and in the archive.
Ways it can run
“How I built it” Q&A
We send five to seven short questions by email. You answer in a few lines each and add a photo or two.
Parts-Bin Pick
One part you keep reaching for, and why. Up to 80 words, a link and a photo.
How we handle it
- Credit and a link on every piece, using the name or handle you choose.
- You see it first. We send you the final text before it runs.
- You keep ownership. We ask only for permission to publish it in the newsletter, on X and in the archive.
- Licenses respected. Open projects keep their license, and remixes credit the original designers.
- Privacy. We strip location data from photos and leave out addresses, screens, plates and other people’s faces.
- Removal on request. Ask any time and we’ll take it down from the archive and X. Issues that have already gone out can’t be recalled.
Mains voltage, LiPo packs, lasers or anything else that can hurt someone? Include your safety notes. We don’t run builds that bypass safety interlocks.
Open slot