The Practice of System and Network Administration, Second Edition Review

Average Reviews:

(More customer reviews)Are you looking to buy The Practice of System and Network Administration, Second Edition? Here is the right place to find the great deals. we can offer discounts of up to 90% on The Practice of System and Network Administration, Second Edition. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

The Practice of System and Network Administration, Second Edition ReviewGood sysadmins know the technical details. They can resurrect a dead server, understand the intricacies of sendmail or the Windows registry, and recite all of the types of DNS records by heart. They own copies of the UNIX System Administration Handbook and refer to them regularly. They are good sysadmins, and will contribute solidly at an intermediate level.
Great sysadmins know all of that and what is in this book. They are the ones who go on to become the senior sysadmins and consultants, have fabulous careers, and are respected by their bosses, co-workers, and customers.
There is much more to a technical job than simply the technical skills. Don't buy this book to learn how to run a system or you will be disappointed. Do, however, buy it to learn how to be an effective professional systems administrator.
It is also useful for a manager of sysadmins who is either non-technical, or has never been a sysadmin himself, as it is a good introduction to the issues and concerns that sysadmins need to face.
Limoncelli and Hogan cover many topics, including:
- Trouble ticket systems
- Desktops and Servers (how they're the same, differ, etc.)
- Administrative networks (why bother?)
- Requirements (gathering, tracking, etc.)
- Standards and centralization of services
- How to do debugging (not "you see this problem, do this" but rather learning the process of doing good debugging)
- Fix things once, not over and over again
- Security policies (including management and organizational issues for a variety of organizational profiles)
- Disaster Recovery (again, not how to backup data, but why you'd want to, legal issues, etc.)
- Systems Administration Ethics
- Change management and revision control
- Maintenance windows: what they are and why they're good for both you and your users
- Centralization versus Decentralization
- Helpdesks: sizing, scope, processes, escalation, etc.
- Data centers (many physical facility concerns that sysadmins don't often think of, including how to move a datacenter)
- Managing non-OS software (commercial and free)
They will help you answer questions like
- Does server hardware really cost more? Do we go with a few expensive servers or many cheap ones?
- What does "redundancy" actually mean?
- Why would we spend money on backups? There's never been an outage...
- What do I do when asked to do something illegal?
- How do I communicate and schedule large system changes?
- How do I do a safe server upgrade?
- They want to decentralize the sysadmin group -- what do we do?
- How do we move our datacenter?
- What sort of policy issues are there with email?
- How do I deal with my customers abusing printers?
- What do we have to worry about if we're implementing remote access (e.g. dialup modem banks) for our users?
Finally, they close with an entire section on Management:
- How to deal with cost centers, management chains, hiring, customer support, and outsourcing.
- How to manage your customers perceptions and your team's visibility
- How to manage your own happiness (time management, communication, professional development, managing your manager, etc.)
- How to be a technical manager, how to work with non-technical managers, manage your own career growth, etc.
- How to hire good sysadmins, recruiting, interviewing, soft skills, technical skills, employee retention, etc.
- The special concerns around how to fire sysadmins (often problematic, given their higher level of access)
They even have a chapter for non-technical managers who are in charge of sysadmins (this entire book would be very useful to give to a non-technical manager who doesn't really 'get it'.)
The book closes with three appendixes:
A. The Many Role of a System Administrator
B. What to Do When...
C. Acronyms
Appendix B is particularly useful, answering a wide variety of questions with solid, practical answers.
The skills and concepts in this book are the make-or-break in many careers. They turn you from just another sysadmin into a star performer, sensitive to your customers and the business, able to interact with a wide spectrum of people.The Practice of System and Network Administration, Second Edition Overview
The first edition of The Practice of System and Network Administration introduced a generation of system and network administrators to a modern IT methodology. Whether you use Linux, Unix, or Windows, this newly revised edition describes the essential practices previously handed down only from mentor to protégé. This wonderfully lucid, often funny cornucopia of information introduces beginners to advanced frameworks valuable for their entire career, yet is structured to help even the most advanced experts through difficult projects.

The book's four major sections build your knowledge with the foundational elements of system administration. These sections guide you through better techniques for upgrades and change management, catalog best practices for IT services, and explore various management topics. Chapters are divided into The Basics and The Icing. When you get the Basics right it makes every other aspect of the job easier--such as automating the right things first. The Icing sections contain all the powerful things that can be done on top of the basics to wow customers and managers.

Inside, you'll find advice on topics such as

The key elements your networks and systems need in order to make all other services run better
Building and running reliable, scalable services, including web, storage, email, printing, and remote access
Creating and enforcing security policies
Upgrading multiple hosts at one time without creating havoc
Planning for and performing flawless scheduled maintenance windows
Managing superior helpdesks and customer care
Avoiding the "temporary fix" trap
Building data centers that improve server uptime
Designing networks for speed and reliability
Web scaling and security issues
Why building a backup system isn't about backups
Monitoring what you have and predicting what you will need
How technically oriented workers can maintain their job's technical focus (and avoid an unwanted management role)
Technical management issues, including morale, organization building, coaching, and maintaining positive visibility
Personal skill techniques, including secrets for getting more done each day, ethical dilemmas, managing your boss, and loving your job
System administration salary negotiation

It's no wonder the first edition received Usenix SAGE's 2005 Outstanding Achievement Award!

This eagerly anticipated second edition updates this time-proven classic:

Chapters reordered for easier navigation
Thousands of updates and clarifications based on reader feedback
Plus three entirely new chapters: Web Services, Data Storage, and Documentation


Want to learn more information about The Practice of System and Network Administration, Second Edition?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Documenting Software Architectures: Views and Beyond (2nd Edition) Review

Average Reviews:

(More customer reviews)Are you looking to buy Documenting Software Architectures: Views and Beyond (2nd Edition)? Here is the right place to find the great deals. we can offer discounts of up to 90% on Documenting Software Architectures: Views and Beyond (2nd Edition). Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Documenting Software Architectures: Views and Beyond (2nd Edition) ReviewSoftware architecture really is unlike any other aspect of its design. The architecture has deeper meaning and larger scale than any other aspect, and can't be discussed in the same ways.
This book opens that discussion. Among the "architecture" books I've read lately, this is the only one to offer concrete advice on describing, presenting, and analyzing archtiectural features of a system. It identifies a number of documentation types and variations. It also identifies a number of different readers - developers, future architects, users, etc. - and addresses their different documentation needs.
The authors use a little UML, but not a lot. For one thing, standard UML works at too low a level for architectural discussion. Classes, and even hierarchies of class inheritance are such fine-grained entities that architecture gernerally won't address them. Instead, the authors offer a number of diagramming styles of their own. For once, I agree with the need for non-standard notation.
Even so, I think they under-utilize the existing standards in favor of their own terminology and notation. They could have used a UML profile for lots of the discussion. It would have had to be a new profile, however, not just a force-fit of the real-time profile. They also under-used the existing architecture standards (IEEE/ANSI, DoD, NASA, and more) in favor of their own discussion. Maybe their approach can be used in any of those frameworks, but that should have been more explicit.
I see only one major flaw in this book, the assumption that a software system's architecture describes the program delivered to a customer. That's way too narrow. A large system includes things like test harnesses, debug instrumentation, application-specific QA tools, and user documentation of many kinds. Those can be major undertakings of their own. They are intimately tied to the delivered software, and may constrain the actual product.
On the postivie side, this book offer an extensive real-world case study. That probably doubles the book's value, by putting a concrete face on the otherwise abstract discussion.
There are two ways to use this book: you can agree with it, or think about it and disagree with it. If you really think about it, though, you get it's full value whether you agree or not.
In other words, you can't lose by reading this book.Documenting Software Architectures: Views and Beyond (2nd Edition) Overview"This new edition is brighter, shinier, more complete, more pragmatic, more focused than the previous one, and I wouldn't have thought it possible to improve on the original. As the field of software architecture has grown over these past decades, there is much more to be said, much more that we know, and much more that we can reflect upon of what's worked and what hasn't—and the authors here do all that, and more." —From the Foreword by Grady Booch, IBM Fellow

Software architecture—the conceptual glue that holds every phase of a project together for its many stakeholders—is widely recognized as a critical element in modern software development. Practitioners have increasingly discovered that close attention to a software system's architecture pays valuable dividends. Without an architecture that is appropriate for the problem being solved, a project will stumble along or, most likely, fail. Even with a superb architecture, if that architecture is not well understood or well communicated the project is unlikely to succeed.
Documenting Software Architectures, Second Edition, provides the most complete and current guidance, independent of language or notation, on how to capture an architecture in a commonly understandable form. Drawing on their extensive experience, the authors first help you decide what information to document, and then, with guidelines and examples (in various notations, including UML), show you how to express an architecture so that others can successfully build, use, and maintain a system from it. The book features rules for sound documentation, the goals and strategies of documentation, architectural views and styles, documentation for software interfaces and software behavior, and templates for capturing and organizing information to generate a coherent package. New and improved in this second edition:


Coverage of architectural styles such as service-oriented architectures, multi-tier architectures, and data models
Guidance for documentation in an Agile development environment
Deeper treatment of documentation of rationale, reflecting best industrial practices
Improved templates, reflecting years of use and feedback, and more documentation layout options
A new, comprehensive example (available online), featuring documentation of a Web-based service-oriented system
Reference guides for three important architecture documentation languages: UML, AADL, and SySML


Want to learn more information about Documenting Software Architectures: Views and Beyond (2nd Edition)?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...