Autoscaling is a simple concept. Automatically add resources when needed, and automatically shut them down to avoid paying for excess capacity. How hard could that be? If you've set up Autoscaling yourself, you know it's not that easy, especially using the native Autoscalers on platforms like AWS and Heroku. That's why you need JudoScale.
JudoScale is Autoscaling as a service, and they make Autoscaling simple and easy, as it should be. You can use JudoScale on AWS, Heroku, Render, Fly.io, and more. It's free for low traffic apps, and unlimited plans start at $25 per month. Autoscale on Easy Mode at judoscale.com Hello, and welcome to another episode of the Bikeshia, a weekly podcast from your friends at Thoughtbot about developing great software. I'm Sally Hall.
And I'm Joel Kenneville. And together we're here to share a bit of what we've learned along the way. So Joel, what's new in your world? I've been playing a D&D campaign with some of my friends, and this coming week is the grand finale. So I'm really pumped for that.
Nice. I don't know a ton about D&D, but I know that there's like, you campaign kind of has a story in a setting, so where are you playing? Yeah, so this is a collaborative storytelling. So you're, it's not quite like a video game where you're trying to maybe play most optimally, instead you're often trying to play true to character. So it's a little bit closer to improv with the rules than a full-on strategy board game or something like that.
This has been really interesting because I've been playing a character who's all about illusions, which means that unlike a lot of characters where you're like, oh, we're going to fight, and I'm going to like, I'm going to talk to this person. I'm going to cast a fireball. I'm going to do damage. I have to just find really creative ways of doing things through illusions and misdirections that if they work is going to have a big impact, but it really forces me to be sort of creative and on my toes at the table because I can't just be like, hi, sweet, my sword. I have to find something creative to do otherwise.
My impact is nothing. Yeah, because you're going to deliver something after a good sword. Exactly. And if I'm having an off-night and I'm not creative, then a lot of the things I'll do will sort of fall flat. So it's a character type that requires me to really keeps me on my toes as far as the sort of creativity and storytelling and trying to find something that will be plausible.
Yeah, I love how constraints can sometimes improve creativity. Like, I watch a lot of competitive baking TV shows, which is very niche, but often like there'll be one event and then whoever wins gets an advantage, which often translates into like a constraint for everybody else. So like the person who's a love to use chocolate and everybody else has to do the challenge without chocolate. But I've noticed that the advantage rarely actually ends up being that advantageous and it seems like those constraints actually help everybody else be more creative and produce better things. That's insightful.
Do you find that you often get better results in your own work when you have constraints? Well, as a person with ADHD, time constraints are the way to get me to do really good work, honestly. My brain just, you know, there's urgency. I'm going to work a lot harder on it. But yeah, I think in general, constraints can push you to do things you wouldn't necessarily thought about otherwise.
Like recently I've been trying to, instead of deciding a project that I wanted it and then buying yarn for it, I am looking at the yarn already, I already have, I go, what can I make out of this? In some cases, that gets pretty interesting. In other cases, it's just a lot of hats. It almost sounds like a problem inversion, right? Instead of saying, here's the thing I want to make, what do the materials need to be, you're now saying, here are the materials, what should my project be?
Yeah, exactly. It's a thing that I think is usually not productive in software, you know, going, here's a new tool, what can I do with it? I have a problem, I need to solve what's best tool. How can you be a bit of a blessing that occurs, right? They're like, here's a hammer and I'll go find a nail.
Yeah. Sometimes people do like out of left field, really creative things, you're like, wow, I would never have thought to use it in that situation. And maybe that just is fun from a sort of creative expression side of things. Maybe it's actually really useful and unlock something for the rest of the team or community, because no one ever thought to use a tool in that situation before. Yeah, that's true.
But also sometimes you end up with like hype cycles where, you know, there's some shiny new hammer that everybody wants to shove it into every new project. Exactly. What's new in your world? Do you have a shiny new hammer? I wish I had a shiny hammer.
I spent a lot of this morning struggling with parsing imported CSV files in the app or using, which is I feel like an eternal challenge, just because you know, CSV feels like such a simple file format. Until it isn't. Until it isn't until someone sends you a Excel file that they saved a CSV and there's all kinds of encoding surprises. So I've been dealing with that one and I don't know that it would be necessarily possible for anyone to write a parser or like software that uses a parser that can account for every possible way that a CSV is going to be weird. So I'm kind of struggling with like how broad and how careful do I want to be, right?
Like how many different kinds of a weird CSV encoding or whatever else do I want to account for and take into consideration and handle versus, you know, if it's not like this, then you just need to do something different with your file. Do you need to sort of change your processing pipeline to handle it or do you reject it until people look? That's your problem. Yeah, exactly. Considering the user base that we have, I think it's very likely that almost every CSV that gets imported will be created via Google Sheets or Microsoft Excel.
So I think if we can just sort of handle the most common things that will come out of those that will probably be okay. I feel like Excel to CSV exports are notorious for all sorts of weird artifacts and encoding issues. They sure are. One that happens to me a lot is my name. My name has an accent.
Yeah. And oftentimes the encodings get broken when it goes through Excel. And this even happened to be once at a conference where the badge with my name was printed and instead of my letter with the accent on it, I just had some, a few gibberish characters that got printed on my actual conference badge, presumably because all of this had gone through a spreadsheet at some point. Yeah. I am lucky that in this case the data that's in the Excel or in the spreadsheet in the CSV is very standardized.
It's going to be numbers, dates and stock tickers. Okay. There's not going to be accents. I've got some weird date formatting stuff. I'm trying to figure out that I think is actually less the CSV and more of the API reset than the data too.
I know Excel can be weird with dates sometimes and it will sort of try to assume that too many things are dates. So you put in other forms of data in a column and it's just it really wants to believe it's a date and it will try to like transform it. Yeah. I feel like I've seen a lot of memes based on that. It can be pretty funny.
Yeah. So that's definitely a piece of it too. So, and I think the other thing that's really fun is that I'm working on a laptop running Linux for this project. So I don't, and there's like a really lockdown VPN. I don't actually have access to either Microsoft Excel or Google Sheets.
So another fun, pretty constrainable project made me creative. Have you ever tried to debug an issue in production while switching between your air tracker and your log viewer and APM tool? Maybe you know how painful it is when you can see the error but can't find the relevant logs or when you see slow performance but it can't connect to the root cause. Scout monitoring is all in one platform built to make your life easier with log management, performance tracking and error monitoring coming soon. All of your data will be together at last.
We'll go from bug to fix in one place. The result? Less context switching, faster debugging and monitoring that actually helps you ship code instead of distracting from it. No DevOps team? No problem.
Scout works with your existing stack and gives you insights in five minutes, not hours. And bug to fix in one place at ScoutAPM.com. As you're going through this and encountering novel problems, do you find yourself taking down a lot of notes about the thing or like maybe trying to capture some big lessons learned that you'd want to hold on to longer term? I want to be a person who can do that but I have just never been good at taking notes and then remembering that those notes exist or not referring to them. I think the closest I get is sticking out everywhere.
Okay. I have a few different colors and you know there'll be a sticky note for a blog post I want to write or a sticky note for a thing I need to do. I don't like that but that's not as close as I get to taking good notes when I'm starting on the problem. But I feel like this is a thing you're pretty good at or have put a lot of work into developing a system for us. Right?
Yeah, I do a fair amount of it. Not in all areas but what I do have is a longer term, almost like mini wiki that I've created of ideas about software. The ideas are broken down into very small chunks, typically a thesis statement and a paragraph of supporting text, maybe a diagram or code sample. And then they interlink to each other pretty heavily. So oftentimes what I try to do is when I'm faced with a problem and I solve it is to step back and say is there a lesson I can take away from this.
If yes, maybe I can distill that down into something that can fit in that note-taking system. I'm sort of inconsistent about how often I'm adding ideas there. Sometimes I'm adding five or six at a time and then it's a couple of weeks and I don't touch the system and then I come back. But I try to at least be more mindful of the work that I'm doing and trying to extract lessons out of it. What tool do you use for that system?
Because the sort of interlinkingly mentioned sounds very useful but difficult to do with stick hands. The old-fashioned way of doing it, if you're using sticky notes and note cards, is you have a number of systems. So every note has effectively an incrementing idea or something like that. And then when you want to link a card to another one, you just say, you know, see note number and then you give it a number. And then that is how you use sort of cross index.
That's cool. Is that what you do? So I don't do use physical notes. I use a digital system. I use Obsidian as the program but there are others out there as well.
I think it's the sort of newest generation of note-taking apps have pretty much all converged on the idea of hyperlinking notes being a good thing. I'm kind of strict with it though and then I don't put temporary notes, random sort of half form thoughts. You know, I don't put tracking my debugging journey like, oh, remember this function here is branching there. Like all that kind of thing. I might take notes for those things but that stays separate from my sort of mini personal wiki.
Do you have a different system for those or is it just sort of ad hoc writing about what you need to? It is ad hoc. I wish I were more sort of organized and disciplined for those. I will oftentimes create maybe a separate Obsidian fault and just sort of track things down there. Sometimes it's just like a notebook or a scratch pad or something like that.
If I'm going through debugging and I just need to leave breadcrumbs for myself or sort of capture the outcome of what I'm trying to understand. Someone I was working with recently showed me that they had a set up for basically checking every project they've done because we're consulting and we're working on many different projects over time. They had noted sort of like what the project was and what technologies they used and maybe even accomplishments for that time along with dates and so it could refer to sort of like a history of work that they've done, which I found really inspiring and also really entertaining the idea. I felt like that it looked really useful and I don't do any sort of tracking like that. Yeah, I feel like that would be really helpful if you're ever having to like try to go back to lessons learned from a particular situation or even when you're just trying to look back and get a sense of like, oh, what have I done in the last few years?
What is my professional growth looking like? I feel like sort of interview style questions, tell me a time when you had to deal with an outage or something like that. My mind always freezes and I know that I've done a bunch of these but I can't think of a concrete example right now. Yeah, it would be so useful to have a cool up your own little brain record. How do you feel about journaling either for like a sort of work related sort of code stuff or even just like your own personal life?
Is that a thing that you try to do? I have tried it a few times in my life and it's never really stuck. I think I tend to get caught up in like trying to decide the perfect level of detail and how perfect do I want it to be and like I just get really in my head about like what I'm doing instead of just writing things down and then I get frustrated and give up. I have had jobs in the past where we sort of had to do like a pseudo journal of like just a little paragraph about our day at the end of every day. Like the Elon Musk style, tell me five things you did this week?
Yeah, yes. And I think, you know, anytime there's like an enforced system like that, it just kind of ends up being not very useful because you just kind of are checking the box. What about you? Do you do any journaling? I do not.
Don't I do journaling for personal life? For a while, I was keeping TIL doc today. I learned I even had like a Vim shortcut for it so that I could just sort of hit a keyboard command and start typing and then I would add an entry to my TIL doc. I wasn't using that consistently enough. So I think that's sort of the closest thing that approximates journaling.
I know a lot of modern note taking apps. One of the sort of things that became trendy was the idea of a daily note, the act sort of like journaling, but that could be tailored to some sort of maybe reflection at the end of the day. You write down some things and reflections from your day or maybe even throughout the day, you're like, huh, I encountered a new method I never used or like any sort of like little thing like that, which might then allow you to go back and treat that as source material for a bigger idea, something that might fit in my wiki. But I don't do any of that. Yeah.
These are all sort of like note taking as like a long term practice. But what about recording notes and thoughts as you're working through a problem? So less reflecting on it later, but more like I am trying to design a thing or debug a thing. Maybe make a diagram of a thing. Yeah, I do a lot of diagramming as a way to get my thoughts out of my head.
So that's definitely not quite the same thing as note taking, but I think it does hit a lot of the similar values. Do you keep those like, is there a system for storing those and reflecting back on them or using them for future problems or is it sort of an ephemeral? This is helping me now, but there's no archiving. It's a mix. Sometimes it's ephemeral.
Sometimes I will keep copy or screenshot of the diagram if it was particularly interesting to share with other people or to use examples in other situations. I've even done situations where I've created an ASCII version of the diagram and embedded it in my commit message. Oh, that's nice. If it's particularly relevant. It's been a little while since I've used it, but Monodraw is a tool for Mac OS that allows you to just draw shapes and diagrams and ASCII and that makes it really easy to have something copy, paste into a commit message.
Yeah, that's really cool. I'm not doing a diagramming commit message. I feel like sometimes commit messages are actually the closest I got to any sort of journaling. Yeah, that's true. You can look back through your commits in a day and sort of see what happened for better or for worse.
Are you the kind of person that does a lot of work in progress commits, sort of like all the little steps and then maybe like, oh yeah, I've cleaned it up at the end of the day? Absolutely. I remember distinctly like maybe my first or second PR ever when I was working as a developer. I hadn't learned about rebasing or squashing or anything like that and the PR was like dozens of commits that were like, whoops, where again, but generally I, if I'm very frustrated, you know, getting the same error message or something or just can't get something to work and then I get a bit of progress, new error message or something is working a little bit better. I feel like I've got myself pretty well to think of that as a moment to make a commit.
So often if I don't and keep going, I will somehow undo that progress. I just did and not be able to get back to it and be like, I know that 30 minutes ago, this was working. And now I've done something that's not working anymore and I didn't make a commit at that point. So I don't really have a good way other than, you know, control Z and cross my fingers to getting back to what was working before. So I like to do a commit anytime I've got a little bit of progress to celebrate when I'm pairing with someone.
If we have a moment where somebody goes, yay, or oh, it works or something like that I go, okay, commit. Every time I like to commit at the end of the day, but if I don't have a good stopping point or like a progress, but I don't like to walk away at the end of a day with uncommitted changes on my local machine. Is this committing specifically in pushing to another repository? I think the day usually is. Yeah, during the day, if I'm just making little bits of progress, I don't always push that up.
Sometimes I do, you know, if I want to see like, how does this look on CI works on my machine, but that committing at the end of the day is specifically because you're trying to mitigate the risk of, oh, no, my dog at my laptop or something. Yeah. Or I'm unexpectedly out and I can message a coworker and be like, I've got to do that. I've got to branch if you're able to pick it up and keep going, ideally, you know, in a perfect world, the commit would also indicate where I am at what's next. Right.
Right. Yeah. I think it seemed like a teacher or whatever, which is like in case of fire, get commit, get push. I like that. And you know, I've never actually had a building I'm working on catch on fire, but just the idea of like, you know, necessarily know what's going to happen tomorrow.
So you do a lot of little sort of working progress commits throughout the day and that maybe gives you a sense of like what the path was to get to the end of the feature. Do you tend to then squash at the end? Or do you like to keep that journey permanently in the record? I tend to do at least some squashing. I don't find a lot of value in like a string of commits that were like, you know, litter fix or update test with different data or whatever.
If the quits aren't meaningful, I think it's worth squashing. I think if the commits are kind of meaningful as far as like this bit, you know, if I work on a full feature that I might have a commit that is like setting up the migration in the model or commit that is like the controller and the controller is next or something like that. If they represent meaningful, distinct pieces of work, then I think it makes sense to keep the commits. But when it's really just a journey of me struggling and succeeding and then finding a new area and then succeeding and messages that aren't necessarily going to be meaningful to anybody else, I don't feel like I need to keep those. Yeah, I find that I tend to like my history on main to sort of be like, I do want them for atomic and discrete.
Like these commits should be self-contained. But ideally they're kind of as small as they can be in terms of like this adds one little slice of the feature or this is doing every factor that sets up some other work, but it's distinct so that I can just scroll through the commits and see the full story of what's happening in the app. I know a lot of teams like to just sort of keep all the like in progress commits and do merge commits, which can make the history sort of ugly to read. And oftentimes also means that the descriptions are really bad on the individual commits. So you're sort of stuck heading to GitHub and having to read the PRs if you want to get a sense of what was happening.
You can't just get that from the the Git log. Yeah. How often do you find yourself reading Git history? Is that a thing that's like you do often enough to think there's value in all the time? All the time.
I use VS code and I've got an extension that like when you click on a line it will show you what commit it's from. And I find that so, so valuable to be like, this looks weird to me. Why is this weird? It's probably a good reason. And then being able to look at the commit and go, okay, well, this is part of this refactor and this commit message actually explains why this weird thing happened or this commit message doesn't explain why this weird thing happened.
But it does tell me that Joelle did it. So I can go talk to Joelle if he's around and gets some clarity on it. Yeah, I love Git history spelunking. I think of it as a little bit. Yeah.
And then sometimes also going to the PR and seeing the description there and what other files were changed and things like that. I find it so, so useful. So I get very frustrated when a commit doesn't actually say anything meaningful. I think my least favorite is a commit that just has the ticket number. Oh, yeah.
Yeah. And then I can even go to the PR and go to the ticketing system that we work on and see what it was there, which actually brings me to another way kind of like sort of note taking. I guess more documentation in general is like the trail of comments on a ticket or issue that you're working on. I have some thoughts about this. But what are your thoughts about like if you are working on a ticket and you have questions or need clarification, how do you push that?
It depends on I think some of the social norms of the team on a smaller team. Sometimes the best way is just slacking someone. Yeah. And so I typically like to have a little bit more visibility. So I won't DM all maybe in the like team channel, Slack at PM and say, Hey, for this feature we're building in this edge case scenario, what are your thoughts on behavior A versus behavior B and then we have a conversation there that the rest of the team gets to see it.
It's a little bit more immediate than the asynchronous way of doing it on the ticket. It's a little bit then like the context gets lost because it's not on the ticket for someone else to see, but it's a little bit more non blocking for me. And on a smaller team, I think that that pattern works well. And on a larger team or one that's a little bit more process oriented, doing it on the ticket is often the other way to go. I think it also sort of depends where the person you're asking the question of tends to like what apps they live in during the day, right?
Someone who's like, always got your open, constantly working in your app. And that's probably going to be the best way to hear from them. Or if they live in email, right? Yeah. I'm the kind of person who monitors Slack pretty closely, but only checks email a few times a day, which means that my sort of patterns for responding to things are going to be different than someone who's constantly on top of their email.
And then what notifications you have set up, do you get notifications from GitHub every time someone comments on something you're working on? Or do you have to look for those when you're ready to look at them? I do feel strongly though that if you ask, like asking for clarification on something in a space that isn't where you're tracking the work, like I'm just going to say, Jira, but Jira will mean everything, but that's just because I'm using Jira. I always want to go back and then summarize that conversation or at least the outcome of that conversation on the ticket itself, which is for other team members, but it's also very much for me, you know, I'm going to take a long weekend and come back and have absolutely no memory of what the answer to that was.
Or yeah, recently I had, I was halfway through a future when it got deprioritized because we were coming up to a deadline. And so I just dumped everything I could think of about what I had finished and what I hadn't finished and what was still a problem onto that ticket and then moved on to something else and then just picked it back up now. I think I've been three months since I worked on it last. And I was so grateful for those notes I had taken. When there are sort of edge case conversations like that that happened, do you tend to also document that in the commit message?
The like, we considered having the behavior of the X, but we ended up deciding it that we wanted to do why. I do that occasionally. If it's a case where like X seems like they're really obvious way to go, but we did Y instead for good reasons, whatever reasons that seemed good at the time, I think that's what documenting in a commit message. I think when it's more along the lines of like clarifying requirements or straightforward decisions, I find those less useful to copy into the commit message. I find that I'll put oftentimes things where I'm trying to preempt a potential reviewer asking a question.
So like, why are we doing it like this? Doesn't our app normally work like this? Those sorts of things typically make it into the commit message. Absolutely. I think if you're deviating from a convention that's like applied or just industry-wide, I think that's really important to note in a commit message.
So you mentioned the better note taking is the thing that's aspirational for you. What are the aspects that you find are aspirational or benefits you're hoping to get out of it? Because I think people approach note taking with a whole lot of different motivations. Yeah, that's a great question. For me, I think it is remembering things that I've done before.
I use command history in the terminal so often to like try to figure out, I know there's a way to do this and I know the command has this word in it. So I will search my command history to figure out the way that I had done this before. And almost every time that I do that, I think I should really alias this or record it somewhere because you know, your command history is only so long and it's all local and you know, I can't find it. Things that I do just often enough to repeat them but not often enough to remember them. Or things that I learned that I think are worth either sharing with someone else or recording for myself so I don't have to relearn it in the future, for sure.
So for you it's a constant aid for memorization? Yeah, I think it's, yeah, absolutely. I can be very forgetful. I can remember numbers but not tasks and things like that. And I think also to aid in reflection, if someone will ask me like, how's your project going?
I can tell them, you know, this is how I feel about it in the moment. But I would like to be able to have some sort of documentation for like, what has happened, what has been good, what has been frustrating. Because you know, on a day when you just had a really frustrating interaction with a teammate or reviewed a really disappointing PR, it can make you feel like this whole project is garbage. But I know that in reality that one day is overshadowing maybe, you know, three or four weeks of great. And so having like documenting how things are going, I think can give me more, I don't want to say objective, but more holistic or long term view of what's been happening.
I feel like there's also a part of it though, that's like, I just feel like I should take that more. Mm hmm. Yeah, like part of being a cool developer or maybe even just a, you know, adult who's got got it together is taking notes, it's an aspirational thing because it's a marker of having made it. Yeah, yeah. Or it's just like a thing that people do.
When I joined Thoughtbot, I got, you know, first day there's like a little swag, like a sticker and a t-shirt and also a little molesk notebook. And I definitely have teammates who have gone through so many of those since they started. I am six and a half years in and about two thirds of the way through my first one. So in a way it is kind of an interesting reflection of like, like the notes are not super meaningful now. It's more just, I use that when I need to drop something down, but looking back over it, I can be like, oh yeah, I remember that project and then I was like working on that problem or something like that.
But yeah, it almost feels like I'm embarrassed to admit that I have, years written down. Mm hmm. You're not a note taker. Yeah. I feel like I'm sort of one foot in both camps and then I'm not a regular note taker.
I don't feel like I take notes the way a lot of people take notes. But because I have this like mini personal wiki of like deeper software thoughts, it means that I can be in a conversation and slack with a teammate and they mention a problem. I'm like, oh, I have a note about that. Or a couple of notes like a pull together was almost a mini blog post on a lot of different topics, sort of at will. And so that gives that sort of impression of like, wow, you've got something super cool going on and you've really got it together.
Even though like, it does give that impression that is what I believed about you Joel. It's all illusion. That's your D&D character. Taking notes for the illusion of taking notes. So for me, it was a way to help build more intentional growth, do some deeper thinking about software and then build connection between ideas.
And it's turned out that this style of note has been really helpful for building content. Like I said, I can sort of almost throw together a little impromptu blog post on all sorts of topics because I can string together two or three notes that are already written in prose or you have a code example. So that helps me when I'm actually trying to blog, when I'm a conference season and I'm trying to find ideas as a bit to a CFP. And sometimes when I'm trying to put together a list of topics for the mic shed, I'm like, oh, what are we going to talk about next week? I can scroll through some of those notes and be like, oh, that would be a good idea.
Yeah, all of those are places that I, yeah, those are reasons I want to take. You better taking notes because I often, I feel like I have good ideas for blog posts and I'll jot them down or not jot them down. And then when I go to write them, it's like this immense task trying to get my brain back into the context of where it was when I had that thought. I also have never actually spoken at a conference. I've submitted a couple of proposals that haven't been accepted.
And while I was submitting them, I was like, this doesn't feel like the best I can do. But it is the best I can do with what I've got right now. Right, right. I know some people keep a sort of note document of just ideas they got excited about throughout the year so that when conference season comes, they have a list of things they can pitch from. And I guess in that sense, it is a note.
It's different from what I'm doing, but it definitely fulfills a similar function. Yeah, absolutely. Is your collection of notes sort of how you wound up writing a book? I think it helped me to do a lot of content in general and that gave me the confidence to be like, oh, yeah, I could write a book. The inspiration behind writing a book is really just a lot of interactions I had with people when I was spending a lot of time in a few different Slack groups online, helping people out, answering the same questions over and over.
I've also been part of a few mentorship projects and again, answering questions. So the genesis of the book, which for those who have not heard of this before, I'm in the process of writing a book on the fundamentals of web development, focusing on the web platform itself. So not the languages, but understanding how the web works, what are the big ideas and how that impacts what you can build. And so the idea of looking at the web through this platform lens came out of helping people who were stuck, a lot of them more junior and realizing that, oh, there's some pieces missing in this sort of like mental puzzle of how the web works and because that piece is missing, they don't have enough of the full picture to be able to get themselves unstuck in the situation.
Have you found yourself taking a lot of notes or taking notes in a new way as you write the book? Yes. So part of the approach that I use is the idea that any creative work you create is going to have byproducts. So I read a talk, I read a blog post or a writing book. Some things make it into the book and some things are really good, but I have to cut them because they just don't fit the narrative that I'm following in this particular situation.
That's not true. It's really valuable. And so I can recycle it for some other time. But maybe it starts its life as just a note in my noting system. And then from there, it can then grow into something else.
Another form of, I guess, my product that doesn't necessarily get cut, but the book relies a lot on talk about mental models. And so we did an episode a while back where we talked about a few different mental models that I have for answering the question, what is a web browser? What does it do? And so I'll have notes for mental models. Mental models are a thing that I find really powerful and I like to collect them.
And so most of the mental models that are in the book either start as notes in my note taking system or if I discover them while writing, then I'll extract them and put them in my note taking system as well. I feel like we have coming up our first wrap up episode for, I guess, the first seasonal version of the bike shed where we are hoping to recap, look back over the season, talk about things we've learned, ways we've grown, things we've tried and maybe had success or failure with. And maybe something that I could introduce as part of my contribution to that regular episode is just a look back and like, hey, what's one or two interesting ideas that made it into my note taking system over this past season? Yeah, I would love to hear that.
And I feel like that sort of thing is another reason I kind of wish I was better at taking notes. And as far as reflecting on the season, I'll find a way to reflect without the notes that I haven't taken. I think many sort of regular listeners might notice that a lot of things that end up in my notes will often end up as well in when I talk about what's new in my world, because I might have an idea that's percolating in my mind. Like, oh, I'm excited about this mental model or I'm excited about this idea about thinking about uncertainty in programs or whatever the particular thing is. As we wrap up, I'd like to point our listeners to a couple of articles that I've written.
We'll share them in the show notes. One, just about being more self-aware, trying to examine your experience, the work that you do day to day to extract learning out of it. This is something that I do to try to have this sort of continual growth mindset as I'm just doing regular feature work every day. Noting is one part of that, but that's sort of the broader mindset that I use that motivates note taking. So I wrote a little bit about that, this other techniques I share there.
So I'll link to that. And then there's an article where I go more in depth about my personal note taking system and the mechanics of how I break things down and all that. So for all the listeners who are like, oh, you sort of teased a little bit of like a wiki thing, but like exactly how does it work? It's all written down there. So we'll link to that as well.
Awesome. Yeah, I think I've read those before, but I'm excited to go dig into them again. And maybe take some notes. On that note, shall we wrap up? Yep, absolutely.