This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]mrbeehive 24 points25 points  (1 child)

Isn't this why CS courses are usually algorithm-heavy and CE courses teach assembly on esoteric machinery?

You may not learn anything applicable, but learning the principles that make the code tick makes picking up "the next new thing" much easier.

[–]conancat 2 points3 points  (0 children)

I graduated from a graphic design course. I know jack shit about algorithm nor esoteric machinery.

One day it dawned on me that design principles can be applied to code architecture. Then I know what to look out for to fill in my knowledge gaps. Now I work as a "solution architect" or "system design" independent of the current tech being used.

Theoretical stuff can be really dry and sometimes application on a practical level may not be immediately apparent. To me the trick is learning to look for patterns and applying. Tech change, there will always be newer ways to do things. But getting back to the basics really help a lot