Read the book and Cisco IOS Cookbook, my two cents
on
Network Warrior
·
· Score: 3, Informative
This is a really nicely put together book. It fills a nice niche at Intro to Middle level of the Cisco areas somewhere just after the CCNA and probably touching on some of the CCDA topics. Its not meant as a real cookbook - that's why there is the excellent Cisco IOS cookbook also from O'Reilly which deals with the particular obsure, nutty but damn valuable gems that are out there, from Net engineers who've had the long hours and coffee to hand us great tricks.
How to place this book is like this, so you've finished or are close to your CCNA and would like some sound practical advice to round out the course or maybe to help you revise it, well this is the book for you. If you know more and are in deeper Cisco terrority well you might like this but you'd probably prefer the Cisco IOS cookbook.
Off topic - I also got a copy of Limoncelli et al's revised version of The Practise of System and Network Administration in the same batch, given the first edition was most excellent there is little to say except the second is even better. Common sense and practical knowledge without getting lost in OS or application issues.
Congratulations to Mel Gorman for actually managing to get down to this low a level and still explain it sensibly.
Here are the links for interested readers: http://www.kerneltrap.com/node.php?id=55 5 (kerneltrap article)
Actual documentation: The documentation comes in two parts. The first is "Understanding theLinux Virtual Memory Manager" and it does pretty much as described. It isavailable in three formats, PDF, HTML and plain text.Understanding the Linux Virtual Memory Manager PDF: http://www.csn.ul.ie/~mel/projects/vm/guide/pdf/un derstand.pdf HTML: http://www.csn.ul.ie/~mel/projects/vm/guide/html/u nderstand/ Text: http://www.csn.ul.ie/~mel/projects/vm/guide/text/u nderstand.txtThe second part is a code commentary which is literally a guided tourthrough the code. It is intended to help decipher the more crypticsections as well as identify the code patterns that are prevalent throughthe code. I decided to have the code separate from the first document asmaintaining the code in the document would be too painfulCode Commentary on the Linux Virtual Memory Manager PDF: http://www.csn.ul.ie/~mel/projects/vm/guide/pdf/co de.pdf HTML: http://www.csn.ul.ie/~mel/projects/vm/guide/html/c ode Text: http://www.csn.ul.ie/~mel/projects/vm/guide/text/c ode.txt
HCI Labs are expensive items, it ain't cheap to get either multi-disciplinary personnel or more single disciplinary people.
The best in the business at the moment are HCIL Maryland, M$ Redmond even if they never implement their research!, Xerox PARC and Nokia's Research Lab in Finland (who ain't got a Nokia?).
Others that I know more about personally are Prof. Stephen Brewster group at Glasglow Interactive Systems Group http://www.dcs.gla.ac.uk/gist/ and my own group the Interaction Design Centre http://www.ul.ie/~idc (Gotta mention it !:-)
HCI is one area which still needs both more available research and more universal courses on the topic.
Research is definitely needed in new technology. As it requires investigating both current and possible HCI methods and techniques. As with technology, neither are social or personal interactions static these need to be further examined such as in CSCW ( Computer Support Collaborative Work) an offspring of HCI.
The requirement for more univeral courses is obvious in that I've seen friends and students design UI's and winced at the end result. Until every programmer or software engineer is taught simple HCI principles interfaces will still pain the user.
One easy book to read on this subject is Jeff Raskin's "The Humane Interface".
The best place to see what the top research labs in HCI are is in the current research literature such as the ACM http://www.acm.org in the CHI section, this really is the best place to find academic research on the topic. To find the best place for corporate research just find a successful product that uses an interface and there you go!
I'm a fourth year computer science student, I've worked in industry. I have to say that I found this book to be very useful. It is worth purchasing just for the section on Meyer's DBC (Design by Contract) ref OO Software Construction. I did however find that in conjuction with probably Code Complete over The Practice of Programmer that you get a rounded view of programming (not software engineering, just good programming practices). A visit to the website, www.pragmaticprogrammer.com is highly recommend as the resource section has a list of freeware tools and utilites that I as a student found excellant. That's my two cents
Slashdot Mirror
This is a really nicely put together book. It fills a nice niche at Intro to Middle level of the Cisco areas somewhere just after the CCNA and probably touching on some of the CCDA topics. Its not meant as a real cookbook - that's why there is the excellent Cisco IOS cookbook also from O'Reilly which deals with the particular obsure, nutty but damn valuable gems that are out there, from Net engineers who've had the long hours and coffee to hand us great tricks.
How to place this book is like this, so you've finished or are close to your CCNA and would like some sound practical advice to round out the course or maybe to help you revise it, well this is the book for you. If you know more and are in deeper Cisco terrority well you might like this but you'd probably prefer the Cisco IOS cookbook.
Off topic - I also got a copy of Limoncelli et al's revised version of The Practise of System and Network Administration in the same batch, given the first edition was most excellent there is little to say except the second is even better. Common sense and practical knowledge without getting lost in OS or application issues.
Congratulations to Mel Gorman for actually managing to get down to this low a level and still explain it sensibly.
5 5 (kerneltrap article)
n derstand.pdfu nderstand/u nderstand.txtThe second part is a code commentary which is literally a guided tourthrough the code. It is intended to help decipher the more crypticsections as well as identify the code patterns that are prevalent throughthe code. I decided to have the code separate from the first document asmaintaining the code in the document would be too painfulCode Commentary on the Linux Virtual Memory Managero de.pdfc odec ode.txt
Here are the links for interested readers:
http://www.kerneltrap.com/node.php?id=5
Actual documentation:
The documentation comes in two parts. The first is "Understanding theLinux Virtual Memory Manager" and it does pretty much as described. It isavailable in three formats, PDF, HTML and plain text.Understanding the Linux Virtual Memory Manager
PDF: http://www.csn.ul.ie/~mel/projects/vm/guide/pdf/u
HTML: http://www.csn.ul.ie/~mel/projects/vm/guide/html/
Text: http://www.csn.ul.ie/~mel/projects/vm/guide/text/
PDF: http://www.csn.ul.ie/~mel/projects/vm/guide/pdf/c
HTML: http://www.csn.ul.ie/~mel/projects/vm/guide/html/
Text: http://www.csn.ul.ie/~mel/projects/vm/guide/text/
HCI Labs are expensive items, it ain't cheap to get either multi-disciplinary personnel or more single disciplinary people.
:-)
The best in the business at the moment are HCIL Maryland, M$ Redmond even if they never implement their research!, Xerox PARC and Nokia's Research Lab in Finland (who ain't got a Nokia?).
Others that I know more about personally are Prof. Stephen Brewster group at Glasglow Interactive Systems Group http://www.dcs.gla.ac.uk/gist/ and my own group the Interaction Design Centre http://www.ul.ie/~idc (Gotta mention it !
HCI is one area which still needs both more available research and more universal courses on the topic.
Research is definitely needed in new technology. As it requires investigating both current and possible HCI methods and techniques. As with technology, neither are social or personal interactions static these need to be further examined such as in CSCW ( Computer Support Collaborative Work) an offspring of HCI.
The requirement for more univeral courses is obvious in that I've seen friends and students design UI's and winced at the end result. Until every programmer or software engineer is taught simple HCI principles interfaces will still pain the user.
One easy book to read on this subject is Jeff Raskin's "The Humane Interface".
The best place to see what the top research labs in HCI are is in the current research literature such as the ACM http://www.acm.org in the CHI section, this really is the best place to find academic research on the topic. To find the best place for corporate research just find a successful product that uses an interface and there you go!
I'm a fourth year computer science student, I've worked in industry. I have to say that I found this book to be very useful. It is worth purchasing just for the section on Meyer's DBC (Design by Contract) ref OO Software Construction. I did however find that in conjuction with probably Code Complete over The Practice of Programmer that you get a rounded view of programming (not software engineering, just good programming practices). A visit to the website, www.pragmaticprogrammer.com is highly recommend as the resource section has a list of freeware tools and utilites that I as a student found excellant.
That's my two cents