Write While True Episode 59: Transcript

listen | subscribe

Transcript made with Whisper and made more readable with ChatGPT. Checked for accuracy by Lou Franco.

Lou: Hi, this is episode 59 of Write While True. Write While True is an infinite loop, and that’s because we think of writing as an infinite game, a game we’re playing for fun and to get better at, like a game of catch. So in each episode, we’ll tell you something we learned about writing, and then we’ll throw you the ball with a writing challenge or a prompt.

This episode is the second episode of season six, where Brian and I will be interviewing other software engineers who, like us, like to write in public. I’m Lou Franco.

Brian: And I’m Brian Hall. Today we’re very excited to be joined by Sandrine Banas, author of The Art of Code: The Surprising Power of Beauty in Software Development. Sandrine, welcome. We’re glad to have you.

Sandrine: I’m glad to be here. Thanks.

Brian: If you would, let’s begin by hearing a bit about how you got into writing as a developer. What made you decide to start writing prose?

Sandrine: As a developer, yeah. Well, I didn’t start writing as a developer. I started writing as a teenager, so it was a long time ago. I wrote diaries, stories, and stuff like that. And I love writing. But as a developer, it took me a really long time to start writing something. I started in 2022 with a French book about our profession.

Why did I start? I don’t know. I just felt like I needed to make sense of my 20 years of experience. I needed to have something concrete, because code is really—software is something temporary, and I wanted to have something lasting. So maybe that’s why I started writing, generally.

Lou: One of the things I was wondering early in the book—and we should actually get into what the book is about, but I just wanted to say one quick thing. You talk about the importance of storytelling in code. And I was thinking when I was reading that, oh, she’s coming at this as a writer, applying writing skills to development, whereas I think of it as applying development skills to writing. So it makes sense that you’ve been writing for so long, because that was exactly the feeling I had when I was starting the book.

Sandrine: Oh, that’s nice to hear.

Lou: Why don’t you give the audience a summary of what the book is about and what it’s trying to do? And then we’ll have questions about how you came to write it.

Sandrine: Sure. The book is built around a simple idea: writing code isn’t just a mechanical task. There’s a creative side to it. And I believe that creativity can make code beautiful. But what’s really interesting about beauty is it’s not just about some personal taste or making code look nice. It has really practical benefits.

In the book, I explore how things like simplicity, clarity, expressiveness, and creativity can help us write software that’s easier to understand, maintain, and evolve. And there are also less obvious aspects, like sustainability, durability, and so on. And a few AI tools, too.

Lou: Right. One of the things you introduce early in the book is the idea of these eight dimensions of beauty, which I think really work well from a structuring point of view, structuring the book. I get, very early on, a map of what I’m about to read. Can you tell us a little bit about how you came to that? Were the eight dimensions something you developed? Did you find them during the writing? Did you come to them first? Have you been collecting these? How did you come up with that?

Sandrine: Oh, that was a long process. Maybe I should start with the idea of the book. It might be simpler to explain.

It was a beautiful fall day, and I think I had a manager saying something like, “Every developer should write code exactly the same way,” like we were all machines. And I was really pissed. So I came out and started to vent by writing something like, “No, code is beautiful. We’re not machines. We’re making stuff. Beautiful code is like art.” And it was just for myself. I was venting.

But then I started to ask myself, “Why do I feel code is beautiful?” And I tried to explain it. It took a really long road. I wrote a few chapters, and that structure was not there. So I pushed those chapters to an editor at the first meeting. After that, he really challenged me, saying, “Yeah, but exactly how would you define it? And could you set qualities to it?” And it’s thanks to him and his relentless questions that I finally formalized my structure. But it was really a long and hard process for me.

Brian: I’m curious if you’re able to share what some of the first were. Actually, if it’s okay for me to just list them for anyone listening—and I do recommend just going to pick up the book—we have several different components in a rosette of beautiful code. There’s storytelling, clarity of intent, sustainability, purity, simplicity, expressiveness, creativity, durability. Where did you start? Were the first two something that came to you immediately? I’m curious about the order in which they arose.

Sandrine: Simplicity, I think, was one of the first. And I really wanted to add sustainability because that was something that really mattered to me. That is something that’s maybe the hardest for some readers. And then expressivity, also. Maybe clarity of intent was one of the hardest, because it was really a hard idea to express: how to make data beautiful as well.

