2 ms·
It's common approach because building something that you want is good motivation. I don't think that works as well when it is some random project from the book
by ilyt 4y ago
It's common approach because building something that you want is good motivation.
I don't think that works as well when it is some random project from the book. Like, sure, better than dry code, but I'm far more motivated to learn when I also make something for me.
- Icathian 4y agoThe challenge I, and I think many others, run into with this is that there's almost never anything I "want". I spend so much time racking my brain for what to build I never start. Having a nice curated problem put in front of me sets me off and it's easy from there.
- dgb23 4y agoI agree in regards to complete beginners. But I think for more intermediate or advanced programmers it is very beneficial to go about a project in a more self-driven, free form way. Software design, exploration, research, reading specs and so on are half of the work (or more) in programming. What I would have loved to realize when I was younger is that there's nothing you can't write. It might be a drastically simplified version compared of the real thing, but you can absolutely do it. An operating system, a browser, a web server ("from scratch") a programming language, a video game (with a custom engine)... It's all possible with enough effort. And even if you don't want to do the up-front work yourself, it is easier to find cool, guided projects out there if you already know what you want.