Daniel's built a home inventory system that rivals commercial asset management platforms, and it's surfaced a problem he didn't expect. The system knows everything he owns, which means it also knows about the old Kindle sitting in a drawer that has no resale value, no obvious donation path, and a vague future as a source of spare parts. His question is whether that vague future is real or a fantasy, and how to tell the difference.
The backstory matters here. Daniel moved apartments involuntarily several times, and his collection of small components got so expansive that finding a specific cable was slower than just reordering it. So he built a proprietary fork of an open-source inventory system, tagged everything with labels, engraving, or NFC, and started tracking warranties, manuals, maintenance logs, duplicates, and donation candidates. The stated goal is leanness, not hoarding. But maintaining any inventory system means you end up with legacy objects. The Kindle is his example. It's a previous generation, it works, it feels wasteful to throw out because if the current Kindle breaks, this one is a spare. But he also can't imagine who would want it as a donation. And he's been thinking about parts harvesting, the targeted dismantling of objects for components usable in other projects. He wants a decision flow. When is a legacy object worth keeping for parts versus sending to e-waste? How do workshops and home lab people actually do this? And what's an objective heuristic for people who keep old things as spares? Resale value, donation potential, spare parts. If none of those, it goes out.
The Kindle is almost a perfect test case, because it sits right at the boundary of every category. It works, so it's not obviously e-waste. It has no resale value, so it's not an asset. It's too old to donate comfortably, so it's not charity. And it contains components that are technically interesting but practically difficult to extract. If you can decide what to do with the Kindle, you can decide what to do with almost anything.
That's the thing that struck me reading this. It's not really about the Kindle. It's about the triage logic underneath every object in a collection. The inventory system makes the problem visible, but the problem was always there. Most people just don't have a database telling them exactly how many objects they're keeping for reasons they can't articulate.
Right. And the inventory system creates a new obligation. Before you cataloged everything, an old Kindle in a drawer was just an old Kindle in a drawer. You didn't have to think about it because you didn't have a record of it. The moment you assign it a SKU and a status field, you've made a claim about what it is and why it's there. If the status field says spare, you've committed to the idea that it's a spare. If it says harvest candidate, you've committed to the idea that you're going to harvest it. The system doesn't just track reality. It creates a kind of accountability to your own stated intentions.
And Daniel's system is sophisticated enough that it can flag items that have been sitting in a status for too long. Which means the system itself can become a triage tool, not just a location database. But that only works if the triage criteria are sound. Which is the actual question.
Let me distinguish three different reasons to keep a legacy object, because they have different decay curves. The first is that it's a functional spare for something you currently use. That's the Kindle scenario. The second is that it contains components that could repair or upgrade something you currently use. That's the harvesting scenario. The third is that it has resale or donation value to someone else. That's the liquidity scenario. These are not the same thing, and treating them as interchangeable is how collections get bloated.
The spare logic decays with time. A spare Kindle is only valuable as a spare if the current Kindle is likely to fail before the spare becomes obsolete. If your current Kindle is new and the spare is two generations old, the spare is probably going to be useless by the time you need it. The resale value decays faster. The harvesting value decays too, but in a different way. Components don't become less useful, but your ability to extract them and your need for them both change.
The harvesting question is the one Daniel is most curious about, and it's the one that's easiest to get wrong. There's a concept I want to introduce here, harvest viability. It's the threshold at which dismantling an object for parts is worth the time, storage, and cognitive overhead versus just buying the component new or sending the object to e-waste. And the threshold is higher than most people think.
Let's get into how workshops actually do this. Because there's a body of practice here that's more disciplined than the home gamer approach.
The Circuit Salvage book, which is a maker's guide to repurposing electronics, lays out specific discard criteria. Three main questions. First, board-level value. Does the board have a microcontroller, a motor driver, a power management IC, something that's still useful as a component? Second, component accessibility. Is it through-hole or easily desoldered surface mount, or is it ball grid array and effectively unrecoverable without reflow equipment? Third, time cost. How many hours to extract versus the cost of buying new? Those three questions filter out most of what people hoard.
The BGA point is brutal, because it means a lot of modern electronics are effectively sealed. The processor inside an old Kindle is a Freescale slash NXP i.MX chip. It's a real Linux-capable processor. It's also ball grid array, which means the connections are underneath the chip, inaccessible to a soldering iron. You'd need a reflow station or a hot air setup, and even then the success rate on extracting a BGA chip without damaging it is low for a hobbyist. So the single most sophisticated component in the Kindle is also the least harvestable.
That's the Hackaday piece from November 2025 on hacking an old Kindle. It details exactly what's inside. The e-ink display, a lithium battery, the i.MX processor, and a surprisingly capable Linux system. The article's argument is that the Kindle is more valuable as a hackable device than as a parts donor. The e-ink display is the single most valuable component, but extracting it without damaging the fragile ribbon cable is non-trivial. And the processor is technically valuable but practically unrecoverable. So the parts harvesting logic says this object has high-value components, but the extraction difficulty says those components aren't actually available to you.
So the Kindle is a case where contains valuable components and contains components worth extracting are different statements. The e-ink display is worth money if you could get it out cleanly. The ribbon cable is the failure point. One wrong flex and you've destroyed the valuable part. The battery is a standard lithium cell that may or may not be healthy. The processor is locked behind BGA. The real value of an old Kindle is as a whole device you can repurpose. Weather display, e-ink dashboard, a dedicated reading device that isn't connected to your main account. That's what the Hackaday piece is getting at. The Kindle is worth more as a Kindle than as a pile of parts.
The Loopstr electronics parts harvesting guide makes a related point. Start with a target component list. Don't harvest randomly, harvest toward a specific project or repair need. The guide categorizes objects by harvest priority. High priority means it contains rare or expensive components. Medium means common but useful components. Low means only passives and generic ICs. And the low category is where most home collections live. A box of old routers and printers and power supplies that contain capacitors and resistors and voltage regulators. All technically useful. All individually worth pennies.
This is the trap Daniel identified himself. Soldering out individual components of marginal value. The time cost of desoldering a ten cent capacitor or a generic resistor is almost never worth it. Even if you value your time at minimum wage, the math doesn't work. And the research consistently warns against this. The strategic approach is to identify components that are expensive to buy new, hard to source, or needed for a specific repair you're actually planning. Not components that might be useful someday.
The Okon Recycling guide frames harvesting within a hierarchy. Whole-device reuse comes first. Then high-value component harvest. Then material recycling. Then landfill. And the guide warns that improper e-waste disposal has environmental costs that outweigh the benefit of harvesting marginal components. So the sustainability argument cuts both ways. Harvesting a ten cent capacitor from a dead router and then throwing the rest in the trash is worse than just recycling the whole router properly.
The hierarchy matters because it prevents harvesting from becoming a justification for keeping things you should donate or recycle. If the most sustainable option is whole-device reuse, then the first question is always can someone else use this as it is. Not can I strip it.
And that connects to the donation point Daniel raised. He said when you donate, you want to donate good things to people who need and appreciate them. That's exactly right, and the research on donation is clear. Donating broken or obsolete items is not altruism. It's offloading. You're transferring the disposal problem to a charity that now has to pay to recycle your broken printer. Donation only counts if the item is functional and someone would choose to acquire it.
An old Kindle with a degraded battery is not a good donation. A functional laptop from five years ago is. The difference is whether the recipient would choose it if they had other options.
Let me give you a workshop example that illustrates the discipline. Some makerspaces keep a harvest shelf of old printers, scanners, and routers. But only for ninety days. If a component hasn't been pulled in ninety days, the object goes to e-waste. The shelf is a staging area, not a permanent collection. It prevents the harvest shelf from becoming an accumulation.
The ninety day rule is interesting because it's a forcing function. It says you don't get to keep something for the possibility of future harvesting. You keep it for a specific, near-term harvest, and if that harvest doesn't happen, the object leaves. The shelf doesn't become a museum of good intentions.
And that's the misconception that drives most of this. Keeping something for someday parts is not the same as having a plan for those parts. Without a specific, near-term need, harvesting is a fantasy that leads to accumulation. The object sits there for years, and the fantasy is that someday you'll need a twelve volt two amp power supply and this old router has one. But you never do the extraction, because the extraction is work, and the need never becomes concrete.
So that's how the pros do it. Target lists, discard criteria, time limits, and a hierarchy that puts whole-device reuse above harvesting. What happens when you bring that logic home, into a collection you actually care about?
This is where Daniel's question about an objective heuristic comes in. Because the professional frameworks are useful, but they assume a workshop context where time is billable and storage is shared. At home, the costs are softer. Storage is free until it isn't. Time is your own until it's wasted. And the emotional dimension is different. A makerspace doesn't feel guilty about sending an old printer to e-waste. A person who bought that printer with their own money does.
The emotional dimension is real. Daniel said it feels wasteful to throw out the Kindle. It's not a technical assessment. It's a vague sense that the object still has value, even if you can't name what the value is. The heuristic works because it replaces that vague feeling with a specific, objective test.
Let me build the tiered decision flow. Step one. Is this object currently functioning, and do I have a use for it as is? If yes, keep it as a spare, but set a review date. The review date is crucial. A spare without a review date is just clutter with a job title. Step two. If not, does it have resale value above a threshold? Say twenty dollars or the equivalent in your local market. If yes, sell it. Don't wait for the perfect buyer. List it, price it to move, and if it doesn't sell in a month, drop the price or move to the next step.
The twenty dollar threshold is interesting because it's low enough to be realistic but high enough to be worth the transaction cost. Selling something for five dollars involves photographing it, listing it, answering messages, meeting someone or shipping it. That's an hour of work for five dollars. Not worth it. Twenty dollars is the floor where the transaction starts to make sense.
Step three. If not, could it be donated to someone who would use it? And the test is whether the recipient would choose it if they had alternatives. A functional laptop, yes. An old Kindle with a degraded battery, probably not. Step four. If not, does it contain components that are high-value, needed for a specific planned repair or project, or rare and hard to source? If yes, harvest those specific components and then dispose of the rest. Not the whole object. The specific components. Step five. If none of the above, e-waste.
And the review date concept applies to step four as well. If you've designated something as a harvest candidate, set a deadline. The common pattern in workshop triage is a one year rule. If you haven't pulled a component from an object in a year, you never will. The object becomes clutter, not a resource.
The one year rule is harsh but accurate. A year is enough time for any project you're actually going to do to become concrete. If you haven't needed the component in a year, the need isn't real. And the object has been occupying space and mental bandwidth for twelve months for nothing.
Let's apply the heuristic to the Kindle. Resale value? Near zero for an old generation model. Donation? Only if it's functional and someone would want it. An old Kindle with a degraded battery is not a good donation. Harvestable components? The e-ink display is valuable but extraction is risky. The battery is a maybe. The processor is unrecoverable. Verdict. If it still works, keep it as a spare with a review date, or hack it into a useful device. If it doesn't work, e-waste. The harvestable value doesn't justify the extraction time.
And notice what the heuristic does. It doesn't say the Kindle is worthless. It says the Kindle's value is as a device, not as a parts donor. If you have a use for it as a device, keep it. If you don't, the parts argument isn't strong enough to justify keeping it. That's a much cleaner answer than the vague feeling of wastefulness.
Contrast with an old laptop. Resale value? Maybe fifty to a hundred dollars. Donation? Yes, if functional. Schools and refurbishers want them. Harvestable components? RAM, SSD, and sometimes the display panel are easy to extract and have real value. Verdict. Sell or donate first. Harvest only if it's broken and you have a specific need for the RAM or SSD. The laptop passes the test at multiple levels. The Kindle doesn't.
The difference is extraction difficulty and component value. Laptop RAM and SSDs are modular. They're designed to be removed. A screwdriver and five minutes gets you a component worth thirty dollars. The Kindle's valuable components are either fragile or inaccessible. The extraction cost eats the value.
And this is where Daniel's inventory system becomes useful. He can track not just location but status. Active, spare, harvest candidate, donation candidate, e-waste pending. The system can flag duplicates. Two identical cables, three old routers. It can surface items that have been in harvest candidate status beyond the review date. The inventory system becomes a triage tool, not just a location database.
The duplicate flagging is underrated. Most people don't know they have three old routers until they catalog them. And once you know, the question answers itself. You don't need three old routers. You need zero, or one if you have a specific use. The other two are e-waste or donation.
The sustainability angle deserves a moment. The research hierarchy is whole-device reuse, then high-value component harvest, then material recycling, then landfill. Harvesting is a middle option. Better than e-waste, worse than reuse. And the hierarchy matters because it prevents harvesting from becoming a justification for keeping things you should donate or recycle. If you're harvesting a ten cent capacitor from a dead router and then throwing the rest in the trash, you've done something worse than just recycling the whole router properly.
The environmental cost of improper e-waste disposal is the part people forget. A lithium battery in a landfill is a fire hazard and a toxic leak. The plastic and metals in a Kindle are recyclable, but only if they reach a proper facility. Keeping the Kindle in a drawer for five years and then throwing it in the trash is the worst outcome. E-waste recycling now is better than hoarding followed by improper disposal later.
The emotional dimension is worth naming directly. Daniel said it feels wasteful to throw it out. And the heuristic works because it replaces that vague feeling with a specific test. You're not throwing away a spare Kindle. You're sending a device with no resale value, no donation pathway, and no harvestable components to a recycler who will recover the materials properly. That's not waste. That's the responsible end of a product lifecycle.
The feeling of wastefulness is often misplaced. It attaches to the object rather than to the resources. The object is already manufactured. The materials are already extracted. The question is whether those materials get recovered or buried. Keeping the object in a drawer doesn't recover the materials. It just delays the decision.
And the decision delay has a cost. Storage space, mental bandwidth, the low-grade guilt of knowing the drawer exists. Daniel's inventory system makes that cost visible, which is why he's asking the question now. The system surfaced the Kindle as an item with no clear status. That's the system working.
I want to address the Israel-specific detail about warranties, because it's relevant to the spare logic. Daniel said formal warranties are often effectively useless in Israel. You're told to bring the item to a warehouse and wait weeks for inspection. So the practical value of a warranty is lower than the theoretical value. Which means the spare has more value, because you can't count on the warranty to replace a failed device.
That's a real factor. If the warranty process is slow and uncertain, a functional spare is worth more than it would be in a market where warranties are honored quickly. But the spare still needs a review date. The warranty situation doesn't make the spare valuable forever. It just shifts the calculus slightly in favor of keeping it.
And the calculus shifts more as Daniel's repair skills improve. He said his soldering and repair skills and sustainability awareness are evolving. A component that wasn't worth harvesting five years ago might be worth harvesting now if he has the skills and the specific need. The heuristic isn't static. It evolves with your capabilities.
That's the forward-looking piece. The heuristic is a snapshot of your current skills and needs. As those change, the answers change. But the process stays the same. Functioning and useful as is? Keep with a review date. Resale value above threshold? Sell. Donation candidate? Donate. Specific harvestable components? Harvest. None of the above? E-waste.
Let me also say something about the proprietary fork of an open-source inventory system, because that detail matters. Daniel didn't just buy a commercial asset management platform. He forked an open-source project and customized it. Which means he has the ability to add triage logic directly into the system. A status field, a review date field, an automated flag for items past their review date. The system can enforce the heuristic.
That's the difference between a database and a workflow. A database stores information. A workflow acts on it. If the system can generate a weekly list of items past their review date, the triage happens automatically. Daniel doesn't have to remember to review the Kindle. The system reminds him.
And the reminder is the key to leanness. The goal isn't minimalism for its own sake. It's knowing that everything you own has a reason to be there. Use, spare value, or genuine harvest potential. If an object doesn't have one of those, it's not part of a lean collection. It's just stuff.
The misconception most people hold is that keeping something for someday parts is the same as having a plan for those parts. The research shows it's not. Without a specific, near-term need, harvesting is a fantasy. The object sits there, and the fantasy is that someday you'll need the component. But someday never arrives, and the object becomes clutter.
The second misconception is that donation is always the ethical choice. Donating broken or obsolete items offloads the disposal problem onto someone else. Donation only counts if the item is functional and wanted.
And the third is that harvesting is the most sustainable option. The hierarchy puts whole-device reuse and donation above harvesting. Harvesting is better than e-waste, worse than reuse. If you can donate a functional device, that's more sustainable than stripping it for parts.
Hilbert: You've got the mechanism right.
Hilbert: I worked a summer at an electronics surplus store. A proper surplus place that bought pallets of corporate liquidation. My job was to triage the incoming pallets. Test it, price it, shelf it, or strip it. And I learned pretty fast that the strip pile was almost always a mistake.
Hilbert: The owner would look at a pallet of old routers and say we'll get to it. And the pile would grow. And grow. Until it was a fire hazard. The only things that ever actually got stripped were the things that had a buyer waiting for the specific part. Not this might be useful someday. I need a twelve volt two amp power supply and this old router has one. That's a harvest. Everything else was just a pile.
Hilbert: The Kindle is a perfect example. Unless you have a project that specifically needs an e-ink display, the harvest is a fantasy. The device is worth more as a device. And if you don't have a use for it as a device, it's e-waste. The parts argument doesn't change that.
Hilbert: The store had a graveyard out back. A literal pile of stripped chassis and boards that had been harvested and then abandoned. The graveyard was bigger than the sales floor. Every one of those boards was someone's good idea. Someone was going to use that transformer, that voltage regulator, that display driver. And then they didn't. And the board sat there, half stripped, until it wasn't worth finishing.
The graveyard of good intentions. That's the physical manifestation of the harvest fantasy. A pile of objects that were kept for their potential and then abandoned when the potential didn't materialize.
And the graveyard is bigger than the sales floor. That's the ratio that should scare people. More space devoted to abandoned intentions than to actual commerce.
Hilbert: The buyer waiting test is the only test that ever worked. Not is this component valuable. Is there a buyer waiting for this specific component. If the answer is no, the object goes to the floor or the bin. The strip pile is for things with a known destination.
That sharpens the heuristic. The question isn't does this contain valuable components. It's do I have a specific, known need for a specific component in this object. If the need is vague, the answer is no.
The graveyard is what happens when you answer yes to vague needs. A pile of half-stripped objects that were going to be useful someday.
Hilbert: The owner used to say the strip pile was where electronics went to die twice. Once when they stopped working, and again when nobody stripped them.
That's the line that should stick. The object dies twice. The second death is slower and takes up more space.
The first death is the failure. The second death is the waiting. And the waiting is the part you control.
Hilbert: I had a pair of needle nose pliers I kept in my back pocket all summer. Still have them, actually. They're in a box somewhere. But I don't miss the graveyard.
The open question is what a lean collection actually feels like. Not minimalism for its own sake, but the knowledge that everything you own has a reason to be there. Use, spare value, or genuine harvest potential. If an object doesn't have one of those, it's not part of the collection. It's just occupying space.
The reason evolves. As repair skills grow and sustainability awareness deepens, the calculus changes. A component that wasn't worth harvesting five years ago might be worth harvesting now, if you have the skills and the specific need. The heuristic isn't static. It's a living process.
Thanks to our producer Hilbert Flumingtop for keeping the show running while we talked about the graveyard of good intentions.
This has been My Weird Prompts. If you have a home inventory system, or you're thinking about building one, or you just have a drawer full of old Kindles and routers and cables, tell us how you triage. Email us at show at my weird prompts dot com.
We'll be back soon.