But the complete story of the book was, first, it was more like “Writing Java Can Be Beautiful.” So I had to go from there and find the qualities in all the languages and extract them piece by piece. And it’s not easy to extract because it’s a whole. It’s the mix of all those dimensions that can make something beautiful. So you have to fraction it. It’s not easy.

Brian: No, not at all. That points to something else I wanted to ask about, too. The book maybe centers on Java, but you bring in a lot of other languages. There’s Kotlin, there’s Swift, I believe, Haskell, even a little Python, if I remember correctly. How did you go about choosing the languages that you would use for the examples?

Sandrine: Well, first, I’m a Java developer, so that’s why there’s a lot of Java in the book. And the editor really wanted the idea to reach as many developers as possible. So he asked me to add other languages, and I was more familiar with those languages. So that’s why I picked examples in them.

Lou: Yeah. There are some areas where you go through multiple different examples of the same kind of thing, but in different ways. I think it really helped. Personally, I’m okay with reading a book if I don’t know the language, and I do know Java, so that’s lucky for me. But I found it really useful, because I’m way more of a Swift developer or a TypeScript developer. Seeing, “Okay, so that’s what that thing is,” did help me a lot. And then when it went back to Java, I was fine, because I had learned the syntax.

And I also think one of the things your book does really well is, yes, there’s a programming snippet, and it’s a working piece of code that’s syntactically correct, but the point is something else. You can sort of see what you’re getting at on a different level. Even if you didn’t understand exactly what it did, don’t you see that this first version has lots of opportunities for errors and misunderstanding, and that this next version is quite simple? You talk about the complexity scores, but you can also just see it, even if you didn’t understand it.

So I thought those worked really well in the book. I can’t say I literally went through all the code examples trying to understand them, but I could see the point, which was very good.

Brian: Out of the languages that you’re familiar with, which one do you find naturally lends itself toward beauty, if there is one you could choose? I’m asking this because I thought as I was reading—and I don’t want to start a controversy—but I do not think of Java as a language in which beautiful code is typically written. Although maybe that’s just speaking about my own lack.

Sandrine: Okay, okay.

Brian: It’s okay to say that, then! I just wonder, given the other languages you’ve worked in, are there any that you think naturally lend themselves to beauty? Because I do see that it’s a challenge in Java, though you achieve it.

Sandrine: Yeah. There are some languages that were designed to be beautiful from the start, such as Haskell, I think, which has a really simple syntax. And Java is not a beautiful language because there’s a huge legacy.

And maybe that’s a bit of the point, because it’s not easy to think of something beautiful if the language is as it is. Maybe it’s because Java can be pretty damn ugly sometimes, but you can see the change from ugliness to something beautiful. You can see the gap. So that’s why it’s a great language to demonstrate it. I don’t think you can demonstrate it with a language which is naturally beautiful. You need to show ugliness that way as well.

Brian: I really liked that you shared this almost defiant spirit behind the origin story of the book. It was about saying, “No, no, we’re not machines. No, that’s not how I see it. That’s not how code should be.” I wonder if, in the process of writing, you thought about a particular type of reader, or who the book is really for. Did you think of it in terms of something that should change minds, or are you more targeting people who are already inclined to want to see beauty in code? Have you thought about specifically who the book is for and how it should affect them?

Sandrine: Yeah. Well, I wanted to target all developers, but it was too much. So my editor asked me to focus more on intermediate level, maybe. And I’d like junior developers to be interested as well, but I was a junior once, and I know at that stage you’re more focused, maybe less on beauty and more on surviving.

Lou: I think in the introduction you say something about it being something a mentor could share with a junior, which I also thought put me in that frame of mind while I was reading it. I was thinking, “Oh yeah, this would be a way to show…” Because I do some mentoring, and I was like, “Yeah, this would be something. It’s not just me saying it. Look, it’s in a book.”

Sandrine: I agree. Sometimes it’s hard to explain to a junior why something is not easy to read. Yeah, it’s working, but it’s not maintainable. So with ideas like storytelling and so on, I was hoping I could help some juniors.

Lou: Yeah, I think it definitely will. Maybe with a mentor’s help, I think it would be even better.

One of the things I also noted is that I felt myself nodding while I was reading the book, because I’m very aligned with the content. But it’s so good to have someone who’s thought through it a little. Maybe I’m more reacting from an “I know it when I see it” perspective. I haven’t really given it a lot of thought. But it’s good to have the why, or some next-level thoughts about how to answer a why question, beyond just, “Look, it’s experience. I know it’s right.”

