Julian: 0:00

I think so many of us get into coding and software development and IT and technology in general because we just enjoy it. So many of us just we're nerds. We love problem solving. We love tinkering. We love soldering. We love laying cables. We love coding just because of the joy, right? And that passion. And I don't want people to lose that. Hello and welcome to the Pie Bites Podcast, where we talk about Python, career, and mindset. We're your hosts. I'm Julian Sequero.

Bob: 0:30

And I am Bob Eldibles. If you're looking to improve your Python, your career, and learn the mindset of success, this is the podcast for you. Let's get started. Hello and welcome back, everybody, to the Pie Bites Podcast. This is Bob Eldibles, and I'm here with Julian Sequero. How you going, man? Yeah, man, good. Is this the first time we record in what, like three months? It's ridiculous.

Julian: 0:52

Yeah, a couple of months, and certainly 2026. So happy new year, man. Happy New Year to everyone listening. This is our first episode together this year. We had an episode last week, but we did record that before the end of the year. So this is officially our first episode this year. So I'm very, very excited to be here, kick things off fresh. It's awesome. So um I hope you all enjoyed the break. Bob, do you have a good break? Two weeks, man.

Bob: 1:17

Completely switched off. It's crazy. You're very fortunate. Yeah.

Julian: 1:21

It was it was wonderful. Um, and we we switched off. Like um, everyone, you know, Bob and I, we we always promote switch off when you have a break, switch off when you have a break. But when you have a business like Pie Bytes, sometimes you don't get to switch off completely. You you check your email, you want to look at maybe if there's support cases, if there's uh something happening in the community, something you have to keep on top of. But we didn't even do that, we did absolutely nothing for Pie Bytes over the two weeks, and we're very proud that we didn't because now coming into 2026, we have so much energy and we're excited. We got all these ideas. I mean, we're late recording this. We should have started recording 46 minutes ago, Bob, but we spent 35 to 40 minutes talking about the ideas and new things coming this year. So we're very excited. But the first thing that we want to mention, everyone, aside from saying thank you from be for being here and happy new year, is we want to grow this podcast this year. This is now one of our goals. Uh, we want to grow this, we want to get it in front of more people. We have incredible guests coming up. Uh, Bob and I have so many insights and things we want to share. We're committing to more episodes together. So please, if you have not done so, I'm saying this at the start of the episode intentionally, please subscribe. Whatever app you are using to watch or listen to it, just tap it right now and click subscribe, share it with someone, do whatever you can. The power is in your hands. It costs you nothing but a finger tap to share this with someone who might find it interesting and and might get something out of benefit from subscribing and listening. So thank you to everyone who does that for us on a regular basis. And if you're new here, we appreciate you being here and we can't wait to share more with you.

Bob: 3:05

I got a second ask. Like if you really like the podcast, then please leave a review. Uh, or just reach out to us because we always want to make the show better and we want to make sure that we address what uh what's useful for you, right? So um, if you see certain people in the space and you would like us to interview them, then let us know, right? Or there's certain topics like uh AI, uh Wes and whatever, right? Like Rust, um reach out to us. We want to know uh because then we can we can make this podcast more valuable. Also, yeah, we draw we've drawn the stats and we uh saw that we're a little bit. We had 32 episodes, which you know it's it's it's great, but uh it's it's good enough. But we want to get to 50. So here's some accountability. Yeah, we need to get to 50 this year. What gets like uh uh somebody reminded me uh yesterday that he got the quote from us uh from Peter Drucker, right? Like what gets measured gets managed. So it's yeah, we always say that, and that's true, right? Like we stopped measuring and we got 60 percent of what we usually do, which is 50.

Julian: 4:09

So yep, and the the old mindset stuff, right? And and productivity and habits and all those things we always talk about on this podcast as well. We stopped the habit. We had a habit in 2024 of recording every Tuesday. Tuesday was our recording day, and we dropped that in 2025 because of time zone differences. You know, Bob, you and I working on slightly different things sometimes. Uh, it just kept falling off as a priority. And so we had probably more episodes with guests in 2025 than with you and me. So we want to make sure we at least find some balance there. Yeah, yeah, way more. Yeah, so more balance this year. That's that's number one. Yeah, yeah.

Bob: 4:49

And number two is uh we probably need to uh read James Clear's uh atomic habits again, and right.

