Yes, it is really that good." "This is going to be my 'go to book' when I've had a bad day!" Please Note: Some profanity, not for children!

    sed, awk, and regular expressions allow programmers and system administrators to automate editing tasks that need to be performed on one or more files, to simplify the task of performing the same edits on multiple files, and to write conversion programs.The sed & awk Pocket Reference is a companion volume to sed & awk, Second Edition, Unix in a Nutshell, Third Edition, and Effective awk Programming, Third Edition. This new edition has expanded coverage of gawk (GNU awk), and includes sections on:An overview of sed and awk's command line syntaxAlphabetical summaries of commands, including nawk and gawkProfiling with pgawkCoprocesses and sockets with gawkInternationalization with gawkA listing of resources for sed and awk usersThis small book is a handy reference guide to the information presented in the larger volumes. It presents a concise summary of regular expressions and pattern matching, and summaries of sed and awk.Arnold Robbins, an Atlanta native now happily living in Israel, is a professional programmer and technical author and coauthor of various O'Reilly Unix titles. He has been working with Unix systems since 1980, and currently maintains gawk and its documentation.

    High-profile projects such as the Linux Kernel, Mozilla, Gnome, and Ruby on Rails are now using Distributed Version Control Systems (DVCS) instead of the old stand-bys of CVS or Subversion.Git is a modern, fast, DVCS. But understanding how it fits into your development can be a daunting task without an introduction to the new concepts. Whether you're just starting out as a professional programmer or are an old hand, this book will get you started using Git in this new distributed world. Whether you're making the switch from a traditional centralized version control system or are a new programmer just getting started, this book prepares you to start using Git in your everyday programming.Pragmatic Version Control Using Git starts with an overview of version control systems, and shows how being distributed enables you to work more efficiently in our increasingly mobile society. It then progresses through the basics necessary to get started using Git.You'll get a thorough overview of how to take advantage of Git. By the time you finish this book you'll have a firm grounding in how to use Git, both by yourself and as part of a team.Learn how to use how to use Git to protect all the pieces of your project Work collaboratively in a distributed environment Learn how to use Git's cheap branches to streamline your development Install and administer a Git server to share your repository

    You’ll learn how to create structured JavaScript applications, using Backbone’s own flavor of model-view-controller (MVC) architecture.Start with the basics of MVC, SPA, and Backbone, then get your hands dirty building sample applications—a simple Todo list app, a RESTful book library app, and a modular app with Backbone and RequireJS. Author Addy Osmani, an engineer for Google’s Chrome team, also demonstrates advanced uses of the framework.Learn how Backbone.js brings MVC benefits to the client-sideWrite code that can be easily read, structured, and extendedWork with the Backbone.Marionette and Thorax extension frameworksSolve common problems you’ll encounter when using Backbone.jsOrganize your code into modules with AMD and RequireJSPaginate data for your Collections with the Backbone.Paginator pluginBootstrap a new Backbone.js application with boilerplate codeUse Backbone with jQuery Mobile and resolve routing problems between the twoUnit-test your Backbone apps with Jasmine, QUnit, and SinonJS

    The aim of The Node Beginner Book is to get you started with developing applications for Node.js, teaching you everything you need to know about advanced JavaScript along the way on 59 pages.

    You will learn how to create notes, how to create stacks, how to set up a hierarchical structure for tags, how to create virtual genealogy binders, easy ways to transfer your computer files into an Evernote Note, and more. You will be able to follow each step to create your own Genealogy Binders full of your research (documents, photos, audio files, and more) on all your ancestors. Your Genealogy files will be organized, easily accessible and readily available to share with others if desired.

    Together, they ruled big business. They transformed popular culture. And they provoked a national controversy. More than anything, they lived a unique and rollicking American Dream, escaping the broken homes of their youth to produce the most notoriously successful game franchises in history—Doom and Quake— until the games they made tore them apart. This is a story of friendship and betrayal, commerce and artistry—a powerful and compassionate account of what it's like to be young, driven, and wildly creative.

    The RESTful approach to web services design is rapidly become the approach of choice. Unfortunately, too few people have truly solid REST API design skills, and discussions of REST can become bogged down in dry theory.The REST API Design Handbook is a simple, practical guide to aid software engineers and software architects create lasting, scalable APIs based on REST architectural principles. The book provides a sound foundation in discussing the constraints that define a REST API. It quickly goes beyond that into the practical aspects of implementing such an API in the real world.Written by cloud computing expert George Reese, The REST API Design Handbook reflects hands on work in consuming many different third party APIs as well the development of REST-based web services APIs. It addresses all of the debates the commonly arise while creating these APIs. Subjects covered include:* REST architectural constraints* Using HTTP methods and response codes in an API* Authenticating RESTful API calls* Versioning* Asynchronous Operations* Pagination and Streaming* Polling and Push Notifications* Rate Limiting

    This book presents all the important test design techniques in a single place and in a consistent and easy-to-digest format. An immediately useful handbook for test engineers, developers, quality assurance professionals and requirements and systems analysts, it enables you to: choose the best test case design; find software defects in less time and with fewer resources; and develop optimal strategies that help reduce the likelihood of costly errors. It also assists you in estimating the effort, time and cost of good testing. included, helping you to fully understand the practical applications of these techniques. From well-established techniques such as equivalence classes, boundary value analysis, decision tables and state-transition diagrams, to new techniques like use case testing, pairwise testing and exploratory testing, the book is a usful resource for testing professionals seeking to improve their skills and a handy reference for college-level courses in software test design.

    It’s helpful for learning Agile and Scrum, and also for a basic preparation for the PSM I exam (Professional Scrum Master level 1). It can also act as a simple reference for Scrum practitioners.

    This book helps you use SQL and Excel to extract business information from relational databases and use that data to define business dimensions, store transactions about customers, produce results, and more. Each chapter explains when and why to perform a particular type of business analysis in order to obtain useful results, how to design and perform the analysis using SQL and Excel, and what the results should look like.

    Each lesson is followed by list of key concepts and sample questions to help you study for your ITIL(R) Foundation certification exam. Chapter review questions, modeled after the real exam questions, reinforce your learning for each unit.Written by an ITIL(R) Expert trainer who has taught thousands of students and hundreds of organizations, "Foundations of IT Service Management with ITIL(R) 2011" provides a reader with the introduction to this approach to IT services without the expense of a formal classroom course. While the focus is primarily on providing information required to pass the ITIL(R) Foundations exam, this book goes beyond those basics to also provide a real understanding of ITIL(R) to further your knowledge and abilities as a valuable part of IT/business alignment. Using a case-study approach, real issues are discussed that represents challenges experienced by almost every IT organization.Everyone prepares for the ITIL(R) Foundation certification exam in different ways. Accompanying the book are numerous study aids to support your study preparation on the supporting web site. Whether you are new to IT or a seasoned professional, this book is one you need to aid in your quest for certification.Included in your purchase is access to the online study resources including:- Exercise guide- Audio "learn while you drive" reviews- Sample exams- Exam syllabus- PDF version of the "100 ITIL Exam Questions" bookCompanies in all industries are requiring ITIL(R) Foundation as a minimum requirement for their staff. Whether you are entering IT for the first time or switching jobs, ITIL(R) Foundation certification is a step toward your desired career.

    While there have been attempts to establish one standard or another as the default, there is no common agreement. So beware people telling you there is one right way, they are assuming too much. As a general rule though, netiquette involves the same principles as plain old etiquette -- basic courtesy, respect and ethics. Treat people the way you would want to be treated yourself. By following the principles outlined below, the recipient of your email will be more likely to read and act, if not be favorably impressed by your message:Subject line to summarise the message. Make the Subject line summarise the body of the e-mail. Ask yourself, 'will the recipient(s) know what this e-mail is about'. For example, Instead of Subject: Exam, say Subject: Location of 1508INT Exam, 23 July 2011.Don't assume the recipient knows the background. Include enough contextual information at the beginning of the e-mail for the recipient to know what the matter is about. If in doubt, put background information in. For example, don't say can I have an extension for my assignment?, instead say I refer to the CIT3622 assignment 1 that I handed in late. I was ill and have a doctor's certificate. May I ask for an extension on the basis that I was too ill to do it on time?Keep it concise. Keep messages brief and to the point, but not so brief that it causes the problem outlined in the previous point. This includes deleting any irrelevant text when an email has been back and forth several times. No-one wants to scroll down through pages of text in order to reach the message they want to read. If the sense of the email will be lost by deleting that text, however, leave it in.Reply within 24 hours. Try to reply within 24 hours, less if possible. In fact, get in the habit of replying immediately -- it is the polite thing to do, and the recipient will appreciate a prompt reply. It also makes you look efficient. The longer you leave it to reply, the more likely you will forget or have too big a log-jam of unanswered email.Allow time for a reply. E-mail messages are not usually required to be answered immediately, though it is good practice if you do. Before sending a reminder, allow some time for a response, some times even a few days. Not everyone is online 24 hours a day.Use the BCC field when sending bulk email. If you're sending email to a whole list of people, put their email addresses in the BCC field. That way, the privacy of the recipient is respected, and spammers cannot harvest the email addresses for their dastardly purposes.

    The Web is awash in Ruby code that is now virtually impossible to change or extend. This text helps you solve that problem by using powerful real-world object-oriented design techniques, which it thoroughly explains using simple and practical Ruby examples. Sandi Metz has distilled a lifetime of conversations and presentations about object-oriented design into a set of Ruby-focused practices for crafting manageable, extensible, and pleasing code. She shows you how to build new applications that can survive success and repair existing applications that have become impossible to change. Each technique is illustrated with extended examples, all downloadable from the companion Web site, poodr.info. The first title to focus squarely on object-oriented Ruby application design, Practical Object-Oriented Design in Ruby will guide you to superior outcomes, whatever your previous Ruby experience. Novice Ruby programmers will find specific rules to live by; intermediate Ruby programmers will find valuable principles they can flexibly interpret and apply; and advanced Ruby programmers will find a common language they can use to lead development and guide their colleagues. This guide will help you Understand how object-oriented programming can help you craft Ruby code that is easier to maintain and upgrade Decide what belongs in a single Ruby class Avoid entangling objects that should be kept separate Define flexible interfaces among objects Reduce programming overhead costs with duck typing Successfully apply inheritance Build objects via composition Design cost-effective tests Solve common problems associated with poorly designed Ruby code

    Each idiom comes with a detailed description, example code showing the "wrong" way to do it, and code for the idiomatic, "Pythonic" alternative. *This version of the book is for Python 2.7.3+. There is also a Python 3.3+ version available.* "Writing Idiomatic Python" contains the most common and important Python idioms in a format that maximizes identification and understanding. Each idiom is presented as a recommendation to write some commonly used piece of code. It is followed by an explanation of why the idiom is important. It also contains two code samples: the "Harmful" way to write it and the "Idiomatic" way. * The "Harmful" way helps you identify the idiom in your own code. * The "Idiomatic" way shows you how to easily translate that code into idiomatic Python. This book is perfect for you: * If you're coming to Python from another programming language * If you're learning Python as a first programming language * If you're looking to increase the readability, maintainability, and correctness of your Python code What is "Idiomatic" Python? Every programming language has its own idioms. Programming language idioms are nothing more than the generally accepted way of writing a certain piece of code. Consistently writing idiomatic code has a number of important benefits: * Others can read and understand your code easily * Others can maintain and enhance your code with minimal effort * Your code will contain fewer bugs * Your code will teach others to write correct code without any effort on your part