For further actions, you may consider blocking this person and/or reporting abuse
Read next
Tips for Building MVP with Cursor AI
Ethan Lee -
Kubernetes homelab - Learning by doing, Part 4: Storage
Sacha Thommet -
Thoroughly experimented with Fine-Tuning / DreamBooth training of Flux-dev-de-distill, PixelWave v03, Verus Vision
Furkan GΓΆzΓΌkara -
Exploring Java's Role in Cloud Computing and AI for 2024
Teo Nordic -
Top comments (3)
Alternating works well for myself. I have a main side project that I work on. I apply my current knowledge to its development one week. Then the next week I spend my spare time learning something new I've been eyeballing that I can apply to my current or a new project. Then when dev week rolls back around I apply my new knowledge. Rinse and repeat π
Yes, please share! I'd say this is the thing I struggle with the most (or at least a lot).
Myself, I try to do about 70% building/blogging, 30% learning (in the form of reading or coding in intro tutorials). I'm still trying to figure this out too, since there are multiple areas I want to learn like machine learning, computer vision, and frontend. Hard part for me learning is that I have a lot of different things I want to learn like machine learning, computer vision, and frontend