← All articles
Learning system·3 min read

How I actually learn new technology

My loop for picking up frameworks and tools, small builds, production constraints, and learning in public without drowning in tutorials.

learningtypescriptcareercraft

I do not learn technology by finishing a 40-hour course and forgetting it. I learn by forcing a tool to answer a real question: can it help me ship something I already understand better, faster, or safer?

The loop

  • Pick a thin vertical: auth, a CRUD domain, a job queue, a chart, one path.
  • Read official docs first; reach for blogs only when stuck on a sharp edge.
  • Break it on purpose: bad input, retries, empty states, deploy.
  • Write three notes: what surprised me, what I will reuse, what I will avoid.
  • Re-use it in a second project within a month or it was tourism.

That is how NestJS stopped being “Node with decorators” and became how I structure APIs. How Next.js stopped being a React router and became a deployment and data story. How React Native stopped being a curiosity and became a way to keep mobile and web in one product conversation.

Depth over collection

Collecting logos on a résumé is easy. Depth shows up when production misbehaves. I would rather be boringly strong in a stack I can operate than conversational in twelve frameworks I have only scaffolded. Learn widely, keep deeply.

Key takeaways

What to remember

  • Thin verticals beat marathon courses.
  • Break it on purpose, then redeploy.
  • Reuse within a month or it was tourism.
Tubonibo Williams

Written by

Tubonibo Williams

Isaac · Full-stack engineer

Full-stack engineer. I build products like Djengo end to end , architecture, delivery, and the human side of shipping under pressure. Open to roles and collaborations that value operable software.

More from the archive

Related articles