Julian: 4:56

Yeah, let's let's make we gotta make more time for that. Exactly.

Bob: 4:59

I mean to our defense, the time zone is no joke, right? Like it's uh in in our winter, in your summertime, it's 10 hours. So that's I will say that to our defense.

Julian: 5:08

Yeah, hey, it's uh almost 9 p.m. here in Sydney instead of chilling out on the couch and relaxing the cold drink because it's like 30 degrees at the moment. Uh, I'm standing here under a hot lamp recording a podcast with you. So yeah, takes effort. Um, all right, so let's let's move on. We've we've talked about that. The next thing we want to talk about was just quickly, Bob, you know, the holidays. We had two weeks off. Just because we switched off from the business doesn't mean we switched off from technology, learning, growth, all that stuff. What's um, if you were to say one thing that you did over the holiday um that you want to share, what was that?

Bob: 5:49

A lot of quality time at family, which was really great, right? And of course, when I'm not coding, then uh I'm I'm defaulting to to reading and books, right? So uh I'll well I'll have the books at the end, I guess, of the episode. It was really good too, just uh just focus on the reading. And I almost did no coding. Uh I think I did one or two, I think one vibe coding session, and that was that was great as well, right? So um yeah, and for the rest I cannot honestly remember. I I prioritized the gym, so I did the daily workout, and I'm still on track with that. Um yeah, and it was we we we haven't even met like over the break. It was we were going to play chess. Uh didn't happen, so we were really uh uh disconnected and focused on our families. Um I did play a lot of chess with my daughter, which is great, and she's now winning. That's cool. That's that's that's amazing. So I need to up my game.

Julian: 6:45

Yeah, I love it. I can imagine the way she'd be cheering every time she beats you as well.

Bob: 6:51

It's it's it's painful. Uh no, I love it because that that's just awesome, right? Yeah, it's good. It's good with that, right?

Julian: 7:00

So this the student becomes the teacher, yeah.

Bob: 7:03

Yeah, exactly. Yeah, so it's just literally teaching me like moves and sound like uh this is cool.

Julian: 7:08

That's awesome. We gotta play. We gotta play. That's awesome, man. Love hearing.

Bob: 7:13

You can expect more resistance because now I'm I'm learning from the master, right?

Julian: 7:17

Yeah, that's true. That's true. Yeah, I was bummed that we didn't get a chance to play. I mean, every day that we went to meet up to to talk, it was like, oh, just I'm here with the kids or you're out with the family. Yeah, but that's good. I'm glad that you switched off from technology and had one coding session, which you know you weren't prepared for. You you were preparing to code every single day a little bit just for fun, and you almost did none, which was fantastic.

Bob: 7:41

Happy I did I do want to drive home that point, right? Like, like taking a break, or like it doesn't have to be Christmas or anything, right? Like, even if you do like a weekend break, you always find this with weekends as well, right? Like, uh okay, two days you don't do anything, but it's it's one step back, but then you come back and your week will just be so much more productive. So it's one step back, two steps forward, right? So um I see a lot of people stressed out and they they just constantly working, right? Like this this workaholic thing. Um, but it it there's just a diminishing return, right? Like, and and yeah, the recharge is so important.

Julian: 8:14