So I really appreciate that part of the book. I liked diving deep, thinking about, “What does expressiveness really mean?” I thought that was a particularly interesting chapter, for example.

Sandrine: Yeah. I’m sure most experienced developers already have those instincts. Maybe they did not formalize them, but they know it by instinct. So it’s maybe more for intermediate or junior developers.

Brian: Or the experienced developer who just needed a language to speak about it. I would recommend it to an advanced developer as perhaps a quick read, but one that gives such excellent structure to a concept. As Lou said, “I know it when I see it,” but if you’d like to be able to articulate it, here it is articulated.

I think it’s interesting how you deliberately chose to focus on intermediate developers, and I think it’s effective at that. When you focus in that way, you do tend to write something that’s still usable to people outside of that target because of the scoping. I don’t know if you found that. Have you gotten any feedback from readers who are outside your target readership?

Sandrine: No, not yet.

Brian: Okay. Well, hopefully soon. I give a heartfelt recommendation.

Lou: Same here, especially as something to talk about with someone else. That’s what I kept thinking while I was reading it: “Oh yeah, this would be a good discussion while I’m talking with another developer about code improvements.”

One of the other things we really want to talk about—and in the last episode we touched on this with Glenn Stovall—is what it means to write books like these in an AI world, a world where people are using agents to write code. And also, just from what the world wants to talk about and read about these days, AI can’t really be ignored.

I had no idea what the answer was to that, because I don’t really want to read AI engineering books. I want to read books like this one that are about things I’m interested in. But what surprised me in the book was that you have an interesting idea for how to incorporate AI into the rest of your book. So I’d love to hear you describe what you’ve done and how you came to that, because I think it was a really interesting solution.

Sandrine: Well, if I’m a hundred percent honest, that was not my idea. When the book was almost finished, the market started to be really about AI, and I don’t think a book can be sold or marketed if there’s not AI somewhere in it. So my editor asked me, “How could you incorporate AI with those ideas?”

And I really tried to think how to answer that. For some dimensions, I found an answer, or kind of an answer. And for other dimensions, like storytelling, for instance, AI was not helpful at all. It’s really horrible at understanding what storytelling means in code.

But it was really an interesting exercise, because it helped me see how you can use AI as a tool to code, but for some dimensions, AI still needs to be guided and has limits.

Lou: So maybe it’s a relief. If there’s some valuable thing in code that it takes a human to do.

Sandrine: Yeah. If you want code to be maintainable. If you don’t care—and maybe that’s where we are going—you generate code while it’s working, and when it collapses in two months, you write it again. If you want code to be maintainable in the long term, I think humans are still necessary.

Lou: Yeah. And I also think if we want to maintain any kind of human in the loop, explainability of the code review or whatever, it would help for it to be beautiful in the ways you’re saying: readable, understandable, clear, simple. All the benefits we get from beautiful code still matter. At least now they do, I think.

Sandrine: I hope so.

Lou: And one of the things that’s available is you’ve taken the various dimensions that could be explained to an agent via a skill, and you make some skills available. Is that right? Alongside the book?

Sandrine: Yes. There’s a Git repository where those skills are.

Lou: I’m actually looking forward to trying them out at some point. I just started something yesterday where I kind of don’t care about the code yet because I’m still exploring. But I was thinking, “Oh, this will be an interesting place to try to see what I can do with those skills.” I’m probably going to try it out next week and see, because I haven’t really read the code yet. But I intend to before I do anything real with it. So it’ll be a fun exercise to try that out.

Sandrine: Of course, the effectiveness of the skills depends on the agent, on the level of intelligence.

Lou: Well, I’m using Claude Code, so I have high hopes.

Sandrine: Let me know.

Lou: It’s kind of interesting. You’ve said a couple of times about the collaboration aspect of the book, your editor. Just so everyone knows, this book has been published by Manning. Manning, if you don’t know it, is a major publisher of tech books. And I assume the editor is someone from Manning that you worked with there?

Sandrine: Yeah.

Lou: Can you tell us how you came to Manning? Tell us about how the book came to be published by Manning.

Sandrine: Well, it’s pretty simple, actually. On their website there’s a link to submit an idea or something like that. And I just sent an email. Since I’m not a famous author, I had a few chapters to prove my point. So it started like that.

