My 2c: 1. Learn to study. Better men than I have already given good advice in earlier posts. 2. Brent Thomson's #2-4 (production code is not the same as class code; show-offs disrupt the class; people skills are harder to develop than computer skills) 3. Linux at BYU? Both the CS and EE departments run great RHEL labs you'll be able to use. (I like the CS ones better.) 4. Linux rocks, yes, but hatred and ignorance are the way of the Dark Side. (MSDNAA + virtual machines is a great way to go. In CS345 we got some student presentations that helped me understand just how different iOS, Linux, and Windows 7 are.) 5. Have fun. 6. Take 252 from Ventura or Goodrich. 7. Don't be afraid to drop a class if you will have a hard time learning from the prof. 8. Learn at least one weird language, maybe even writing an interpreter for whitespace. 9. Learn another flavor of Unix. (see #4) 10. Sometimes it's more efficient to write less-efficient code and spend your time elsewhere. (a.k.a. gcc -O3 isn't for everyone all the time)
Like I said, those're just my 2c. Enjoy! Jon Kunkee
-------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info (unsubscribe here): http://uug.byu.edu/mailman/listinfo/uug-list