Absolutely, absolutely, and we both come back feeling that as well, which is good. You me. Um, you me? Yeah, that's me. So I coded these holidays. Um, look, first and foremost, obviously family time. It's summer here for Christmas. So uh for those of you listening, it was poor weather. I got a brand new barbecue uh over Christmas, so we cracked that out at New Year's, had a great party, and it was just wonderful. I did so much socializing locally, close to home, and then mixed in with just days of not leaving the house. And it was beautiful. We had a wonderful time with the kids, we're in the swimming pool every day, we played board games, Pokemon Monopoly, Pocopoly, Pokemonopoly, whatever you want to call it. It was it was great. We we just had a great time. It was awesome fun to switch off. Um, but you know, as you do, you want time for yourself to do certain things that you want to do, work on your hobbies, your projects. So, you know, I worked on a couple little tech projects around the house. I uh rack mounted a Cisco switch in the garage, but probably the big thing I did was I vibe coded. And man, I was coding almost every single day of the holidays, and I don't get to code very often, right? Because of the the roles that we have at Pie Bytes. And I have to tell you, I really wanted to experiment with vibe coding because we have so many people who listen to this podcast, who email us, who get on calls with us in our community, who are playing with you know the different vibe coding bits of software out there. And I'm not talking about the extreme depth of clawed code and uh lovable.dev and all those things. I'm talking about just using Gemini and saying, hey, I need this, write me this code. And if I can count it up all the hours I spent on this app that I'm building, probably five hours, I think, is all I spent on it, accumulated, maybe a bit more. But this app is launched, it's deployed, it's 95% done. And I'll announce it when it's when it's ready. Yeah, you still need to send me a link. Oh, you're gonna I gotta add you to the repo. Sorry, I forgot about that. But um the the beauty and the thing that I really realize, and this is a great segue as we move into the next topic of this podcast, which is you know, what should you be thinking about in 2026? So, all of you listening to this, here is what we think you should be listening to and thinking about and pondering and um weighing up in this year, right? And we know AI is going to be that topic. There are people who hate hearing about AI, and you're probably burnt out like we can be sometimes, but it is here and it is relevant to your livelihood and your well-being. So you can't ignore it, right? Um and from this experience of vibe coding over the holidays, I realized that having a technical background, having built a Django app before, having an understanding of the app that I was building from a code perspective, and merely using the LLM to generate code that I could have written but would have taken days and days to do because I would have had to consult that bit of documentation, go to my old repo. Ah, just remind me what's the correct syntax for this class or this whatever, right? Um it just did it for me. But I had the knowledge for most of it to be able to say, okay, that's correct, or that's incorrect. Um, or you missed a step. So there were plenty of times where it forgot to migrate, uh, do a make migration at a simple level. Uh at one point it wanted me to push code to production with debug equals true in the Django settings, right? So different things like that it didn't quite manage. But because I have that knowledge or that experience, I could catch it. And this is what I want people to think about this year is that yes, you can push code to AI as a job. Yes, companies will be doing that, but they still need people to fact-check it. They still need people to know how to code and understand what it's spitting out. And yes, there are some companies, such as maybe lovable itself, that use their own tool to generate code actively and they may not even check it. They put agents in place to check the code and test it. But the vast majority of people right now, while yes, they are outsourcing to AI in certain tech companies, Amazon, um, sorry, other companies that you you shouldn't name, um they still need people to be able to understand what it's doing because you can't just blindly trust it. And you shouldn't, because you still need someone to check it. And that's, I think, what you really should be thinking about this year is how can you position yourself to understand the code bases that are that need to be written these days? What is the code that companies are writing? What kinds of tools are they using? What stacks, what frameworks, how can you learn that inside out? Show that you know how to write it and read it from an AI, and that and that you might have to vibe code an app and show that you can you can access it and use it um to be able to stay relevant in the industry. You know, I think that's something that for better or worse, as forget morals, forget morality, um, and humanity. I think there's just something you have to do to stay relevant these days.

Bob: 13:46

I agree. Um, I think a lot of this is actually timeless, right? There will be new frameworks, there will be old frameworks, we still be using Fast API, we still be using Django, whatever, or the data science frameworks, right? Or tools. Uh it's just that we can go so much faster, right? So the expectancy might be that you ship faster and more, right? Um, but yeah, um a lot of solutions can be sand castles, right? Like they will be washed away with with the tie, right? So you need to still make sure that you write uh quality code, maintain maintainable code, uh, write tests, um, automate your CI, CD pipelines and all that, right? So yeah, uh you were successful because you already had you did Django before once or twice, right? And um and you probably had very detailed prompts. And that's the other thing, right? You didn't you can only use these tools uh efficiently, effectively if if you have proper prompting, right? And you put in that effort to make good prompts and and iterate step by step. Like one of the pitfalls is to have it do too much for you and then it becomes a mess, right? And uh so you need small iterations. So yeah, it's uh it's very interesting. Um yeah, it's it it basically it changes a lot how we write software, right? Um but at the end of the day, it's just a more potent uh tool set, um, but you still need to have the knowledge and the patience and the debugging skills and the the the craft mentality, right, to write tests and and to ship quality quality work, right? So um a lot is the same, different tool set, same morale, same care little job.

Julian: 15:39

