On Monday 17 March 2003 20:55, Soren Harward wrote: > On Mon 17 Mar 2003 at 15:58:23, Jacob Albretsen said: > > Basically it appears to be "work on your > > own" then come ask questions and take the test and if you pass, boom, > > you're certified. > > I won't make any comments about certifications themselves and their > helpfulness, (because I haven't been in any fields where anyone paid any > attention to them whatsoever) but I will say that the best way to study > for one is to get hold of the hardware/software you're being tested on, > work through any test problems or cases that the book has you do, and > then try to push the limits by making it do the craziest stuff you can > come up with. For instance, if you're being tested on MySQL, don't just > see if you can get the mysql client to work, and get it to work with > PHP, but see if you can get it to connect to a Windows box via ODBC and > run IIS or PWS using it. Experimenting and creating/solving your own > problems will teach you faster than anything else.
I agree wholeheartedly with that sentiment. In fact, tinkering is IMO the best way to learn. It certainly is for me. That being the case, I personally don't even see a need to buy a book or take a test, since if I can get it to do the weird stuff I want it to do anyway, then normal stuff will be easy. But maybe I just have different expectations than many. I also have the luxury of being self-employed, so sounding like I know what I'm talking about (because I do) is a lot more important to me than anything on my resume. JN ____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://phantom.byu.edu/cgi-bin/mailman/listinfo/uug-list
