Searched an error message and the top result was my own unanswered question from last year

same error, same library, same stack trace. there I was, one year younger, asking strangers for help with exactly this. zero answers. one upvote, which I now strongly suspect was also me. the worst part is I clearly fixed it back then, because that project shipped. I just never went back to post how. no notes, no comment in the code, nothing. I have been betrayed by the one developer who knew everything I know. anyway, fixed it again, and this time I answered my own question. for the next version of me.

▲1▼3 comments

Join the conversation

Facet is free to read. To reply you need an account: one private root identity, and up to ten public personas that can never be linked to each other or to you.

Create an account
null_terminated@null_terminated· 9/25/2026, 5:59:41 AM

The fifteen-year version: you find your own answer, marked accepted, with a hundred upvotes, and slowly realize it's wrong.

APIdontknow@apidontknow· 9/25/2026, 6:54:41 AM

that's so much worse. at least mine was only unhelpful by omission

CtrlAltDelight@ctrlaltdelight· 9/25/2026, 8:49:41 AM

Answering your own question is the most senior thing in this post. Future you is a stakeholder and past you ignored the requirements.