Just a quick break. Let me ask you a question. How much of your last pull request did you actually write? And how much did AI write? If Copilot or Chat GPT disappeared tomorrow, would you still know how your code works and could you explain it in a code review? This is the problem we hear about the most from developers like you who reach out to us for a chat. And PieBytes, our Pybes developer mindset program helps you become the developer who uses AI effectively, not the one who is completely propped up by it. Through a one-to-one coaching, real-world projects, and proper code reviews with an expert coach, not AI, you'll actually understand the Python code that you ship. If you're tired of feeling like a prompt engineer instead of a real developer, check out and apply for PDM using the link in the description. Now back to the episode. And I think you shared uh you shared a post with me from Charlie Marsh today on Twitter. Um actually you you share what what was it that he said in the the Twitter post?

Bob: 16:45

Yeah, he said something like agents make me so much more productive and faster, but it also takes away the joy of the work, right? And I'm I'm I really resonate with that because there are now two ways I I use these tools. So I have the uh what became old in six months uh way of of using um chat interface and then copilot, right? To really go granular and and do a prompt and then copy-paste, iterate, have copilot autocomplete. And I really like that flow because the iterations are much smaller, I'm more deliberate, I'm reviewing it much better, and and I'm just more involved, right? And but I also start to use cloud code, and um, I have built complete features with that, uh, but then it really becomes like prompt and it does all this stuff for you, which is brilliant, right? But it also leads to very big PRs, very a lot of code changes, and it's um you need to have way more discipline and be way more deliberate to then also review it very, very in a very detailed way. So I can definitely see how Charlie C is like, yeah, Cloud Code is it's very it's a very smart tool that can write big pieces of code autonomously, but then also where's where's my job, right? Like we were increasingly becoming the reviewer and the architect and then and the even like the team manager in a sense, because you have like different AI tools work together, right? They might have cloud code, write code, then you submit the PR, you have Copilot, review it, right? So you're you're basically managing a team of agents, right? Um, which which is fun in a sense, but yeah, there's the I can definitely see how the real craft of of building software gets gets lost. Like I I can miss the whole syntax the syntactical level with with you know um, but uh that's already like one level up now. That's that's going uh to be less where you're you you're like if if you're even not putting the pieces together yourself, I can definitely see that that's where the joy then then and then the job satisfaction uh is is going to get lost. Yeah. Yep. So sorry, yeah. So I'm I'm switching between the two, and it depends the thing I'm doing. Like I also use cloud code to try to redo our our our our uh CRM tools, uh front end to uh Django Ninja and React. And that was looked very nice, but it's not working. Uh so I'm going back back and forth between these two modes, right? And I actually enjoy going back to Charlie's quote. I draw more the the smaller increments where yeah, I'm just more in the middle and and uh yeah, yeah. But yeah, cloud code is it's brilliant, it's amazing, but it's it's it's doing too much. I don't know.

Julian: 19:24

It's uh it's yeah, it's to me, it's just where where's the joy? Where's the joy in coding? You know, we're all I think so many of us get into coding in software development and IT and technology in general because we just enjoy it. We have yeah, okay, there are people going to get in for a month for the money, whatever. But so many of us just we're nerds. We love problem solving, we love tinkering, we love soldering, we love laying cables, we love coding you know, scrappy things that do ridiculous things that just because of the joy, right, and that passion. And I don't People lose that. So again, what are you thinking about this year? I think find the joy in coding again and not just defaulting to I need to just use AI for everything, right? Understand the code, get it, enjoy it again. Don't feel like you're being left behind because you won't, because you you won't be. If you understand the code and you enjoy it, when you go for a job interview, you are going to be passionate. You are going to be excited to talk about it. You're going to be able to share. And just naturally, you'll be exposed to an LLM or some sort of AI coding agent, whatever, as you build and grow, right? Um, but yeah, it it is it is just it's sad. It because I the same thing. I love the terminal, I love computer hardware, I love networks, I love um, you know, all the stuff that I used to do in the data center and the um server admin, sysadmin type stuff. I I love that stuff. And so I built the home lab at home so I can keep doing it without working at a company. So what are you gonna do this year to keep up your passion for coding? How are you going to do that? Um, how are you going to incorporate incorporate AI, but not let it take over everything that you do? There's there's a question worth pondering this year, I think.

Bob: 21:16

