┌─[  ~/site  ]─────────────────────────────────┐
│     tknjkn's place                           │
└──────────────────────────────────────────────┘
                
Do everything, yet nothing to show
[ 2026-02-14 ] 

Had a talk with my uncle again — he's a devops guy who does interviews,
so we usually end up talking tech, and somehow the conversation always
steers toward so what can you actually solve? and that's when I freeze.

Not because I don't know things. I can spin up a backend with CRUD,
throw containers around when needed, build a UI to go with it,
explain why one language fits better than another, when monolith is
fine and when it's not, why microservices exist, why React gets
overused, why managers just play different game. Lately digging
into lowlevel stuff — memory, bits, squeezing cycles. Three years
fullstack. Couple if personal side projects like converting UML to code.
I'm eager to learn whatever helps solve what's in front of me.

So I list some of that. And then I stop.
Because that's literally it. That's the answer.
After the list there's nothing else — just silence.

So when he asks what next? and I say solve problems i guess it
lands flat. Like he's waiting for something specific I'm not saying.

Maybe the issue isn't what I do but how I tell it.
Or maybe I don't actually have the experience I think I have.
Three years in, still feels like I'm waiting to be found out.
I can build things but can't sell them, and maybe there's nothing
to sell in the first place.

Do everything, yet feel like nothing to show. Communication gap.
Working on it.