4 ms·
Definitely impressed by her tenacity and creativity. But if I were to do the same for self-enrichment reasons, I might go a different route. I'd rather build on
by mcchen 13y ago
Definitely impressed by her tenacity and creativity. But if I were to do the same for self-enrichment reasons, I might go a different route. I'd rather build one or two full-blown apps in 180 days so I can dive in a deeper depth. After all, quality is better than quantity, isn't it?
Though she definitely has inspired me to do something similar.
- samsolomon 13y agoI would argue quantity is better than quality for learning. This is why in art classes teachers have you constantly making new things instead of spending the entire semester on one painting, sculpture, whatever... When I was learning Ruby on Rails I built iterations of the same stupid app dozens of times—I found that more helpful that the more in-depth app that took more than a month. EDIT: wording
- mcchen 13y agoWhen you build iterations of the same app, you are essentially working on just one app, refining it, probably making it perform faster, look nicer or just architect it better. That, to me, indicates quality over quantity. That's pretty much what I meant in my original comment. The lady who posted this is building 180 different small apps in 180 days, many of them aren't refined or related to each other, that's quantity over quality.
- sejje 13y agoI still think that quantity over quality is the way to go, though I would opt for a little more depth than these are. There's a lot of "one-time" stuff that's important in web-dev--primarily server & app config--that can be a big obstacle, for instance. Getting it down pat is a huge step in the right direction. Anyway, for beginners, I think this is a great way to do things.