41–50 of 171 posts
I always start with a ship project. My project of choice, for the last ten years, has been this little "toy" app: https://littlegreenviper.com/portfolio/nacc/ When I finally start learning SwiftUI, for real, I'll do a version of that. I find that it is a good idea, for me, to always be writing for ship.
I learn a new language/framework while trying to solve a specific problem. The latest I picked was Nodejs/Vuejs/Electron while building https://nocommandline.com. A year ago, I basically had zero to little knowledge about them but now I know a whole lot more.
Also, I'm not a professional developer. I'm a Product person who basically writes code to solve specific problems I encounter (at work and outside of work).
The thing that my job is requiring me to do. Trial by fire. But also after the 4th or 5th language and Nth framework, it gets much quicker to pick up new ones.
I really like building Conway's Game of Life. It's big enough that each time I still have to think about the solution and how to build it, but small enough that it allows me to recognize patterns and differences from a language to another.
Also second someone else’s suggestion of Exercism.
The whole idea of implementing something useless to learn a tool is deeply flawed and it is sad that most of our schools and universities still follow this practice
Some of us just really like digging through raw Martian Elevation data and turning it into models or textures or whatever. And learning a new language while we’re at it is a nice (intended) side effect. If we could just “learn the language” cold we would. By all means, if you have something “useful” you need to do, prefer that. But we don’t always have that on hand, and fun toys are a good substitute.
The thing that my job is requiring me to do. Trial by fire. But also after the 4th or 5th language and Nth framework, it gets much quicker to pick up new ones.