Initially, It took us days to implement even simplest of algorithms because we were encouraged to constantly improve our code bit by bit. Only when he was satisfied with what we had implemented would he allow us to look at the code in the book. He taught us to think independently. Independent of the book. Unfortunately this method got a bit lost as the number his students increased from 30 - 40 to hundreds.
No wonder most of the people from my batch and my seniors went on to start small but successful companies like me. Even today, most of the people I have hired are either from my batch or my seniors.
I have never met a single person who delayed learning data structures and was good at programming.
I also was studying network engineering, not CS, but I still believe I am good programmer and clients willing to pay for my work only prove it more.
This is regarding your aggressiveness of the last line...
Now - what you are saying is basically what I meant - do not just learn (as memorizing) algo, but try to implement it yourself, or better - stuck with a problem where you have to implement algo yourself not knowing such algo already exists and described. (of course, this is not applicable when you work for a client, that's why 'fun' period is necessary =))
Algorithms on other hand are already created. And “When you don’t create things, you become defined by your tastes rather than ability.", tastes to algorithms in this case..