Yeah. I mean, uh, the rules are pretty simple, right? Like don't have a takeover, understand what you're building, do small iterations, um, still care for the craft, and that comes down to you know writing tests and and and chip quality code, right? And that that's no difference. You should totally use the tools because you can go so much faster. And you can also what a lot of especially experienced developers call out is that these tools are also great at explaining things, right? Or or writing tests. So there's because yeah, they I I'm with you like the craft of coding and we joy, but there's also like the boring stuff, like writing tests is not always that fun, right? And yeah, um, I'm happy to accept boilerplate for that and then tweak it. Yeah, um, and then and then finding joy in the tweaking. That's where I do find joy.

Julian: 22:00

Yeah, yeah. Absolutely. I love it. There we go. Okay, yeah.

Bob: 22:04

So I hope that helps uh navigate this this so this this this this industry trend that it's moving so fast, right? Like it's this dystopian trend.

Julian: 22:16

Yeah, I I know, I and and I hope everyone, you know, one thing I will end on at this point is just things can seem pretty bleak you know in the industry, in the world, whatever, but you've got to find the joy where you can. You've got to find the good in the day wherever you can. I know that seems very uh philosophical, but it's just that's what's gonna get you through the year. This is not gonna be an easy year. 2025 was not the easiest of years for so many people around the world. And so, what are you gonna do to find the good? What's within your control to find the good? And that's um, I think we can all safely, regardless of where we sit on the spectrum, I think that's something we can all take home and and reflect on. So um, all right, so finishing this up, focusing on the one thing and you know, New Year's, all about resolutions, blah, blah, blah, all that stuff, goals and and so on. One thing I'm just gonna ask everyone is what is that one thing you want to accomplish this year? Right? Don't it doesn't have to be the most extravagant extravagant goal of I need to get a promotion here, there, and whatever, right? Um, you can by all means, but what is that one thing you're gonna work towards this year? Um, in the 10 minutes of spare time you might have, what might that thing be? And you know, just sit down, turn off the screens, put your if you're watching on YouTube, Bob's holding up the book, The One Thing. Perfect read. That's your goal. Read the one thing this year. Um sit down, no phone, no screen, don't even type this out. Get a pen and paper, do it old school, pencil and paper if you want to go even further back, and just write out what is it that you want to do this year? What's the one thing you want to accomplish that if you got to the end of the year to December 31st and thought, I got nothing done this year except for this, you would be content. Right? Well, what what is that one thing gonna be? That's that's my challenge to everyone. Yeah.

Bob: 24:17

And let's do a post in a community and we link it, and then if you want to share and chime in.

Julian: 24:23

Well, in the community, there's a here's a nice little plug for the community. It started last January, um, and we're gonna kick off a post this January for it. Um, every month we ask everyone to do a goals check-in. So in January, I asked everyone, what do you want to achieve this year? What are your goals for this year, personal and um business or professional, whatever? And then everyone wrote. We had a whole bunch of people sharing, and every month we did a check-in. And then the months that I started forgetting to create the check-in post, the community picked it up and started creating it. So um, it is really cool that it's got a life of its own. So I'm excited to get that one done for 2026. So we'll do that after this podcast.

Bob: 25:04

Yeah, yeah, forgot about that. You have a monthly thing going there, yeah.

Julian: 25:09

It is pretty cool. It's awesome seeing everyone reach their goals. And you know, some someone was um going for certifications and they were getting them, you know. Other people were talking about giving talks and they did that, you know. Um, it's really cool. And it's and it's a safe space to do it. So if your goals you don't reach them or you choose to pivot and say, Well, that's not happening, I'm gonna change it up, then do it. No problem. So uh very cool. If you want to get involved in that, make sure you join the community and we will have that post coming up coming days.

Bob: 25:38

I want to give a shout out as well to uh Tony Di Pesa. Uh he had a cool post about New Year's intentions and like New Year's resolutions have typically fallen by the wayside about two weeks into two weeks into January. We see that, right? Uh therefore I'm going to try something different this year instead of resolution. I'm making a New Year's intention. And uh I think then he goes on like he's going to use or learn a Python library every month. So yeah, that's uh that's interesting. So yeah, yeah.

Julian: 26:06