Then they contacted me, and it’s not an immediate contract. There are several internal steps. They submit the idea and samples to readers, and they say, “Oh yes, I would be interested in that book,” or “No, I wouldn’t.” And at the end of the process, they gave a green light.

Lou: That’s really interesting. I had no concept that that was even happening. It seems like an excellent process.

Sandrine: Yeah. And I was really impressed while working with them because just before, I had made a self-published book in French, and there was such a huge difference between publishing yourself and working with a publisher. I thought it would just be some editing and proofreading. And no, they challenged a lot of my ideas. They pushed me.

After that, there were beta readers who also challenged some ideas and asked for more explanation, sometimes with contradictory opinions on the same line of the book. So it was hard. It really pushes you as far as you can go to make it the best thing you can possibly make. And that was really exhausting, but interesting.

Lou: Now that you’re saying that, it does feel like—again, I don’t know what it was like before the process—but with all the thoughtfulness of the arguments, you can tell it’s been well tested. By the time it got to me, I definitely felt these were ideas that were thought through completely.

And I will also say that I feel like you’ve maintained your voice throughout. It feels like the kind of thing written by a person with opinions and background and a cohesive point of view. I really enjoyed that part of it, too, just getting to understand you through your thoughts and your writing.

Sandrine: Nice to hear.

Brian: Sandrine, would you tell us a bit more about the writing process? Details like how long did it take? If you’re willing to share a bit about your writing habit, do you wake up and write every morning, or did you write it in long bursts? I think to us that kind of thing is actually really interesting, just how you went about the actual writing of the book, whatever you could share.

Sandrine: Yeah, sure. So I’m not a morning person. I’m at my peak between, I don’t know, 10 p.m. and 2 a.m., when my daughter is asleep.

Brian: Ah, got it.

Sandrine: So that’s the best time for me. And I’m not a native English speaker, so it’s slower for me to write in English. Pretty soon in the process, I estimated my writing speed to know how much I could produce and how fast. And I found out that I had approximately a writing speed of half a page per hour.

Because when you’re working with an editor, you have deadlines. So if I wanted to have finished the chapter by the deadline, I needed to schedule my sessions. And doing that, I discovered that with my writing speed, I needed to write every day. So that was a long process, every day.

And then I discovered another limit. I don’t know if it’s me or everyone, but I have a creative capacity which is limited to approximately two to three hours. I can write longer, but after two or three hours, depending on my day, it takes me twice as long to write something half as good. My creative capacity is going down. So I could write at half a page per hour only two to three hours a day. Using that, I scheduled my sessions to write a few hours each day, if possible, at night.

Brian: So it’s nighttime, you have deadlines, you’re writing a page or two per evening, depending on the time and your energy. I’m curious about the tiniest details, too. Do you write longhand? Do you have a preferred writing tool on your computer? Do you write everything in English from the beginning, or do you write some parts in French and translate? Tell us about your process.

Sandrine: Well, I wanted to use Scrivener, but I discovered that the editor has rules for that, too. Pretty early they told me, “No, this is our template. Use our template.” It’s good, actually, because you immediately write in the format of the page of the book. So you can see almost immediately the end result. That’s nice.

I was constrained by the tool, and I used, in the end, Microsoft Word with the editor’s template. The first chapters, I wrote them in French and translated them. But after a while, I discovered it took too long, and I started writing directly in English because switching from French and the way you think about it makes sentences weird. I don’t know how to—

Brian: Sure.

Sandrine: So I tried writing directly in English, and since it’s not my native language, I did use AI to correct my mistakes. I asked it, “Please make it sound like it’s written by an American.”

Brian: Okay. I think you pulled it off.

Can we talk about my personal favorite part of the book, the chapter on storytelling? I, like Lou, was nodding my head along with a lot of the book. The functional programming stuff, I loved it, but I’m already, I guess, a true believer in that school. But what you wrote about storytelling, I’ve just never thought about code in that way.

And I was surprised earlier when you mentioned which parts came to you first and where you started. I was surprised that wasn’t on your list. So it sounds like that emerged a little bit later in the process. Would you mind, for the listener, outlining how storytelling is a component of beautiful code and talking about how you stumbled upon this framework? Because I think it’s so powerful.

