Discover new books on Goodreads

Meet your next favorite book

92 ratings (4.14 avg)
41 reviews

Pablo

Add friend

Pablo’s Bookshelves

to-read‎ (64)
currently-reading‎ (16)
read‎ (91)

did-not-finish‎ (0)
d1‎ (36)
descartados‎ (7)

kindle‎ (6)
d4a‎ (33)
d5a‎ (23)

inbox‎ (2)

Stats | More…

Pablo is Currently Reading

Pablo is currently reading

Viaje del Parnaso

by Miguel de Cervantes Saavedra

bookshelves: currently-reading

Rate this book

Clear rating

1 of 5 stars 2 of 5 stars 3 of 5 stars 4 of 5 stars 5 of 5 stars

Oct 18, 2026 04:37PM

Pablo is currently reading

The Horizon Problem: Por qué fracasan las transformaciones — y qué funciona de verdad (Spanish Edition)

by Michael Kaufmann (Goodreads Author)

bookshelves: currently-reading

Rate this book

Clear rating

1 of 5 stars 2 of 5 stars 3 of 5 stars 4 of 5 stars 5 of 5 stars

progress:

(51%)
— Sep 15, 2026 11:49AM

Sep 15, 2026 11:49AM

Pablo rated a book it was amazing

Open and Async: The collaborative software development playbook for remote and distributed teams

by Ben Balter (Goodreads Author)

bookshelves: currently-reading

Rate this book

Clear rating

1 of 5 stars 2 of 5 stars 3 of 5 stars 4 of 5 stars 5 of 5 stars

Pablo said: " The book I would love to read when I joined GitHub, or earlier when I started working remotely, or earlier when I started at the software industry. The book that every new Hubber should be given the very first day of onboarding.

It tells the origin of The book I would love to read when I joined GitHub, or earlier when I started working remotely, or earlier when I started at the software industry. The book that every new Hubber should be given the very first day of onboarding.

It tells the origin of inner-source, how to build proprietary software the way open source software is built, bringing the practices that worked for people who never met in person, who doesn't speak the same language, who have few or no overlapping of working hours.
Then why not applying these concepts to company management? To any other activity you organize, say a conference? Ben does it applying his technical background, and I love all his metaphors, e.g. meetings are like synchronous blocking calls in code, or you're building the operating system for your team.

Ben makes a great work at identifying the core principles, which are condensed even on the title: Open and Async. Once you read the book, the 3-word title is a pointer to every concept on it, like the 3 first words of a song you've memorized, all makes sense now. And it works better because this is not dark magic. This is something you already do when contribute to open-source, when planning with friends (WhatsApp groups, rare calls, meetings for fun) and with tools you're already familiar with, so it feels so natural.

I'd enjoyed reading the examples and stories which are extracted from real GitHub own history, so nothing speculative there, just real stuff. Disclaimer: I work at GitHub since 2020 though I never worked close to Ben. I've still learnt and enjoyed so much from Ben's distilled experience. This is a playbook on running a company that, as a matter of fact, it's AI ready.

Ben glorifies my old motto: use commit message for the why, the code already says the what and the how, but Ben expands this principle by orders of magnitude to a system of communication. As a side effect, this sets up the org (any kind of org) for the AI, which will find all the documentation in a well structured way.

As a fan of pair programming, I use it very often in an async-first environment,ñ. Ben's thesis is not against pairing, but about not having to pair to make progress, about putting in place other mechanisms to avoid blocking, and then fallback or use or even enjoy pairing when it fits.

There are so many good quotes, but my favorites:
- Async is the operating system; remote is the hardware.
- Share demos, not memos. More prototypes than decks.
- Speak like a human: you can be professional without being formal.
- Chat is for now, issues are for later, email is for outsiders.
- Your hiring process is your culture.
- Without trust, transparency feels like surveillance. Openness without safety is just exposure.
- Open: The best answer is a URL.
- Open: The risk isn't that someone will question your decision. It's that no one will. ...more "

progress:

(71%)
— Jul 18, 2026 10:20AM

Jul 21, 2026 07:52AM · see review

See all 16 books that Pablo is reading…