Yeah, good idea. I like that, Tanya. And we'll see how that goes. And then we had another request for Pie Bikes books to let people track their own articles and blog posts and as a pro kind of an accountability productivity thing. Leam did that. So yeah, we're gonna have to figure that out now. Yeah. It's very cool. Um, and of course, everyone, if you want to share the wins at your meeting, technically, personally, whatever, we do have a share your win space in the community. We've got uh lately, it's been incredible. People sharing all sorts of apps and um tools that they've built and published on PyPI and all of those things. But um, I I have to mention this a special, very, very special, proud shout out to our very own Sherry, who is our community manager. And she landed a job. She's been working for a nurse, uh she's been working for a hospital as a nurse for 10 years or so, and she's landed a role there as a system developer. So she's coding there, she's doing technical admin stuff. It's just incredible. So she did a coding type test that was take home and all of those things that everyone goes through. And she landed the job and in December and um starting this new year out in the new role. So, Sherry, we're super proud of you. Congratulations, complete grit and determination to get this done. It wasn't an easy year for her on this, and um, but she got there in the end by just sticking with it.

Bob: 27:34

Shows that go, Sherry.

Julian: 27:35

It's all possible if you just stick with it.

Bob: 27:37

So no, definitely consistency.

Julian: 27:39

Yeah, yeah. Love it. All right, so we're gonna wrap this up. This is going on for a super long time, but it's our first episode. We can indulge.

Bob: 27:46

Um well, the books are yes. You want to go first?

Julian: 27:50

We read it, you go.

Bob: 27:52

Okay, so I've read uh vibe coding, not surprising, uh Gene Kim and Steve uh Yeege. Um I might boot for that name. Um, Jim Hodup recommended that, um, who's also um you know our Rust coach. And um, yeah, very really good overview, and just to put this whole vibe coding in perspective, right? Like what is it, how to best do it, um, how to navigate agents, etc. etc. We made a lot of um yeah, uh highlights, and um I'm about to do a post on LinkedIn actually with the lessons learned and stuff. Um, so yeah, really great read um and relevant, timely. And then uh from strength to strength. So I started listening to Tim Ferrer's podcast again. Uh always, you know, world-class performers and uh tangible use usable bits, you know, always get something from that show. And um, yeah, they and it's funny that book was mentioned from strength to strength by Arthur Brooks. And um, I picked it up, and then a day later, uh an episode with him came out, like how like what's that for um what's the word? Serendipity, you know? Yeah, uh, amazing guy, and um yeah, because yeah, I'm uh I've entered my second half of my career, yeah, more or less, right? Like time-wise, and um yeah, it's it's a great read for um you know um to how to navigate that second half better, and how um yes, he distinguishes two types of an intelligence. Um cannot remember the former one, but that's going to decrease. Um, and in the second half, you're going to have more like crystallized uh intelligence, so it comes way more down to the experience of build up and and the wisdom and stuff. So I found that very um useful and also a great perspective how um yeah, we use AI these days and um how to think better and and differently. Yeah, so it was it was a great read, great writing style, and I can recommend it to anybody um I guess over 40, right? When you're going into uh I'll let you know that's almost you.

Julian: 29:58

You can read it in uh whenever you can another year or so. Yeah, yeah, yeah. I'll get there, I'll get there. No, that's cool, man. Nice. Glad you got a great career book.

unknown: 30:08

Yeah, yeah.

Julian: 30:09

That's cool. Um, what did I read? I I didn't read too much, honestly, over the holidays. I I read a third of this giant novel called The Rosefield, uh The Book of Dust, Volume Three, which I've mentioned on a previous podcast episode. It's just it's a long book. So um, but you know, I just I didn't feel it. I came and coded instead, you know. Um, so what I will say instead of that is if you're looking for something to read everyone, um, we'll have a link in the comments. Go ahead and and pick up our uh seven tips to escape tutorial paralysis, seven engineering tips. Um this is something we put together at the end of last year. It's this amazing PDF document kind of e-book thing that just walks you through these seven habits and tips and advice that Bob and I have learned from over the years of coaching people for actually six years now. We've been coaching, and we come across these same trends across every single person, almost every single person. And we distilled that down into this PDF, this document, and it's it's wonderful. So put a lot of time and effort into it. If you're looking for something to read, might take you I don't know, 40 minutes, 30 minutes, depending on how quickly you read and digest. And um, we'll have a link below. You just got to enter your email to get it sent to you, and that's it.

Bob: 31:27

