Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Today's Perl developers spend 60-80% of their time working with existing Perl code. Now, there's a start-to-finish guide to understanding that code, maintaining it, updating it, and refactoring it for maximum performance and reliability. Peter J. Scott, lead author of Perl Debugged, has written the first systematic guide to Perl software engineering. Through extensive examples, he shows how to bring powerful discipline, consistency, and structure to any Perl program-new or old. If you've ever inherited Perl code that's hard to maintain, if you write Perl code others will read, if you want to write code that'll be easier for you to maintain, the book that comes to your rescue is Perl Medic.
Would you recommend the product? yes | Price you paid?: $34.99 | Rating: 8
Great resource for Perl programmers who may have to amend or update someone else's code
Not much use to anyone else
The excellent Groklaw has the following disclaimer: IANAL (I Am Not A Lawyer), so I'd like to add the following to this review IANAPP (I Am Not A Perl Programmer). With that in mind, on to the review.
This book is aimed at people who have to maintain, fix or update Perl code written by someone else. Since I do not fall into that category (see above), I cannot vouch for the methods iven. I can, however, discuss the content and format. This book is 301 pages long and covers (AFAIK) the aspects of what to look for and how to do it. Interestingly for a programmers guide, it also delves into the 'human aspect' - how to approach the original coder, not badmouthing the team who worked on it and things like that. I didn't expect to see that and it is welcome.
It has 12 chapters and an appendix of source code. Without listing them, the chapters are about the how and the why of taking on the code - from being forced to do it as your job to doing it to make it better and more recent.
This book has many examples of code and of tests and modules. It contains good advice to the maintainer and has a large number of web links and references.
The book is well written, funny in places and has some great quotes to head up the chapters. While I couldn't really make use of this book right now (but one day.....) I would definitely recommend it to the target audience.