Tag: book recommendations

  • Vibe coding made less terrifying

    Vibe coding made less terrifying

    It’s been a long time since I’ve felt I like I was hanging on every word of a book.

    I was so done reading about AI. Then I saw that IT Revolution was publishing a new book:

    Vibe Coding: Building Production-Grade Software With GenAI, Chat, Agents, and Beyond, by Gene Kim and Steve Yegge.

    The book isn’t out until October, but I have a few sample chapters of the ebook because I’m on IT Revolution’s mailing list. And I realized that, despite my current dread of all things AI-related, I should read those sample chapters before attending the seminar.

    Wow, y’all. It’s been a long time since I’ve felt like I was hanging on every word of a book. This is one of those books.

    I’ve already added it to my list of books I recommend. And I have a whole list of people, developers and non-developers alike, who I think would enjoy it. (I may be able to get you a discount. More about that later.)

    Skeptical of vibe coding? I sure was, and to some extent still am. Gene and Steve were, too.

    But they are clearly converts, and the book is getting me to rethink my initial impressions.

    Addressing concerns

    Yes, there are serious concerns about writing “real” production code with vibe coding, where you’re not really delving into the code output.

    • Is the coding process itself safe?
    • Is the code it generates secure, maintainable, and extendable?
    • If you don’t understand or even look at the code, how can you be sure there isn’t some terrible problem lurking that will cause major problems once it’s in production? Okay, you can never be sure of that, but it seems so much worse if you don’t fully understand the code.

    It’s clear that the authors of this book are grappling with these same concerns. The chapters where they talk about how to approach vibe coding for better results are still ahead, and not part of the sneak preview! Argh, cliffhanger! 🙂

    Magic and hope

    One of my early takeaways isn’t directly related to vibe coding at all: I finally understood why, after 20 years as a developer, I just didn’t want to write code anymore. The tedious parts have started to outweigh the magic. If you’re feeling that way, too, you’re not alone.

    Vibe coding may be a way for developers to rediscover that magic. It may also be an opportunity for people not trained as developers to discover it too, and to create new software directly.

    The book also gives me hope that the role of the developer, even the junior developer, isn’t disappearing. Changing, yes, that’s inevitable. But they point to other historical moments where people feared the end of our profession, and those moments turned out to be times of growth.

    Learning more

    My thoughts these days are all about the role of humanity for software developers, so I’m interested to see what I’ll learn from Gene and Steve’s session and the conference itself. I’ll report back on my mailing list after the conference.

    Does this Vibe Coding book sound like a good read to you, too? Want 15% off a paperback copy?

    If there’s interest, I will coordinate a bulk order for 15% off for folks on my mailing list. Email me or message me on LinkedIn by 9/28 to let me know if you’re interested.

    Join the mailing list below so you don’t miss a thing!

  • Three books about storytelling

    Three books about storytelling

    I’ve been listening to books on storytelling recently, including three I recommend highly.

    Book 1: How to Tell a Story

    First: ​How to Tell a Story​ is by the team from the Moth Radio Hour. Seek that show out, if you’re not familiar with it. Among the takeaways… strong stories have:

    • A change or transformation. Show how the events of the story changed things, changed you.
    • Stakes. Why should the listener care.
    • A strong start and ending. No “so, yeah” at the beginning. No “uh, well, that’s it I guess” at the end.

    And when telling a story on stage, look for the sweet spot between memorizing and improvising. Know your story arc, what details you want to include or leave out, where you want to speed up or slow down.

    But memorize only the opening and ending. Beyond that, memorizing can make you sound unnatural. And if you lose your place in something you memorized word for word, recovering is hard.

    Neon sign that says "what is your story" glowing in an office window at night.
    Photo by Etienne Girardet on Unsplash

    Book 2: Stories that Stick

    Second, ​Stories that Stick​, by Kindra Hall, provides a framework for how to approach storytelling. Her tips:

    • have a recognizable character,
    • use vivid and relatable details to connect to your audience,
    • bring in genuine emotion,
    • and identify a turning point (the change or transformation mentioned above)

    Stories that Stick then explains how most businesses have four main stories to tell: the value story (what’s the value of the product), the founder’s story (how did it all start), the purpose story (vision and values), and the customer story (testimonials). Each one serves different purposes.

    Given how good those two books were, did I really need another five-star book about storytelling?

    Yes, yes I did.

    I found that the lessons from each book complement the lessons from the others. Combined, they made a powerful course in storytelling. And it sure doesn’t hurt that all three books feature engaging stories as examples.

    But the third book I read, ​Storyworthy​, by Matthew Dicks, might be my favorite.

    Even better: it gave me a rule of thumb that I’m already putting into practice. (I thought I was already following it. I wasn’t.)

    Book 3: Storyworthy

    So many of us were taught to think of an academic style as “good writing.” It’s how we learned to write essays for school.

    Problem is, it can be a little boring.

    In ​the Book Academy​, Luvvie Ajayi Jones encouraged students to ditch the scholarly tone. “Write like you talk,” Luvvie said.

    And sure enough, whenever someone set aside their fancy word choices and just wrote as if they were speaking, their writing came alive.

    I already have a pretty conversational style of writing, so I thought I had this covered. But, in Storyworthy, Matthew Dicks takes this a step further. He calls it the “dinner test.”

    With the dinner test, you’re not just writing like you talk. You’re telling your story the way you’d tell it around the dinner table with friends.

    So now, as I write, I keep going back to imagine saying all this to you. Does it sound like something I’d say? I’m surprised by how often the answer is no.

    Storyworthy recommends another practice I plan to adopt. The author calls it “homework for life.”

    Homework for life consists of pausing at the end of each day for ten minutes to identify any “story worthy” moments that happened during the day. Just jot down enough to remember what the story is. You can also make a note of anything that happened at another time but which you happened to remember in that moment.

    This practice can build a list of stories worth telling, which is great. But even more than that, it can get you to pay more attention to small moments in your life that might be worth remembering.

    Matthew Dicks suggests that since he’s been practicing this habit, he’s had a sense of life not passing him by so quickly. That alone makes it a worthwhile practice for me, even if I never use the resulting list as a source for stories.


    Have you read any of these books about storytelling? Are you incorporating storytelling into your work or your life? What have you found useful when crafting your stories?