So yep, the feedback has been amazing. Um they they love that that document. How many pages? Like 15 or so, right? Uh yeah, something like that. Yeah. Uh so it's pretty exhaustive and and yeah, based from the lessons we've learned over six years and working with hundreds of people. And um, yeah, it's people have found a lot of value in that. Yeah. Yeah. Nice.

Julian: 31:49

Okay.

Bob: 31:49

And and another talk is the uh private books, right? Like talking about books. And um, so I did um Vibecode a couple of features, and one of this that you can follow people there and get weekly um book recommendations. So there's now weekly the die you can sign up or opt in for a weekly design uh digest email based on the people you follow, right? So um I am doing a follow-up to make it easier to follow, like you can follow people on their profile, but now you need to find the profile, so that's coming. Yeah, uh, but yeah, it's um that's cool. It's uh you you find well, first of all, it's addictive to add your books there, which is the point, because then it's less doom scrolling and more reading, which what we want. Um, but it's also um yeah, people stumble upon random book tips, uh, apart from our podcast, right? So it's uh yeah, go go sign up and uh and share with us what you're reading.

Julian: 32:43

That's it. And now this year, you know, we have the stats for how many books people read and all that kind of stuff. Almost like one of those Spotify wrapped things, but we're not gonna call it that. But another future. Yeah, yeah, that's something you put in. But it's really cool to see how many books people read. Uh, one of our users who I know personally somehow read something like three, four hundred books this year. I'm pretty sure that was just a an import thing. We imported a boatload of books from you know something else. And uh yeah, anyway. So it's all good. It's a great platform, super fun to use. Please, if you haven't checked it out, have a look and and start adding your stuff to there. It is one of those apps where we're like, nope, we don't need to have any information about you. You're not being farmed for day uh for for data, you're not being you're not part of the Amazon's uh net of um data collection and you know checking everything about you, like good reads. So uh that's why we built it. And it's pretty cool. We love it. So enjoy.

Bob: 33:41

Just a passion for books and exactly the importance we see. That that's the other thing, right? Like these days, as you said, right? Doom and gloom, a lot of social media, toxic stuff. No, we we want to read, we wanna and and and encourage people to read, right? To to work on their mindset to to enrich their lives, right? And and that's again bringing it back to the strength to strength book. Uh it talks about uh workaholic um and and and how you will find in the second half of your career how work is just one thing, right? And I think we said over the break ourselves, like it this is all about the journey, right? It's uh but you have to balance that with with other things to find happiness.

Julian: 34:22

Um and per per the quote that we have at the bottom of Pywite's books, you know, a reader lives a thousand lives before he dies. The man who never reads lives only one. From and that's from George. Yeah, George uh uh Martin. So yeah, I love it. Super cool. Um okay, well, that's it. I think we're done for the the episode. Um, everyone again, thank you for listening. Thank you for being with us over the past couple of years of the podcast. Uh, we hope you'll stick with us.

Bob: 34:50

By the way, five years.

Julian: 34:52

Jeez. Uh yeah. Well, stay with us for the sixth. And and make sure you share it, subscribe, do all the things that you know will help us get our name, um, get this podcast out there. Lots of cool things coming this year. Got a special AI guest coming up, um, an AI expert from the US joining us, uh, joining me in another week or so. Bob, you've got someone got somebody who's very passionate about Rust and Vasm, I think.

Bob: 35:17

So uh that will be interesting.

Julian: 35:18

Yeah. There you go. So some cool things already um slated for the rest of this month and into Feb. Uh, but we'll be scattered in between this time. So you'll have episodes.

Bob: 35:28

We'll we'll talk about over soon trends and stuff.

Julian: 35:32

Yeah. Awesome. All right. Well, thank you for listening, everyone, Bob. Thanks for the chat, and uh, we'll see you on the next episode. Hey everyone, thanks for tuning into the Pivites Podcast. I really hope you enjoyed it. A quick message from me and Bob before you go to get the most out of your experience with Pyblights, including learning more Python, engaging with other developers, learning about our guests, discussing these podcast episodes, and much, much more. Please join our community at pyves.circle.so. The link is on the screen if you're watching this on YouTube, and it's in the show notes for everyone else. When you join, make sure you introduce yourself, engage with myself and Bob, and the many other developers in the community. It's one of the greatest things you can do to expand your knowledge and reach and network as a Python developer. We'll see you in the next episode, and we will see you in the community.