• Complain

Chris Dawson - GitHub

Here you can read online Chris Dawson - GitHub full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. year: 2015, publisher: OReilly Media, genre: Romance novel. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:

Romance novel Science fiction Adventure Detective Science History Home and family Prose Art Politics Computer Non-fiction Religion Business Children Humor

Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.

Chris Dawson GitHub

GitHub: summary, description and annotation

We offer to read an annotation, description, summary or preface (depends on what the author of the book "GitHub" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.

You use GitHub all day long as a developer. Now learn how to use GitHub as a power user. Learn the ins and outs of the GitHub API using many of the most popular programming languages. Supercharge your development with command line shortcuts. Each chapter digs deep into an important technology from the GitHub ecosystem with examples to accelerate your usage of those features and programmatically automate your developer tools. Along the way, align yourself with the famed GitHub culture to streamline your developer workflow.

Chris Dawson: author's other books


Who wrote GitHub? Find out the surname, the name of the author of the book and a list of all author's works by series.

GitHub — read online for free the complete book (whole text) full work

Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "GitHub" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.

Light

Font size:

Reset

Interval:

Bookmark:

Make
The GitHub Book
Chris Dawson
Ben Straub
Beijing Cambridge Farnham Kln Sebastopol Tokyo Preface In the 1930s The Eagle - photo 1

Beijing Cambridge Farnham Kln Sebastopol Tokyo

Preface

In the 1930s, The Eagle and Child, a pub in Oxford simmeredwith creativity as JRR Tolkien and CS Lewis philosophized and createdtheir fantasy worlds. Heian court life in 11th century Kyoto cradledMurasaki Shibu and produced The Tale of Genji, Japans greatest novel.In the 7th century during the Umayyad Caliphate of modern dayDamascus, glittering Arabic palaces provided fertile ground forthe creation of a new form of poetry, the ghazal (love poems) theinfluence of which still courses through modern Arabic poetry.

Each era of major creative innovation has been backdropped by a uniqueand plumb space where collaboration and creativity flourished. Today,the collaborative gathering space for some of the worlds greatest artists(artists who work as software developers) is a virtual town square, asite called GitHub.

Who You Are

This book should be an interesting source of information for peoplewho have used Git or GitHub and want to level-up their skillsrelated to these technologies. People without any experience usingGitHub or Git should start with an introductory book on thesetechnologies.

You should have a good familiarity with at least one imperative modernprogramming language. You dont need to be an expert programmer toread this book, but having some programming experience and familiaritywith at least one language is essential.

You should understand the basics of the HTTP protocol. The GitHub teamuses a very standard RESTful approach for its API. You shouldunderstand the difference between a GET request and POST request and whatHTTP status codes mean at the very least.

Familiariy with web APIs is helpful, although this book simultaneouslyaspires to provide a guide showing how a well thought out,well designed, and well tested web API creates a foundation for buildingfun and powerful tools. If you have not used web APIs extensively, buthave experience using other types of APIs, this is good company.

What You Will Learn

Much of the book focuses on the technical capabilities exposed byGitHub and the powerful GitHub API. Perhaps you feel constrained byusing Git only from within a certain toolset; for example, if you arean Android developer accidentally using Git to manage your appsource code and want to unlock Git in other places in your life as adeveloper, this book provides a wider vista to learn about the powerof Git and GitHub. If you have fallen into using Git for your ownprojects and are now interested in using Git within a largercommunity, this book can teach you all about the social coding stylepioneered and dogfooded by the GitHub team. This book provides astepping stone for software developers who have used other distributedversion control systems and are looking for a bridge to using theirskills with Git and within a web service like GitHub.

Like any seasoned developer, automation of your tools is important toyou, and this book provides examples of mundane tasks that we thenconvert them into automated and repeatable processes, and we show howto do this using a variety of languages talking to the GitHub API.

If you are unfamiliar with the command line this book will give youa firm understanding of how to use it, and we bet you will find greatpower there. To make this book accessible to everyone, regardless oftheir editor or operating system, many of the programming samples workwithin the command line. If you have hated the command line since yourfather forced you to use it when you were five, this is the perfectbook to rekindle a loving relationship with the bash shell.

If you absorb not only the technical facets of using GitHub but alsopay attention to the cultural and ideological changes offered behindthe tools, youll very likely see a new way of working in the modernage. We focus on these meta viewpoints as we discuss the toolsthemselves to help you see these extra opportunities.

Almost every chapter has an associated repository hosted on GitHubwhere you can review the code discussed. Fork away and take thesesamples into your own projects and tools!

Finally, we help you write testable API backed code. Even the most experienceddevelopers often find that writing tests for their code is achallenge, despite the massive body of literature connecting qualitycode with tests. Testing can be especially challenging when you aretesting something backed by an API; it requires a different level ofthinking than is found in strict unit testing. To help you get pastthis roadblock, whenever possible, this book shows you how to writecode which interacts with the GitHub API and is testable.

First Class Languages You Need to Know

There are two languages which are so fundamentally linked to GitHubthat you do need to install and use them in order to get the most outof this book.

  • Ruby: a simple, readable programming language used heavily by the founders of GitHub.
  • JavaScript: the only ubiquitous browser side programming language, its importance has grown to new heights with the introduction of NodeJS, rivaling even the popularity of Ruby on Rails as a server side toolkit for web applications, especially for independent developers.

Your time will not be wasted if you install and play with these twotools. Between them you will have a solid toolset to beginexploration of the GitHub API. Several chapters in this book use Rubyor JavaScript, so putting in some time to learn at least a little bit willmake the journey through this book richer for you.

Undoubtedly, many of you picking up this book already have familiaritywith Ruby or JavaScript/NodeJS. So, the basics and installation of them are inappendices in the back of the book. The appendices dont cover syntaxof these languages; we expect you have experience with other languagesas a prerequisite and can read code from any imperative languageregardless of the syntax. Later chapters which do discuss a facet ofthe API go into language details at times, and the code is readableregardless of your familiarity with that particular language. Theseexplanatory appendices discuss the history of these tools within theGitHub story as well as important usage notes like special files andinstallation options.

Who This Book is Not For

If you are looking for a discussion of the GitHub API that focuses ona single language, you will be disappointed to find that we look atthe API through many different languages. We do this to describe theAPI from not only the way the GitHub team designed it to work, but theaspirational way that client library authors made it work withindiverse programming languages and communities. We think there is a lotto learn from this approach, but if you are interested in only aspecific language and how it works with the GitHub API, this is notthe book for you.

Conventions Used in This Book

The following typographical conventions are used in this book:

Italic Indicates new terms, URLs, email addresses, filenames, and file extensions. Constant width Used for program listings, as well as within paragraphs to refer to program elements such as variable or function names, databases, data types, environment variables, statements, and keywords. Constant width bold Shows commands or other text that should be typed literally by the user. Constant width italic Shows text that should be replaced with user-supplied values or by values determined by context.
Next page
Light

Font size:

Reset

Interval:

Bookmark:

Make

Similar books «GitHub»

Look at similar books to GitHub. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.


Reviews about «GitHub»

Discussion, reviews of the book GitHub and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.