t4mer@notebook

// essay · learning · essay · 15 august 2026 · 1 min

Why I'm comfortable saying “I don't know yet”

Being experienced at software does not mean being experienced at every technology.

There is a version of seniority that is a performance: never pause, never say “I have not used that,” translate every unfamiliar word into something you already know.

I have done that performance. It is tiring, and it produces bad systems. You map Qt onto Laravel until the map is more dangerous than the territory. You nod at “embeddings” until you ship a search that cannot explain itself.

What I actually know

I know how to work on production backends. PHP, Laravel, MySQL, Redis, AWS, the unglamorous path from a request to a side effect that must not happen twice. I know how to read logs that are lying, and how to notice when the application never ran.

That is a real skill. It is not a licence to fake C++.

What I am learning on purpose

C++ and Qt, because I want to understand programs that live longer than a PHP request. Vector databases and retrieval, because I want to understand search when “nearby” is a coordinate. I label those notes learning. If this site still exists in five years, I would like those pages to look slightly naive. That would mean I continued.

The useful sentence

“I don’t know yet” is not humility theatre. It is a planning tool. It decides whether I am designing a vendor abstraction or reading the installer log. It decides whether I am writing a runbook or a guess.

The Problem Log exists because I get stuck. The C++ series exists because I am supposed to. Both are more honest than a skills bar chart.