Sandrine: Yeah, sure. Well, it’s been in my mind for a few years now. Programming languages are not for the computer. The computer, you could write in zeros and ones, and it would be perfectly happy. Programming languages exist for humans, for developers, to make the process understandable.

And humans have two modes of thinking. One is pragmatic and the other is storytelling, and it helps us make sense of the world. There’s storytelling everywhere around us, in books and things like that. And it’s the same with code. When you read a piece of code, if you see it as a story, something is happening and there’s a result, success or failure. So it makes code easier to understand.

For instance, there’s an example. I don’t know if it made the final cut or not. I’m not sure because a lot of things have been gutted in the process. It was at least a hundred pages longer initially.

Let’s tell a story of someone who is about to go on a great adventure and do something. And first you have a hundred pages where you explain how he prepares his luggage, what he puts in his luggage, and all the details about this luggage. And when you reach the part of the great adventure, the reader is already lost.

And it’s the same with code. If you start the program with a hundred lines of code where you explain how you check variables, connect to the database, you’ve lost the reader the same way. So you extract those parts of the code into a method that you call “prepare a connection to the database,” or “prepare the luggage.” And like an author who says, “He prepared his luggage and then took the plane,” you just have, for the developer, “prepare the connection to the database” and then “connect to the database.” And you don’t lose the reader in details which are completely useless to understanding the story.

It’s already been explained in other ways, like the level of a method. How you tell the story is just a different way, but it’s already been explained by other books. So it’s another way of explaining the same thing.

Lou: I think the novel thing I saw in the way you were describing it is you also had this idea of common plotlines. So, like, the idea of delivery, the story is, “This is how that one goes.” Where I was talking about how it sounds like you’re applying writing things to programming, that was one of those examples. Because I think it’s something fiction people know about, that there are these archetypal stories.

Sandrine: Yeah. There’s a great book about that. I think it’s mentioned, The Seven Basic Plots by Christopher Booker. I think it took him 20 years or something like that. He read a lot of stories and extracted—and in the end, he said, “If you look at them, there are just seven plots that are repeated in all those stories.” Just like, I don’t know, rags to riches or tragedy or stuff like that.

So I thought, “What about code? What are the stories in code?” And I tried to think about everything I’ve ever written as a mostly backend developer. How many stories can I find? And I was pretty shocked, for the backend part, to find only five stories. So that’s not much. But yeah, 25 years, and I’ve just written five stories over and over and over. So, yeah, I don’t know.

Brian: You do a good job, though. I think one of the things that framing them as stories does is it makes them a bit more dramatic and worthy of attention and care. I think when you think about code that is just cleaning some data to be processed or ingested, I think of that as not very important, not particularly glamorous. But in the book, you make the comparison to the story of Hercules cleaning the stables. And I think you invite the reader to take their code—maybe not take it seriously, but to respect it or something. It all matters. It has its role to fill. I thought that was great. Another recommendation to go read that.

And that, I would say, describes the structure of the book, where here are the components of beautiful code, and then within each component, here are the types of implementations or the problems that you run into or the steps of the process. It’s very modular and broken down and structured in a fractal way. I don’t have a question here. I just wanted to say that I thought it was great.

Sandrine: Nice to know that. I guess you both have a mind for writing and stories because that chapter was the one which had the most reaction by the beta readers.

Brian: Oh, really?

Sandrine: Yes. Some found it really interesting, and others, maybe with a more pragmatic and rigid mind, did not really understand it, I think. So I guess it depends.

Brian: It’s a really hard problem. How did you and your editor go about deciding when to take suggestions or act on reactions from beta readers and when to just say, “Thank you for sharing, but I’m going to ignore that”?

Sandrine: For that part, the editor did not give me guidelines. He just gave me the returns and let me do what I wanted with them. So I was more or less free. And then she reviewed it and every time gave a green light. So I know I talked a lot about how they challenged me, but they also gave me a lot of freedom on that part. So that was great.

Lou: And you end up putting it fairly early in the book, the first dimension that you discuss. And I actually think it belongs there, too, because the whole point of the dimension is telling a story. In a way, there’s a meta and fractal thing happening here, where you have a structure in your book that is also telling a story. And you talk about how to take something that might be big and complex and boil it down into a table of contents and chapters, and chapters have scenes, and so forth. And that’s what you’re also doing in the book.

I felt it was a good place to start. It made me feel like I understood what was going to be happening in the rest of the book. I feel like it works on that level. So I’m glad you kept that in.

