continuous integration
description: software development practice based on frequent submission of granular changes
106 results
Jenkins Continuous Integration Cookbook
by Alan Berg · 15 Mar 2012 · 372pp · 67,140 words
Jenkins Continuous Integration Cookbook * * * Jenkins Continuous Integration Cookbook Copyright © 2012 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any
…
this to access PacktLib today and view nine entirely free books. Simply use your login credentials for immediate access. Preface Jenkins is a Java-based Continuous Integration (CI) server that supports the discovery of defects early in the software cycle. Thanks to over 400 plugins, Jenkins communicates with many types of systems
…
also appear in the naming conventions, documentation, how the software is designed, build scripts, the process of deploying the software to servers, and so on. Continuous integration forces the defects to emerge early, rather than waiting for software to be fully produced. If defects are caught in the later stages of the
…
, you will need to create an account at the following URL: https://wiki.jenkins-ci.org/display/JENKINS/Issue+Tracking Using a sacrificial Jenkins instance Continuous Integration (CI) servers are critical in the creation of deterministic release cycles. Any long-term instability in the CI server will reflect in the milestones of
…
-built help. See also Global modifications of Jobs with Groovy Scripting global build reports Global modifications of Jobs with Groovy Jenkins is not only a continuous integration server but also a rich framework with an exposed internal structure available from within the script console. You can programmatically iterate through the Jobs, plugins
…
are more than 400. It is likely that there are plugins already available that meet or nearly meet your needs. Jenkins is not only a Continuous Integration Server but also a platform to create extra functionality. Once a few concepts are learned, a programmer can adapt the available plugins to his/her
Iain M Banks - The Culture complete works
by Iain M. Banks · 5,095pp · 1,429,463 words
When the Forest Breathes: Renewal and Resilience in the Natural World
by Suzanne Simard; · 30 Mar 2026 · 430pp · 111,698 words
these connections for thousands of years. Of Rande telling the kids, We are interdependent with the trees. A forest could only be understood as a continuous, integrated living system. My own life and work had shown me the truth of this. Decades of experience had taught me that we needed to shift
Building Secure and Reliable Systems: Best Practices for Designing, Implementing, and Maintaining Systems
by Heather Adkins, Betsy Beyer, Paul Blankinship, Ana Oprea, Piotr Lewandowski and Adam Stubblefield · 29 Mar 2020 · 1,380pp · 190,710 words
confidence in your recovery methods via continuous validation. Recovery involves actions taken by humans, and humans are unreliable and unpredictable. Unit tests alone, or even continuous integration/delivery/deployment, cannot catch mistakes resulting from human skills or habits. For example, in addition to validating the effectiveness and interoperability of recovery workflows, you
…
, the framework can provide out-of-the-box automation for many common development and deployment tasks—from scaffolding for new components, to automated setup of continuous integration (CI) environments, to largely automated production deployments. These benefits have made this framework quite popular among Google developers. What does all this have to do
…
, to reduce the latency between feature specification and deployment. However, Agile workflows typically rely on reasonably mature unit and integration testing practices and a solid continuous integration infrastructure, which require an up-front investment to establish, in exchange for long-term benefits to velocity and stability. More generally, you can choose to
…
will quite possibly be behind schedule and saddled with technical debt. We’ve already touched on alignment between reliability and velocity: investing in a mature continuous integration/continuous deployment (CI/CD) workflow and infrastructure supports frequent production releases with a managed and acceptable reliability risk (see Chapter 7). But setting up such
…
(3)); } Unit tests typically run locally as part of engineering workflows to provide fast feedback to developers before they submit changes to the codebase. In continuous integration/continuous delivery (CI/CD) pipelines, unit tests often run before a commit is merged into a repository’s mainline branch. This practice attempts to prevent
…
describe the process of writing, building, testing, and deploying a software system. These steps include the typical responsibilities of a version control system (VCS), a continuous integration (CI) pipeline, and a continuous delivery (CD) pipeline. While implementation details vary across companies and teams, most organizations have a process that looks something like
…
Matters stages of evolution, Background and Team Evolution-Background and Team Evolution transparency and community engagement, Be Transparent and Engage the Community CI/CD (see continuous integration/continuous deployment) CIA (confidentiality, integrity, availability) triad, Confidentiality, Integrity, Availability Cisco, Risk Assessment Considerations CL (communications lead), Keeping the Right People Informed with the Right
…
, Software Update API tradeoffs, Tradeoffs configuration-as-code, Treat Configuration as Code conformance checks, Example: Microservices and the Google Web Application Framework containers, Use Containers continuous integration/continuous deployment (CI/CD), Initial Velocity Versus Sustained Velocityimplementing verifiable builds, Implementing verifiable builds-Unauthenticated inputs provenance-based deployment policies, Provenance-Based Deployment Policies unit
Zero to Sold: How to Start, Run, and Sell a Bootstrapped Business
by Arvid Kahl · 24 Jun 2020 · 461pp · 106,027 words
from a lot of potential trouble further down the road. Automate the process. You will benefit immensely from removing manual steps from the release process. Continuous Integration, the concept of automating build and tests, makes releasing extremely easy and manageable. This level of automation makes your business more sellable as well: if
…
an ear on the pulse of our community. We screened public forums and groups for complaints and new developments. In the SaaS world, we have Continuous Integration. I think we should also have the concept of Continuous Validation. Regularly and frequently, assess where you are in terms of still being in touch
The Nature of Software Development: Keep It Simple, Make It Valuable, Build It Piece by Piece
by Ron Jeffries · 14 Aug 2015 · 444pp · 118,393 words
, or GoCD. At least one major software vendor was attacked by means of the build environment. The attacker compromised a plugin to the vendor’s continuous integration server. The plugin injected code that targeted a well-known customer of this vendor (relayed in personal communication to the author). This vendor kept its
…
goods. You need an automated build process that creates new images from an upstream base and your local application code. Ideally this comes from your continuous integration pipeline. Be sure to configure timed builds for any application that isn’t still under active development, though. Configured Passwords Passwords are the Brazil nut
…
like to build every commit to master; others require a particular tag to trigger a build.) In some ways, the build pipeline is an overgrown continuous integration (CI) server. (In fact, build pipelines are often implemented with CI servers.) The pipeline spans both development and operations activities. It starts exactly like CI
Essential Scrum: A Practical Guide to the Most Popular Agile Process
by Kenneth S. Rubin · 19 Jul 2012 · 584pp · 149,387 words
. Although Scrum does not formally define technical practices, every successful Scrum team that I have seen employs practices such as simple design, test-driven development, continuous integration, automated testing, refactoring, and so on (see Chapter 20 for additional discussion). Understanding and proactively using these practices will help teams stop adding many forms
…
been continuously developing, testing, and integrating working features every sprint. During each sprint the team members should be using good technical practices such as refactoring, continuous integration, and automated tests to ensure that they can deliver value at frequent, regular intervals without killing themselves. So, within a given sprint we’ll likely
…
to skills that have been in use for decades and are essential to being successful with Scrum or arguably any software development approach—for example, continuous integration, automated testing, refactoring, test-driven development, and so on. Today the agile community refers to many of these technical practices as Extreme Programming (Beck and
…
delivery. See continuous deployment. continuous deployment. Deploying each new feature to users immediately after it is built, integrated, and tested. Synonymous with continuous delivery, integration. continuous integration. A technical practice where members of a single team or multiple teams integrate their work as frequently as is practical. See also integration, technical practices
…
or all of a product to form a coherent, larger-scope work product that can be validated to function correctly as a whole. See also continuous integration. internal stakeholders. Stakeholders who are internal to the organization that is developing the product, for example, senior executives, managers, and internal users. See also stakeholders
…
customers, 308 product roadmap and, 260 Continuous improvement no end state in Scrum, 395 sprint retrospective and, 375 while applying iterative and incremental development, 34 Continuous integration defined, 404 helping work at a sustainable pace, 209 technical practice, 355 use of good practices prevents accrual of technical debt, 149 Contracts, limitations of
…
based in inspection and adaptation, 248 responsibilities of development team, 197–198 sprint retrospective and, 375 sprint review and, 363 Integration of components, 46–47 continuous integration practice, 149, 404 defined, 410 of improvement actions, 391 release train approach (Leffingwell) and, 222 Integration management, technical debt and, 140 Integration tests, 75 Interference
Code Complete (Developer Best Practices)
by Steve McConnell · 8 Jun 2004 · 1,758pp · 342,766 words
of this discussion is adapted from Chapter 18 of Rapid Development (McConnell 1996). If you've read that discussion, you might skip ahead to the "Continuous Integration" section. This simple process produces several significant benefits. It reduces the risk of low quality, which is a risk related to the risk of unsuccessful
…
projects used daily builds at either the beginning or middle of their projects (Cusumano et al. 2003), so this represents a significant opportunity for improvement. Continuous Integration Some software writers have taken daily builds as a jumping-off point and recommend integrating continuously (Beck 2000). Most of the published references to
…
continuous integration use the word "continuous" to mean "at least daily" (Beck 2000), which I think is reasonable. But I occasionally encounter people who take the word "
…
continuous" literally. They aim to integrate each change with the latest build every couple of hours. For most projects, I think literal continuous integration is too much of a good thing. In my free time, I operate a discussion group consisting of the top technical executives from companies like
…
Amazon.com, Boeing, Expedia, Microsoft, Nordstrom, and other Seattle-area companies. In a poll of these top technical executives, none of them thought that continuous integration was superior to daily integration. On mediumsized and large projects, there is value in letting the code get out of sync for short periods. Developers
…
-Level Refactorings, System-Level Refactorings, Refactoring Strategies, Performance, Performance, Recoding in a Low-Level Language, Recoding in a Low-Level Language, Machine Configurations, Backup Plan, Continuous Integration, Continuous Integration, Additional Resources, Laying Out Files and Programs, Laying Out Files and Programs, Laying Out Files and Programs, Laying Out Files and Programs, Laying Out Files
…
of Programming into a Language control structures, Other Kinds of Complexity, Laying Out Files and Programs, Programming Style as Documentation daily build and smoke tests, Continuous Integration data organization, Programming Style as Documentation data types, Guidelines for Creating Your Own Types debugging, Debuggers defects, General Procedure for an Inspection, Debuggers defensive programming
…
and Programs goto statements, gotos if statements, Tips for Using case Statements inheritance, Beyond Classes: Packages initialization, Using Each Variable for Exactly One Purpose integration, Continuous Integration interfaces, System-Level Refactorings layout, Laying Out Files and Programs loops, Correspondence Between Loops and Arrays names, Kinds of Names to Avoid, Programming Style as
…
Constants containment, Find Real-World Objects, Good Encapsulation continuation lines, Using Spaces for Clarity continue statements, Exiting the Loop, Exiting Loops Early, Exiting Loops Early continuous integration, Daily Build and Smoke Test control structures, Binding Time, Binding Time, Binding Time, Relationship Between Data Types and Control Structures, Unusual Control Structures, Summary of
…
, Daily Build and Smoke Test, Daily Build and Smoke Test, Daily Build and Smoke Test, Daily Build and Smoke Test, Daily Build and Smoke Test, Continuous Integration automation of, Daily Build and Smoke Test benefits of, Summary of Integration Approaches broken builds, Daily Build and Smoke Test, Daily Build and Smoke Test
…
build groups, Daily Build and Smoke Test checklist, Continuous Integration defined, Summary of Integration Approaches diagnosis benefit, Summary of Integration Approaches holding area for additions, Daily Build and Smoke Test importance of, Daily Build and
…
Integration Approaches, Summary of Integration Approaches, Summary of Integration Approaches, Daily Build and Smoke Test, Daily Build and Smoke Test, Daily Build and Smoke Test, Continuous Integration, Continuous Integration, Integration benefits of, Importance of the Integration Approach, Benefits of Incremental Integration big-bang, Importance of the Integration Approach bottom-up strategy, Bottom-Up Integration
…
broken builds, Daily Build and Smoke Test checklist, Continuous Integration classes, Importance of the Integration Approach, Benefits of Incremental Integration, Bottom-Up Integration continuous, Daily Build and Smoke Test customer relations, Benefits of Incremental Integration
…
, Integration interface specification, Top-Down Integration, Bottom-Up Integration key points, Integration monitoring, Benefits of Incremental Integration phased, Importance of the Integration Approach resources on, Continuous Integration risk-oriented strategy, Sandwich Integration sandwich strategy, Bottom-Up Integration scheduling, Benefits of Incremental Integration slices approach, Bottom-Up Integration smoke tests, Daily Build and
Tools for Computational Finance
by Rüdiger Seydel · 2 Jan 2002 · 313pp · 34,042 words
, and Moduli Verhulst, F.: Nonlinear Differential Equations and Dynamical Systems Wong, M. W.: Weyl Transforms Xambó-Descamps, S.: Block Error-Correcting Codes Zaanen, A.C.: Continuity, Integration and Fourier Theory Zhang, F.: Matrix Theory Zong, C.: Sphere Packings Zong, C.: Strange Phenomena in Convex and Discrete Geometry Zorich, V. A.: Mathematical Analysis
Docker: Up & Running: Shipping Reliable Containers in Production
by Sean Kane and Karl Matthias · 14 May 2023 · 433pp · 130,334 words
dad, who read to me. And for my wife and daughters, who are my bedrock. —Karl Matthias Foreword Containers are ubiquitous. From local development, to continuous integration, to managing large-scale production workloads, containers are everywhere. Why did this come about, where is it going, and what do you, the reader, need
…
benefits of a standard interface also flow upstream, making the daily lives of developers easier. A single command can produce an entire development environment. Within continuous integration (CI), containers can be easily spun up to house databases, queues, or whatever dependencies your application needs to allow for integration, smoke, and end-to
…
, yet all of these workflows have been forever changed by Docker. This is largely because Docker has significantly altered everyone’s expectations of how a continuous integration and continuous delivery (CI/CD) workflow should function. Instead of each step involving a time-consuming process managed by specialists, most people expect a DevOps
…
production with Docker: Locally build and test a Docker image on your development box. Build your official image for testing and deployment, usually from a continuous integration (CI) or build system. Push the image to a registry. Deploy your Docker image to your server, then configure and start the container. As your
…
with strong testing discipline. With Docker, you can build your image, run it on your development box, and then test the same image in your continuous-integration pipeline before shipping it to production servers. Testing your containerized application is not much more complicated than testing your application itself, as long as your
…
to that than the dependency roulette often experienced by production deployment systems that are not built on container technology. Note If you use Jenkins for continuous integration or are looking for a good way to test scaling Docker, there are many plug-ins for Docker, Mesos, and Kubernetes that are worth investigating
…
Rocket.Chat launching services, Launching Services-Launching Services Chocolatey for Windows, Docker Client, Chocolatey installation chroot Unix system call, History of Containers, Namespaces CI/CD (continuous integration and continuous delivery)Docker plug-ins, Quick Overview workflow with Docker, The Promise of Docker-Benefits of the Docker Workflow client, Important Terminology(see also
…
-certified runtimes used by, Broad Support and Adoption containers (see Linux containers) containers and pods of Kubernetes, Kubernetes containers and pods-Kubernetes containers and pods continuous integration and continuous delivery (CI/CD)Docker plug-ins, Quick Overview workflow with Docker, The Promise of Docker-Benefits of the Docker Workflow control groups (see
Handbook of Modeling High-Frequency Data in Finance
by Frederi G. Viens, Maria C. Mariani and Ionut Florescu · 20 Dec 2011 · 443pp · 51,804 words
In Our Own Image: Savior or Destroyer? The History and Future of Artificial Intelligence
by George Zarkadakis · 7 Mar 2016 · 405pp · 117,219 words
The Cold War: A World History
by Odd Arne Westad · 4 Sep 2017 · 846pp · 250,145 words
Mathematical Finance: Theory, Modeling, Implementation
by Christian Fries · 9 Sep 2007
Site Reliability Engineering: How Google Runs Production Systems
by Betsy Beyer, Chris Jones, Jennifer Petoff and Niall Richard Murphy · 15 Apr 2016 · 719pp · 181,090 words
Building Microservices
by Sam Newman · 25 Dec 2014 · 540pp · 103,101 words
Agile Project Management With Kanban
by Eric Brechner · 25 Feb 2015
Advanced Software Testing—Vol. 3, 2nd Edition
by Jamie L. Mitchell and Rex Black · 15 Feb 2015
Masterminds of Programming: Conversations With the Creators of Major Programming Languages
by Federico Biancuzzi and Shane Warden · 21 Mar 2009 · 496pp · 174,084 words
Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software
by Scott Rosenberg · 2 Jan 2006 · 394pp · 118,929 words
Version Control With Git: Powerful Tools and Techniques for Collaborative Software Development
by Jon Loeliger and Matthew McCullough · 14 Aug 2012
The Practice of Cloud System Administration: DevOps and SRE Practices for Web Services, Volume 2
by Thomas A. Limoncelli, Strata R. Chalup and Christina J. Hogan · 27 Aug 2014 · 757pp · 193,541 words
The Architecture of Open Source Applications
by Amy Brown and Greg Wilson · 24 May 2011 · 834pp · 180,700 words
Beautiful Architecture: Leading Thinkers Reveal the Hidden Beauty in Software Design
by Diomidis Spinellis and Georgios Gousios · 30 Dec 2008 · 680pp · 157,865 words
Seeking SRE: Conversations About Running Production Systems at Scale
by David N. Blank-Edelman · 16 Sep 2018
Chaos Engineering: System Resiliency in Practice
by Casey Rosenthal and Nora Jones · 27 Apr 2020 · 419pp · 102,488 words
Clojure Programming
by Chas Emerick, Brian Carper and Christophe Grand · 15 Aug 2011 · 999pp · 194,942 words
Testing Extreme Programming
by Lisa Crispin and Tip House · 15 Apr 2003 · 448pp · 84,462 words
Machine Learning Design Patterns: Solutions to Common Challenges in Data Preparation, Model Building, and MLOps
by Valliappa Lakshmanan, Sara Robinson and Michael Munn · 31 Oct 2020
Ship It!: A Practical Guide to Successful Software Projects
by Jared R. Richardson and William A. Gwaltney · 15 Mar 2005 · 203pp · 14,242 words
Producing Open Source Software: How to Run a Successful Free Software Project
by Karl Fogel · 13 Oct 2005
From Airline Reservations to Sonic the Hedgehog: A History of the Software Industry
by Martin Campbell-Kelly · 15 Jan 2003
The Making of Global Capitalism
by Leo Panitch and Sam Gindin · 8 Oct 2012 · 823pp · 206,070 words
Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith
by Sam Newman · 14 Nov 2019 · 355pp · 81,788 words
Architecting Modern Data Platforms: A Guide to Enterprise Hadoop at Scale
by Jan Kunigk, Ian Buss, Paul Wilkinson and Lars George · 8 Jan 2019 · 1,409pp · 205,237 words
The Age of AI: And Our Human Future
by Henry A Kissinger, Eric Schmidt and Daniel Huttenlocher · 2 Nov 2021 · 194pp · 57,434 words
The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win
by Gene Kim, Kevin Behr and George Spafford · 14 Jul 2013 · 395pp · 110,994 words
The Volatility Smile
by Emanuel Derman,Michael B.Miller · 6 Sep 2016
Pro Git
by Scott Chacon · 17 Aug 2009 · 282pp · 79,176 words
The Pragmatic Programmer
by Andrew Hunt and Dave Thomas · 19 Oct 1999 · 509pp · 92,141 words
Scala in Action
by Nilanjan Raychaudhuri · 27 Mar 2012
Test-Driven Development With Python
by Harry J. W. Percival · 10 Jun 2014 · 779pp · 116,439 words
Pro Git
by Scott Chacon and Ben Straub · 12 Nov 2014 · 549pp · 134,988 words
Service Design Patterns: Fundamental Design Solutions for SOAP/WSDL and RESTful Web Services
by Robert Daigneau · 14 Sep 2011
Beginning Backbone.js
by James Sugrue · 15 Dec 2013 · 290pp · 119,172 words
Beautiful Testing: Leading Professionals Reveal How They Improve Software (Theory in Practice)
by Adam Goucher and Tim Riley · 13 Oct 2009 · 351pp · 123,876 words
Scale: The Universal Laws of Growth, Innovation, Sustainability, and the Pace of Life in Organisms, Cities, Economies, and Companies
by Geoffrey West · 15 May 2017 · 578pp · 168,350 words
Kanban: Successful Evolutionary Change for Your Technology Business
by David J. Anderson · 6 Apr 2010 · 318pp · 78,451 words
Docker in Action
by Jeff Nickoloff and Stephen Kuenzli · 10 Dec 2019 · 629pp · 109,663 words
Clean Agile: Back to Basics
by Robert C. Martin · 13 Oct 2019 · 333pp · 64,581 words
Solr 1.4 Enterprise Search Server
by David Smiley and Eric Pugh · 15 Nov 2009 · 648pp · 108,814 words
Excession
by Iain M. Banks · 14 Jan 2011 · 298pp · 151,238 words
Ansible for DevOps: Server and Configuration Management for Humans
by Jeff Geerling · 9 Oct 2015 · 313pp · 75,583 words
The Productive Programmer
by Neal Ford · 8 Dec 2008 · 224pp · 48,804 words
Straight Talk on Trade: Ideas for a Sane World Economy
by Dani Rodrik · 8 Oct 2017 · 322pp · 87,181 words
Androids: The Team That Built the Android Operating System
by Chet Haase · 12 Aug 2021 · 580pp · 125,129 words
Kanban in Action
by Marcus Hammarberg and Joakim Sunden · 17 Mar 2014
Demystifying Smart Cities
by Anders Lisdorf
API Marketplace Engineering: Design, Build, and Run a Platform for External Developers
by Rennay Dorasamy · 2 Dec 2021 · 328pp · 77,877 words
Hands-On RESTful API Design Patterns and Best Practices
by Harihara Subramanian · 31 Jan 2019 · 422pp · 86,414 words
Understanding Power
by Noam Chomsky · 26 Jul 2010
Why Europe Will Run the 21st Century
by Mark Leonard · 4 Sep 2000 · 131pp · 41,052 words
Forge Your Future with Open Source
by VM (Vicky) Brasseur · 266pp · 79,297 words
Team Topologies: Organizing Business and Technology Teams for Fast Flow
by Matthew Skelton and Manuel Pais · 16 Sep 2019
Mind in Motion: How Action Shapes Thought
by Barbara Tversky · 20 May 2019 · 426pp · 117,027 words
The Docker Book
by James Turnbull · 13 Jul 2014 · 265pp · 60,880 words
User Stories Applied: For Agile Software Development
by Mike Cohn · 1 Mar 2004 · 270pp · 75,626 words
The Code: Silicon Valley and the Remaking of America
by Margaret O'Mara · 8 Jul 2019
API Design Patterns
by Jj Geewax · 19 Jul 2021 · 725pp · 168,262 words
Principles of Web API Design: Delivering Value with APIs and Microservices
by James Higginbotham · 20 Dec 2021 · 283pp · 78,705 words
Austerity Britain: 1945-51
by David Kynaston · 12 May 2008 · 870pp · 259,362 words
Software Engineering at Google: Lessons Learned From Programming Over Time
by Titus Winters, Tom Manshreck and Hyrum Wright · 17 Mar 2020 · 214pp · 31,751 words
Mastering Ethereum: Building Smart Contracts and DApps
by Andreas M. Antonopoulos and Gavin Wood Ph. D. · 23 Dec 2018 · 960pp · 125,049 words
Designing Web APIs: Building APIs That Developers Love
by Brenda Jin, Saurabh Sahni and Amir Shevat · 28 Aug 2018
Text Analytics With Python: A Practical Real-World Approach to Gaining Actionable Insights From Your Data
by Dipanjan Sarkar · 1 Dec 2016
Real-World Kanban
by Mattias Skarin · 23 Jun 2015
Kill It With Fire: Manage Aging Computer Systems
by Marianne Bellotti · 17 Mar 2021 · 232pp · 71,237 words
Business Metadata: Capturing Enterprise Knowledge
by William H. Inmon, Bonnie K. O'Neil and Lowell Fryman · 15 Feb 2008 · 314pp · 94,600 words
Apache Solr 3 Enterprise Search Server
by Unknown · 13 Jan 2012 · 470pp · 109,589 words
The Fourth Industrial Revolution
by Klaus Schwab · 11 Jan 2016 · 179pp · 43,441 words
Learning Vue.js 2: Learn How to Build Amazing and Complex Reactive Web Applications Easily With Vue.js
by Olga Filipova · 13 Dec 2016 · 292pp · 66,588 words
Working in Public: The Making and Maintenance of Open Source Software
by Nadia Eghbal · 3 Aug 2020 · 1,136pp · 73,489 words
97 Things Every Programmer Should Know
by Kevlin Henney · 5 Feb 2010 · 292pp · 62,575 words
Docker: Up & Running: Shipping Reliable Containers in Production
by Sean P. Kane and Karl Matthias · 15 Mar 2018 · 350pp · 114,454 words
Common Knowledge?: An Ethnography of Wikipedia
by Dariusz Jemielniak · 13 May 2014 · 312pp · 93,504 words
Pragmatic Version Control Using Git
by Travis Swicegood · 1 Dec 2008 · 184pp · 12,922 words
AngularJS
by Brad Green and Shyam Seshadri · 15 Mar 2013 · 196pp · 58,122 words
Programming Scala: tackle multicore complexity on the JVM
by Venkat Subramaniam · 1 May 2009 · 226pp · 17,533 words
The Art of Monitoring
by James Turnbull · 1 Dec 2014 · 514pp · 111,012 words
Clean Code: A Handbook of Agile Software Craftsmanship
by Robert C. Martin · 1 Jan 2007 · 462pp · 172,671 words
The Vanishing Face of Gaia: A Final Warning
by James E. Lovelock · 1 Jan 2009 · 239pp · 68,598 words
The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses
by Eric Ries · 13 Sep 2011 · 278pp · 83,468 words
Programming HTML5 Applications
by Zachary Kessin · 9 May 2011 · 210pp · 42,271 words
Raw Data Is an Oxymoron
by Lisa Gitelman · 25 Jan 2013
Twisted Network Programming Essentials
by Jessica McKellar and Abe Fettig · 15 Mar 2013 · 193pp · 46,550 words
Creating Development Environments With Vagrant - Second Edition
by Michael Peacock · 26 Feb 2015 · 161pp · 30,412 words
Building Web Applications With Flask
by Italo Maia · 25 Jun 2015 · 157pp · 35,874 words
Alive
by Gabriel Weston · 15 Aug 2025 · 177pp · 59,831 words
Ansible: Up and Running: Automating Configuration Management and Deployment the Easy Way
by Lorin Hochstein · 8 Dec 2014 · 761pp · 80,914 words
9 Lessons in Brexit
by Ivan Rogers · 7 Feb 2019 · 40pp · 11,939 words
Architecting For Scale
by Lee Atchison · 25 Jul 2016 · 255pp · 55,018 words
Programming Clojure
by Stuart Halloway and Aaron Bedra · 17 Apr 2012 · 536pp · 73,482 words
Learning Ansible 2 - Second Edition
by Fabio Alessandro Locati · 21 Nov 2016
Puppet 3 Cookbook
by John Arundel · 25 Aug 2013 · 274pp · 58,675 words
Nudge: Improving Decisions About Health, Wealth, and Happiness
by Richard H. Thaler and Cass R. Sunstein · 7 Apr 2008 · 304pp · 22,886 words
Large Scale Apps with Vue 3 and TypeScript
by Damiano Fusco · 16 Aug 2020