3 ms·
You may have failed classes, but the lessons learned in working on something so improbable were probably worth the price of admission. It's good to be too pure
by chipsy 17y ago
You may have failed classes, but the lessons learned in working on something so improbable were probably worth the price of admission.
It's good to be too pure for learning purposes, because it makes you comfortable with a lot of nitpicky stuff. When you move towards commercial software, you won't get an environment that encourages you to take on the risky stuff. "Lean and mean" is the order of the day. So having the other experience gives you an edge in perspective.
- vog 17y agoI disagree. The lesson to be learned is not that pure functional programming it too extreme, but that it takes time to adopt that style. As with any other style (OO, etc.), you won't get it right in your first attempt. It takes time to get a feeling for good design - in any style.
- eru 17y agoAnd C++ is not really the right language to try functional approaches. (You should at least at a garbage collector to vanilla C++ if you want to try.)
- scott_s 17y agoWell... you actually can try out functional approaches in C++, and even gain something out of it. It's just that doing so requires a sophisticated understanding of C++.
- eru 17y agoAnd probably a sophisticated understanding FP as well, if you want to apply it in such a hostile environment. Not really a good idea when you are starting out, I guess.