Every Saturday morning I build something small with a technology I've never used before.

This habit has taught me more than any course or book.

Last month's weekend projects:

Week 1: Built a simple MCP server to understand the protocol. Took 3 hours. Now I understand what all the hype is about.

Week 2: Trained a small LoRA adapter on my writing style. The results were hilariously wrong at first, then surprisingly good after adjusting the learning rate.

Week 3: Set up a local LLM with Ollama and ran benchmarks against API-based models for a specific task. The local model won for my use case.

Week 4: Built a multimodal RAG system that handles images. Learned more about CLIP embeddings in one afternoon than from reading five articles.

The rule: it has to be small enough to finish in one session (3-5 hours). It has to involve something new. And I have to write a brief post or note about what I learned.

This isn't hustle culture. This is structured curiosity. I genuinely enjoy building things. The career benefits are a side effect.

If building things on weekends sounds exhausting, that's totally valid. Find your own learning rhythm. But if you enjoy it and you're not doing it — start. The compound effect after a year is remarkable.