The Components That Left Your Bench and Never Came Back

There's an FTDI programmer somewhere in Bangalore that belongs to me. I lent it to a friend — good friend, we've built things together, I trust him completely — about eighteen months ago when he was debugging something over a weekend and needed it urgently. He lives twenty minutes away. I figured I'd get it back the following week.

I don't know which friend. I have four friends who fit the description of someone debugging something over a weekend eighteen months ago. I've asked three of them. None of them have it. The fourth I haven't asked yet because it's been long enough that bringing it up now feels strange.

The programmer is gone. I've accepted this. I've bought a new one. But this has happened enough times across enough components that I've started thinking about it more carefully.

The FTDI wasn't my only loss. There's a logic analyser I lent to someone at a workshop two years ago that I vaguely remember handing over but can't attach to a specific person. There are two NodeMCUs from a build night. A decent set of banana-to-crocodile cables. None of these were catastrophically expensive. Together they represent a few thousand rupees and, more annoyingly, several moments of reaching for something I needed and having to reconstruct where it went.

Why this keeps happening

Component lending has a social structure that makes tracking it almost impossible without deliberate effort.

Someone needs something urgently — usually in the middle of a build, usually on a weekend when they can't order. You have it. You lend it. Both of you think "they'll return it when they're done," which means in a day or two. Neither of you writes it down because writing it down feels overly formal for a friendly transaction between people who build things together.

Time passes. The borrower finishes their project. The component goes back into their parts bin, because it was in use and now it's available. The "not mine" label fades quickly once something sits in your own bin.

On your end, you remember for a week or two. Then you get busy. A month goes by. Then you reach for the thing, it's not there, and either you remember the loan or you don't. If you don't, you assume it's misplaced and eventually replace it. If you do remember, it's been long enough that asking feels uncomfortable.

The component has been quietly laundered out of both inventories.

What it's actually costing

I went back through my purchase history over the past two years and identified orders that were probably replacements for lent components I'd forgotten. I found five that I'm reasonably confident about: the FTDI, two NodeMCUs, the logic analyser, and a set of dupont cables I keep running out of despite starting with what felt like a lifetime supply.

Total: somewhere around ₹3,000-3,500. Not ruinous. But also not what I thought I was spending. Each transaction felt like a small unavoidable expense at the time. In aggregate it's a meaningful number.

The more invisible cost is the interruption. When you reach for something that isn't there and can't figure out why, you stop what you're doing, search, doubt yourself, maybe order something, and lose momentum. This happens more often from unclear inventory than from any other single cause in my experience.

How I handle it now

Before I hand something to someone, I log it as lent. Not in a spreadsheet — that has too much friction in the moment — but in my inventory app with a note: "lent to [name], [date]." Takes fifteen seconds. The item stays in my inventory but gets flagged as physically absent.

When I'm doing a stock check and notice I'm low on something, I can see if there's a lent quantity outstanding and who has it. That's the moment to follow up — before I'm placing a replacement order, not after.

I've also become more deliberate about what I lend. Commodity stuff — resistors, capacitors, common transistors, things I have hundreds of — I'll give away rather than lend. The accounting overhead of getting common components back isn't worth it; it's cheaper to absorb the loss than to manage the relationship around returning a ₹2 transistor.

For anything I'd genuinely miss — programmers, analysers, modules I don't have spares of — I lend, but I log it before handing it over. The fifteen seconds at the moment of lending has paid back many times over.

This system is imperfect. I still forget to log occasionally. The FTDI situation predates this approach. But the principle holds: if a component leaves your physical space, it should leave your inventory too, with a note about where it went. Otherwise it's just lost with extra steps.