Daniel's Dremel engraving tool died on him yesterday, and he's been trying to figure out what went wrong. That's the starting point, but the question he sent us goes a lot further. He wants to talk about teardowns as a discipline. What process do professional hardware technicians actually bring to opening up a device? What should you keep in mind when you're recording video or taking photographs if you want to maximize the informational value for other people? Why do manufacturers' spec sheets so often omit board diagrams and specific component part numbers, leaving a blind spot exactly where common repairs happen? And why has sharing this kind of information become more valuable in the AI era, when agents can retrieve something you post on Reddit just as easily as a human can? He's also asking where this kind of knowledge gets shared, crowdsourced, and built on by communities.
So today we're walking through the teardown as a discipline. Not just opening something up, but doing it in a way that produces knowledge other people can actually use.
The thing I want to name right at the top is that a teardown is not disassembly. Disassembly is what you do when you've already decided the thing is garbage and you're stripping it for parts. A teardown is a documentation process that happens to involve disassembly. The documentation is the point. If you open a device and take no photos and write nothing down, you haven't done a teardown. You've just broken something more carefully.
That's the distinction Daniel's poking at, I think. He mentions his inventory system, and how when he's opened something up and photographed the board, he uploads those photos even if he doesn't need them right now. Because he's already done the work of getting inside. The marginal cost of documenting is low once the screws are out.
And the marginal value has gone up. That's the part that's changed. Ten years ago, a photo of a PCB sitting on your hard drive helped exactly one person: you, maybe, if you remembered you had it. Now that same photo, posted somewhere public, becomes retrievable context for every future repair query about that device. Human or otherwise.
So let's start with the process. What does a professional actually do, step by step, when they open up a piece of hardware?
The first step happens before anything comes apart. You photograph the intact device from multiple angles. Every label, every model number, every regulatory marking. The FCC ID, the serial number, the voltage rating printed on the housing. That step is the one amateurs skip and professionals never do. Because six months later, when you're trying to remember which revision of the board you had, that first photo is the only record you've got.
I've done this wrong enough times to know exactly what you mean. You open something, you get excited, you start pulling screws, and then you realize you don't remember which of the three Phillips sizes went where, or whether that ribbon cable was tucked under or over the bracket.
Right. So the pro approach is to work in layers and document each layer. You photograph the intact device. Then you remove the outer housing and photograph what's revealed. Then you remove the next layer, photograph again. Each photo is a checkpoint. If you get lost during reassembly, you can walk backward through the layers.
And the screws. This is where the magnetic mat or the parts tray comes in.
Screw mapping is the difference between a device that goes back together and a pile of parts. Different screw lengths, different thread pitches, different head types. On a laptop, you might have eight screws that look identical but two of them are two millimeters longer and go in the hinge. If you don't track which holes they came from, you're going to strip something or crack a standoff.
The classic move is the ice cube tray. You put screws from step one in the first compartment, step two in the second. It's cheap, it works, and it forces you to be sequential.
Or a piece of paper with the screws taped to it and labels. I've seen repair shops do that for phones. The paper has a rough outline of the device drawn on it, and each screw is taped where it came from. It looks like a conspiracy board, but it works.
So you've got the housing off. Now you're at the board. What changes?
The board is the centerpiece, and it gets treated differently. You photograph it in sections at high magnification before you remove anything. Not one photo of the whole board. Sections. The area around the power input, the area around the processor, the area around each connector. Because the markings on individual components are small, and a single wide shot won't capture them legibly.
This is where Daniel's Dremel lives. The micro USB connector. Once you've got a clear photo of that part of the board, identifying the exact connector type takes seconds. Without the photo, you're guessing from a spec sheet that doesn't list it.
The Dremel 7760 is a good example of the blind spot, actually. The charging failure on those tools is usually the micro USB port itself. The solder joints crack, or the connector gets loose from repeated plugging. It's a known weak point. But Dremel's spec sheet tells you the RPM, the battery type, the weight. It does not tell you what micro USB connector is on the board, what the pin spacing is, or what the solder pad layout looks like.
And that's the information you need if you're going to order a replacement part and fix it yourself. The difference between a five-minute parts order and a ninety-minute drive to the importer.
Daniel's mentioned that drive before. The importer is far enough away that the round trip costs more than the tool. But if you can identify the connector from a photo, you order a five-dollar part and spend an hour with a soldering iron.
So why don't manufacturers just publish the board diagrams? They clearly have them. Some engineer drew that board in CAD. The schematic exists.
Spec sheets are written for integration and compliance, not repair. The manufacturer's documentation is aimed at someone who's deciding whether to buy the product, or someone who needs to certify it for sale in a particular market. The board-level detail is treated as proprietary, or it's simply not considered customer-facing information. It lives in internal engineering documents that never leave the building.
And to be fair to the manufacturers, there's a real cost to publishing board diagrams. You'd have to maintain them, update them when the board rev changes, and answer questions about them.
Sure. But the result is that the exact place where repairs happen is the exact place where public documentation is thinnest. The housing, the specs, the marketing photos, all of that is abundant. The board-level detail, the connector types, the component values, that's all missing. And it's missing for every product, from a fifty-dollar rotary tool to a two-thousand-dollar laptop.
So the teardown fills that gap. But it's not just documentation. You said earlier it's an investigation. What does that mean in practice?
A professional doesn't open a device just to see what's inside. They open it with a hypothesis. What's likely to have failed? What are the known weak points of this product family? What did the user report? The answers shape what they photograph and what they record. If the device won't charge, you're paying special attention to the charging circuit, the connector, the battery. If it won't power on, you're looking at the power supply section, the fuses, the main IC.
So the teardown is diagnostic from the start. It's not neutral. You're looking for evidence that confirms or rules out a failure mode.
Right. And that means the documentation is selective in a useful way. You're not just taking random photos. You're taking photos of the things that matter for the diagnosis. The connector, the solder joints, the components in the failure path. A good teardown tells a story. Here's what I thought was wrong, here's what I found, here's what the evidence shows.
That's what separates a useful teardown from a photo dump. The photo dump shows everything and explains nothing. The useful teardown shows the important things and walks you through the reasoning.
And that reasoning is part of what makes the teardown valuable to other people. If I'm trying to fix the same Dremel, I don't just want to see your photos. I want to hear what you checked, what you ruled out, what the actual fix was. That narrative is the difference between a picture of a board and a repair guide.
We've talked about what to document. Let's talk about how to document it. The photography side. Because Daniel's right that it's easy to open something up and take a steady phone photo. But if you want the photos to be useful, there's more to it.
Lighting is the single biggest lever. A PCB is full of tiny markings, and those markings are printed in low-contrast ink on a dark green board. If you've got harsh shadows or glare, the markings disappear. Diffused, even light is what you want. A cheap lightbox, or even a white sheet over a desk lamp, transforms the quality of the photos.
I've seen people try to photograph boards with the flash on. It's worse than useless. The flash reflects off the solder mask and you get a white blob where the component should be.
Diffuse the light and the markings pop. The other thing is stability. A tripod or a phone mount, manual focus, and a remote shutter or a timer. The blur from a handheld shot at macro distances is enough to make a component marking unreadable. And if the marking is unreadable, the photo doesn't do its job.
The macro side is where it gets interesting. You mentioned focus stacking.
Focus stacking is the technique of taking multiple photos at slightly different focal distances and combining them in software. At macro distances, the depth of field is razor thin. You can get one component in focus and the one next to it is a blur. Focus stacking lets you take, say, twenty shots, each with a different slice of the board in focus, and merge them into one image where everything is sharp.
And the software does the merging automatically now. It's not something you need a photography degree for.
Right. There are free tools that do it. You load the stack of images, it aligns them and blends the sharp parts. The result is a photo where every component marking on the board is legible. That's the gold standard for a teardown photo.
What about scale? I've seen teardown photos where I can't tell if I'm looking at a board the size of a postage stamp or a dinner plate.
Include a ruler in at least one shot per board section. Or a known object. A coin, a connector, something with a standard size. That lets anyone, human or AI, infer the physical dimensions. It matters when you're trying to identify a component. A capacitor that's three millimeters across is a different part than one that's ten millimeters across, even if they look identical in a photo.
And the AI point is worth dwelling on. An AI agent looking at a photo can use the ruler to estimate dimensions, which narrows the search space for component identification.
The ruler is metadata. It tells the viewer something the pixels alone don't convey.
What about video versus stills? Daniel mentioned both.
They serve different purposes. Video captures process and narration. It's good for showing how something comes apart, what order the screws come out, how much force to apply to a clip. Stills capture detail. A video frame of a PCB is almost always worse than a still photo of the same board, because video compression throws away the fine detail.
So the best teardown records use both. Video for the disassembly sequence, high-resolution stills for the board itself.
And if you only do one, do stills. The stills are what let someone identify a component or read a marking. The video is nice to have, but the stills are the substance.
There's also the metadata question. File names, organization. Daniel mentioned his inventory system.
Name the files with the device model, the date, and the board revision if you know it. Something like Dremel 7760, main board, September 2026. Not IMG 4738. Because six months from now, or six years from now, when you're looking for that photo, the descriptive name is what makes it findable.
And it's not just about your own future self. If you upload those photos somewhere public, the descriptive name is what makes them findable by other people and by search engines and by AI agents.
The naming scheme is part of the documentation. A teardown with good photos but no metadata is a library with no card catalog. The information is in there somewhere, but nobody can find it.
This is where the AI era shift really lands. When you post a teardown to Reddit or a forum or your own site, you're not just helping the humans who stumble across it. AI agents can retrieve and synthesize that information just as readily. A single well-documented teardown of a common failure becomes training data and retrieval context for every future repair query about that device.
And the agents never forget. They never lose the link. A human finds your Reddit post, reads it, fixes their Dremel, moves on. An AI agent ingests it, and now it's part of the context that gets retrieved the next time anyone asks about a Dremel 7760 charging failure. The value of the post compounds.
That's the part I think people haven't fully internalized. Sharing a teardown used to feel like a nice thing to do for the community. Now it's more like infrastructure maintenance. You're contributing to the knowledge base that future AI systems will draw on.
There's a self-interested angle too. If you post the teardown, and then two years later your own Dremel breaks again, you can ask an AI assistant for help and it'll retrieve your own post. You're helping yourself, just with a delay.
The audience now includes non-human agents that never forget. That changes the calculus for whether it's worth the effort to post.
Let's talk about where this stuff actually lives. The community hubs.
iFixit is the obvious one.
iFixit is the structured, wiki-style approach. Repair guides with step-by-step photos, difficulty ratings, parts lists. The format is consistent, which makes it easy to follow. And the guides are editable, so the community can improve them over time. If you're doing a teardown of a common device, iFixit is where you want it to end up.
Hackaday is the other end of the spectrum. More narrative, more technical commentary. It's where you go to read about someone's teardown of an obscure piece of industrial equipment, with digressions about the history of the manufacturer and the weird design choices.
Hackaday teardowns are essays as much as documentation. They tell a story. The technical detail is there, but it's embedded in a narrative that makes you want to read the whole thing.
Reddit is the crowdsourced diagnosis layer. Communities like r/electronics and r/AskElectronics. Someone posts a photo of a board, asks what a component is, and within hours someone has identified it and linked to the datasheet.
The Reddit approach is messier, but it's fast. And the threads become searchable records. A question asked and answered in 2024 is still there in 2026, waiting for the next person with the same problem.
YouTube is the visual teardown with narration. It's where you go to watch someone disassemble a specific device and talk through what they're seeing. The video format captures the process in a way stills can't.
Then there are the specialized forums. For specific device families. EEVblog for electronics, Badcaps for capacitor issues, car-specific forums for automotive electronics. The depth on those forums is incredible, but you have to know they exist.
What makes a teardown findable? You mentioned naming earlier.
Descriptive titles, consistent tagging, and posting in the right community. A teardown titled Dremel 7760 teardown, micro USB connector replacement will be found. A post titled my dremel broke lol will not. The title is the retrieval key. If you want your teardown to be useful to someone else, the title has to contain the words they'll search for.
The device model, the failure pattern, the fix. Those three things in the title do more for findability than anything else.
The community matters too. Posting a Dremel teardown on a general repair forum is fine. Posting it on a rotary tool forum, if one exists, is better. Posting it on iFixit is best, because that's where people go looking for repair guides.
The process is: document well, name descriptively, post in the right place. And the value compounds.
I keep thinking about the fact that the bar for good enough is lower than people think. You don't need a macro lens and a focus stacking rig. A phone photo with decent lighting and a ruler in the frame is already useful. The markings on a micro USB connector are legible in a phone photo if the light is right and you hold the phone steady.
That's worth saying explicitly. The perfect is the enemy of the posted. A mediocre teardown that exists is more useful than a perfect teardown that never got uploaded.
In the AI era, even a mediocre teardown gets ingested and becomes part of the retrieval context. The agent doesn't care if your photo is slightly blurry. It cares that the information is there.
Hilbert.
Hilbert: Nineteen ninety-four. Small repair shop in a strip mall. Guy named Sal ran it. Every device that came in got photographed before and after disassembly. Polaroid camera, label maker. Sal called it the evidence locker.
Hilbert: He had a filing cabinet. Organized by device category, not by date. VCRs in one drawer, cordless phones in another. Each Polaroid had a label with the customer name, the device model, the date, and what was wrong.
Hilbert: The reason was liability. If a customer came back and said we broke something, Sal had the photo. Here's your VCR before we opened it. That scratch was already there. That's not documentation for the community. That's defense.
Hilbert: The knowledge sharing came later, almost as a side effect. Customers would come in with a problem, and Sal would pull out the photos from the last three times he'd seen that model. He'd know exactly what failed before he opened it. The Polaroids were his memory.
Hilbert: He had a rule. If you can't find it in thirty seconds, you didn't file it right. I never learned to file that fast. He fired me after eighteen months.
Hilbert: I'm still a little bitter about it. The filing, not the firing. The firing was probably fair.
The thirty-second rule is actually a good test. If your documentation system requires you to remember where you put something, it's not a system.
It's the same principle as the descriptive file name. The retrieval has to be fast or the information might as well not exist.
Hilbert: Sal understood that before digital cameras existed. The Polaroid was the documentation. The filing cabinet was the database. The thirty-second rule was the query time.
Hilbert: What's new isn't the impulse to document. Sal had that in 1994. What's new is the sharing. Sal's Polaroids never left the shop. If the shop burned down, the knowledge was gone. Now you post a photo and it's everywhere, forever.
Hilbert: Sal would have hated that, actually. He was territorial about his knowledge. But he'd have used it anyway. He'd have been on iFixit, posting photos and complaining about the formatting.
The defensive instinct becoming public infrastructure. That's the arc.
The thirty-second rule is the bridge. If you file it well enough to find it yourself, you've filed it well enough for everyone else.
Hilbert: Sal's gone now. The shop's gone. The filing cabinet went to a salvage place, I think. But some of those Polaroids, the ones I took, they're still in a box somewhere. VCRs mostly. I never got good at the cordless phones.
Where does that leave us? If the impulse to document is old but the sharing is new, what does that mean for the teardowns we post today?
It means the teardowns being posted now, casually, imperfectly, are becoming the repair knowledge base of tomorrow. The bar for good enough is low. A few phone photos of a PCB with legible component markings. A descriptive title. A post in the right place. That's enough to save someone else hours.
The AI angle makes it matter more. The agents are reading what we post. They're building their understanding of how devices fail and how to fix them from the teardowns we share. Every teardown is a contribution to that infrastructure.
I think the open question is whether that changes the incentive. If sharing a teardown used to be community goodwill, and now it's infrastructure maintenance, does that make people more or less likely to do it? The goodwill framing was always a little soft. The infrastructure framing is more honest about what's actually happening.
It's also more durable. Goodwill fades. Infrastructure compounds.
If you've done a teardown, post it. Even a few phone photos of a PCB with legible component markings can save someone else hours. And in the process, you're building the knowledge base that your own future self will draw on.
That's a good place to land. Thanks to our producer, Hilbert Flumingtop, for keeping the show running.
This has been My Weird Prompts.
If you've got a teardown story or a repair that went sideways, we'd love to hear about it. Email us at show at my weird prompts dot com.
We'll be back soon.
