I've Forgotten More About This Than You'll Ever Know
There is a line from Burn Notice that has lived in my head for years:
“I've forgotten more about this than you'll ever know.”
It sounds like swagger.
Lately I have discovered it can also be a filing problem.
I was talking to a woman about WinGet manifests.
She had apparently worked with them too.
Good.
Actual context.
Then she said she was impressed that I had done one.
I remember thinking:
“Impressed by what?”
It is a manifest.
A YAML file.
Then more history started falling out of storage.
I had submitted a bunch of manifests publicly.
I had been on the Chocolatey development team once upon a time.
I had built SideQuest Easy Installer as part of a job interview.
WebStorm.
Rider.
Spotify.
XYplorer.
Other things.
And the funniest part was not the list.
The funniest part was that I had not been walking around thinking about any of it.
Somebody else mentioned the niche topic and my brain went:
“Oh right. I did that.”
Technical Archaeology
This happens more than I would like to admit.
Someone mentions some obscure piece of technology.
I do not immediately remember the implementation.
I do not remember the year.
I may not remember the exact project.
But somewhere in the warehouse there is a dusty box labeled:
WE HAVE BEEN HERE BEFORE.
Then I open it.
Inside:
some ancient API,
some dead framework,
some deployment trick,
some browser behavior,
some package-management edge case,
some networking mechanism,
some absurd Windows integration.
I am not retrieving knowledge so much as excavating it.
The Weird Index
My memory is especially useless in a particular way.
I can read something completely unrelated to what I am doing.
Forget where I read it.
Forget the surrounding article.
Forget the exact implementation.
Then, months or years later, encounter a problem and suddenly think:
“This is possible.”
That is all I get.
No citation.
No link.
No exact function name.
Just a little internal flag:
Somewhere, at some point, I saw a way to do this.
Then I dig.
This is how undocumented APIs become hobbies.
Other People Remember Your Resume Better
The strange thing about a long technical career is that old accomplishments stop feeling like accomplishments.
They become sediment.
At the time, maybe something was difficult.
Maybe it took days.
Maybe it required reading source code, reverse engineering behavior, filing issues, arguing with maintainers, or writing something nobody else had bothered to write.
Then ten years pass.
Now somebody says:
“You did that?”
And your reaction is:
“Apparently.”
That is an odd feeling.
It is not pride exactly.
It is more like encountering an old version of yourself in a repository.
You recognize the username.
The commit history claims it was you.
The evidence is compelling.
The Burn Notice Problem
So that line has changed meaning for me.
“I've forgotten more about this than you'll ever know” used to sound like:
“I am an expert.”
Now it sounds like:
“There is a non-zero probability I solved this exact problem in 2014 and forgot the entire event.”
Less intimidating.
More concerning.
The longer you do technical work, the less your knowledge feels like a clean library and the more it feels like an abandoned warehouse where the lights turn on only when somebody says the right keyword.
WinGet.
Chocolatey.
Prototype.
Scriptaculous.
DNSCrypt.
Some obscure Windows tray-menu API.
Click.
Another aisle illuminates.
The Resume That Surprises Me
This is why conversations can get weird.
Somebody asks a normal question.
I answer normally.
Then they say something specific.
A buried association wakes up.
Suddenly I am telling them about some thing I did fifteen years ago that I had not consciously thought about in years.
They react like:
“What the fuck?”
I react like:
“Oh yeah.”
This is not deliberate mystery.
I am not rationing lore.
I genuinely forget.
Which creates the deeply stupid situation where another person can be discovering my technical history at roughly the same time I am.
Maybe that is what twenty-plus years eventually becomes.
Not mastery.
Not omniscience.
Just enough accumulated debris that almost any sufficiently specific question can trigger:
“Wait.”
Pause.
“I think I did that once.”
And somewhere in the background, Sam Axe raises a beer.