The Assumption Nobody Checked
For a couple of weeks I had 23 trading cards sitting in a box, worth maybe $260 all in, waiting on me to list them by hand.
By hand, because a note in my own files said eBay’s listing tools were closed to regular sellers. Partner only. No way to do it from code, so every card meant photos, a title, a condition and a price, one at a time. The kind of job that is always an hour away and never actually gets its hour.
Then I finally checked eBay’s own documentation. It took about twenty minutes.
The door was open the whole time.
Where the “can’t” came from
I went looking for the source of that note, because I wanted to know who told me.
Nobody did. It was one line, written from memory, with no link next to it. Then it got copied. By the time I traced it, the same sentence was sitting in five different files, and every copy made it look more settled. Five places agreeing with each other feels like evidence. It was one guess with four echoes.
The worst part is that one of those files said, in plain words, that the claim had never been verified. I had written down my own warning and then walked right past it.
A “can’t” is the most expensive line in your notes
Most notes are cheap when they are wrong. If I write down the wrong price, I find out the first time I try to pay it.
A “can’t” is different. It never gets tested, because the whole point of the note is to stop you from trying. It just sits there, quietly routing you around a door, and the detour becomes the plan. You build the slow way, you get used to the slow way, and eventually the slow way is simply how it is done.
I have started to think this is where a lot of the real cost in a small operation hides. Less in the things you pay for. More in the things you decided were impossible on a busy afternoon and never looked at again.
Why it is so easy to do
Nobody writes down a false limit on purpose. It usually starts as something true about a neighbor. As far as I can tell, there really is a part of eBay’s tooling that is locked down. It just was not the part I needed. Close enough to be believable, wrong enough to cost me.
And a limit is comfortable. “Can’t” closes the question. “Probably can, after some setup I have not done yet” leaves it open, and open questions are work. So your brain files the closed version and moves on.
There is a little pride in it too. Knowing the limits of a thing feels like expertise. It is a lot less flattering to admit you never actually tried the handle.
What I do now
Three small rules, none of them clever.
Every “can’t” gets a source or a question mark. If I cannot point to where I learned it, the note says so: “I think this is closed, never checked.” That one honest line would have saved me the whole detour.
Every “can’t” gets a date. Things that were true two years ago get quietly fixed. A limit with no date on it reads as permanent, and almost nothing is.
Anything that blocks real work gets checked again before I build around it. Twenty minutes of reading before an hour of workaround. It is the same instinct as not waiting for permission to start, pointed at myself. Half the time the permission I was waiting on was one I had denied on my own behalf.
The part that still bugs me
The cards were never the point. $260 is $260.
What bugs me is wondering how many other lines like that are sitting in my files right now, each one politely steering me around something that would have worked. I will never know the full count. I do know how to find them. Go looking for every sentence that says something is impossible, and ask it one question.
Says who?