Sandrine: I’m glad, too, because I do like that chapter. It’s maybe the one that’s the most personal, I’d say, because expressivity or functional programming is something well known, but this one maybe less.

Lou: Right. That’s why I think it’s novel. I haven’t heard it put quite that way before. I found it gave me a feeling of, “Oh, good, there’s going to be some new stuff in this book.” I was excited to see it. I’ve been around a while, so it’s cool to hear a different idea.

Brian: I think you mentioned cutting quite a lot before the final version. I think you said a hundred pages, maybe. Is there anything you cut that was really hard to cut? I don’t want to say regrets, but any big challenges there?

Sandrine: Well, I mentioned the book is for intermediate developers, but initially I put a lot of stuff to explain to juniors as well. And that was too much. So they said, “No, just choose a target and remove everything just for…” Well, I understand, because intermediate developers don’t want to read explanations about how the code works and why it works. So I cut a lot of stuff like that, but that’s okay.

Maybe what I regret the most is in the first chapters, the first chapter even, there were more stories and explanations about what is beautiful and comparing code to art and painting. And it was too much for the editor, because he explained to me that most of the time readers just read the first few lines, or the first page, or maybe the first paragraph. And you need to explain to them immediately what they will get in the chapter. Otherwise they won’t read it.

So if I went into too many stories instead of jumping into what’s useful in the text, it’s not going to interest the reader. Some of that was good, but I think I will probably share some on my blog or something along the way.

Brian: That makes a lot of sense. But the material that you cut that was oriented toward beginner developers can still be out in the world and can be an on-ramp or an introduction to the book. And then for the stuff that got cut that was just more theoretical or inspirational, absolutely, seems like a good fit. It’s either the book or it’s the book marketing, I guess. So I hope to see that out there in the world.

You said you have a blog. Do you write actively on the blog? And are there any other projects in the works? Just curious.

Sandrine: Oh, I do have a blog, and I don’t think blogs are read anymore. I don’t know what to say.

Brian: There’s a few of us. There’s a few of us, but I’m sure you’re right.

Sandrine: Anyway, my blog was a way to market my first self-published French book. So there’s some stuff in it, but it’s more like, if I want to put something out there, I will put it, but I don’t expect anyone to read. It’s just for my peace of mind. I’ve done it.

Just like the writing process we’re talking about here. There’s some stuff I really wanted to say about how I wrote the book, and I wrote it on the blog because I needed somewhere to rant again.

Lou: And what’s the URL to your blog?

Sandrine: It’s theartofcodebook.com.

Lou: Okay, excellent. We’ll put a link in the show notes there.

Brian: Sandrine, this has been fantastic. We like to close every episode with some sort of a focused tip or suggestion for the listener. And to be clear to the listener, if you’re looking for tips around coding, go get Sandrine’s book. It’s The Art of Code. It’s great.

But we’re speaking specifically about more of a writing-focused tip for somebody who is new to writing, having trouble keeping up with it, trying to reach a greater audience, trying to write in a foreign language, et cetera. Any writing-focused tip that you could share with listeners?

Sandrine: Sure. Well, before your last podcast, I thought about it. And I was initially going to say that it’s important to write regularly, but that’s exactly the takeaway from last week. So I got another one, which I think is just as important.

Don’t put too much pressure on yourself when you’re writing. Not everything you write has to be shared. So at first, you just write for yourself. You focus on writing whatever comes to your mind. And then you will have a first draft, which will probably not be very good. And that’s perfectly fine.

Don’t be afraid to throw in some stupid jokes or make yourself laugh, like what you’re doing. Some of my jokes survived the final draft. And then little by little, you can go back and refine your draft, expand your ideas, fix what’s not working, and polish it up.

It will take a few sessions. You need to make some stops and start again with fresh eyes. So you don’t need to be stressed that you’re not writing something perfect immediately. It takes time. Just write and take your time.

Lou: Well, I agree completely. I’m a big believer in that. And I hope that anyone listening here, after you’re done listening to this podcast, takes out your journal, opens up a file, writes some thoughts down, and doesn’t worry too much about it, like Sandrine is saying. See where it might lead.

Thank you again, Sandrine. We really appreciated you coming on and sharing your ideas and your book. I hope you have a good rest of your week, and thanks, Brian, also. And this has been Write While True, a podcast where we love infinite loops as long as they’re fun.