About the Bundle
Robots will eventually take your job; this bundle contains the 1 simple trick the robots don't want you to know about.
Or, Gregor and Jay believe you'll enjoy both books, and want to offer them together at a discount.
Either way, you should probably buy this bundle. (before the robots make you obsolete)
Working Effectively with Unit Tests
tl;dr: This book details my strong opinions on the best way to test, while acknowledging alternative styles and various contexts in which tests are written. Whether you prefer my style or not, this book will help you write better Unit Tests.
From the Preface:
Over a dozen years ago I read Refactoring for the first time; it immediately became my bible. While Refactoring isn’t about testing, it explicitly states: If you want to refactor, the essential precondition is having solid tests. At that time, if Refactoring deemed it necessary, I unquestionably complied. That was the beginning of my quest to create productive unit tests.
Throughout the 12+ years that followed reading Refactoring I made many mistakes, learned countless lessons, and developed a set of guidelines that I believe make unit testing a productive use of programmer time. This book provides a single place to examine those mistakes, pass on the lessons learned, and provide direction for those that want to test in a way that I’ve found to be the most productive.
The book does touch on some theory and definition, but the main purpose is to show you how to take tests that are causing you pain and turn them into tests that you're happy to work with. If you're like me and enjoy examples, you can take a (free) look at Chapter 1 right now. The foreword, preface, and first 2 chapters are available within The Sample.
Reviews are available at review.wewut.com.
"I trust Jay Fields' opinions about how to write good programmer tests, and so should you." -- J. B. Rainsberger @jbrains
"Buy this. That is all." -- Dan North @tastapod
"This book is a breath of fresh air! Excellent work! The evolution of a hairy test to something really clean is elegant. I wish more people wrote tests like this. Having a book to point people at will really help." -- Joe Walnes @joewalnes
"I just read through what Jay Fields has so far, and it is looking to be really great. I highly recommend it..." -- Corey Haines @coreyhaines
37 Things One Architect Knows About IT Transformation
A Chief Architect's Journey
This book helps architects, CTOs, and CIOs drive large-scale enterprise IT transformation.
Many large enterprises are feeling pressure from the rapid digitalization of the world: digital disruptors attack unexpectedly with brand-new business models; the "FaceBook generation" has dramatically different user expectations; and a whole slew of new technologies has become available to everyone with a credit card. This is tough stuff for enterprises that have been, and still are, very successful, but are built around traditional technology and organizational structures. "Turning the tanker", as the need to transform is often described, has become a board room-level topic in many traditional enterprises. Not as easily done as said.
Chief IT Architects and CTOs play a key role in such a digital transformation endeavor. They combine the technical, communication, and organizational skill to understand how a tech stack refresh can actually benefit the business, what "being agile" and "DevOps" really mean, and what technology infrastructure is needed to assure quality while moving faster. Their job is not an easy one, though: they must maneuver in an organization where IT is often still seen as a cost center, where operations means "run" as opposed to "change", and where middle-aged middle-management has become cozy neither understanding the business strategy nor the underlying technology. It's no surprise then that IT architects have become some of the most sought-after IT professionals around the globe.
This book supports IT architects with the skills necessary to become effective not just in systems architecture, but also in shaping and driving the necessary transformation of large-scale IT departments. In today’s world, technical transformation and organizational transformation have become inseparable.
Organized into 37 episodes, this book explains:
- The role and qualities of an architect in a large enterprise
- Architecture at enterprise scale
- Communicating to a variety of stakeholders
- Understanding organizational structures and systems
- Transforming traditional organizations
Armed with these insights, architects and CTOs will be able to ride the Architect Elevator up and down the organization to instill lasting change.
Praise for 37 Things One Architect Knows:
"As a Business executive and former CTO, this is an enjoyably readable description of an IT Chief Architect’s role and practical methods of influence. I recommend this book to technical staff aspiring to become Chief Architect or CTO." -- Matthew Rawlings, Head of Middle Office and Operations, Bloomberg LP
"Great architects have battle scars and stories to tell. 37 Things reveals a journey that gives character to Gregor’s battle scars and demonstrates how to achieve architecture awesomeness." -- Alexandre Lopes Global Head of Architecture and Service Design, Zurich Insurance Company Ltd
"Gregor shares his hard-learned lessons about enterprise IT using a witty pen. 37 Things has the potential to become a classic for those who need to understand the forces surrounding the IT function in large enterprises. It deserves to be read by an audience far larger than those working on the inside of IT." -- Einar Landre, Leading Analyst IT, COO CIT DIG, Statoil ASA
The Leanpub Unconditional, No Risk, 100% Happiness Guarantee
Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
See full terms