Debug Information

Processing Details

• VTT File: 4101be13.vtt
• Processing Time: September 10, 2025 at 08:56 AM
• Total Chunks: 1
• Transcript Length: 27,873 characters
• Caption Count: 220 captions

Prompts Used

Prompt 1: Context Setup

You are an expert data extractor tasked with analyzing a podcast transcript. 
I will provide you with part 1 of 1 from a podcast transcript. 
I will then ask you to extract different types of information from this content in subsequent messages. Please confirm you have received and understood the transcript content.

Transcript section:
[00:00:00.320 --> 00:00:04.560] Hey, it's Arvid, and this is the Bootstrap Founder.
[00:00:09.280 --> 00:00:16.080] I was reading Brandon Sanderson's latest novel, Wind and Truth, when I came across a sentence that stopped me cold.
[00:00:16.080 --> 00:00:19.760] The sentence was, a stronger current makes for stronger fish.
[00:00:19.760 --> 00:00:21.920] And I thought, wow, that is it.
[00:00:21.920 --> 00:00:24.000] That's exactly what entrepreneurship is.
[00:00:24.000 --> 00:00:32.960] We're constantly finding these currents that either help us, they facilitate what we want to accomplish, businesses we want to build, the lives we want to create, or they oppose us.
[00:00:32.960 --> 00:00:35.520] They're trying to sweep us into more dangerous waters.
[00:00:35.520 --> 00:00:37.600] These currents change all the time.
[00:00:37.600 --> 00:00:41.200] They vary in strength, and that depends on where you are in your journey.
[00:00:41.200 --> 00:00:46.560] And I guess they're mostly invisible until we learn to actually feel them.
[00:00:46.560 --> 00:00:52.560] And somebody on Twitter asked me what my top three currents were after I shared this thought and this quote.
[00:00:52.560 --> 00:01:02.080] And it turned out to be quite a revealing exercise going through this, trying to assess what I'm exposed to, what I'm dealing with, and how I'm navigating these forces.
[00:01:02.080 --> 00:01:10.640] So let me share with you today what I've encountered and discovered about the currents that are pulling at me as I'm building PodScan.
[00:01:10.640 --> 00:01:19.040] The biggest current that I felt over the last year and a half as I've been building the software business is the rapidly changing technological landscape.
[00:01:19.040 --> 00:01:24.480] As a software entrepreneur, I think we're just permanently exposed to new technologies here.
[00:01:24.480 --> 00:01:32.160] And there's always something that you might want to learn, always something that could give you an edge if you figure it out or leave you behind if you don't.
[00:01:32.160 --> 00:01:40.880] And when I was a salaried software engineer back in the day, it was so much easier to get really good at the craft of engineering.
[00:01:40.880 --> 00:01:50.480] All day long, I was dealing with that one particular tech stack and was optimizing my approach to it, understanding it better, implementing everything that needed to be built in that stack.
[00:01:50.480 --> 00:02:01.560] But now, as a founder, there's this fleeting nature of projects and the volatility of early stage software businesses that means pivoting from one stack to another is actually quite easy.
[00:01:59.840 --> 00:02:03.960] And it's not just easy, it's often necessary.
[00:02:04.280 --> 00:02:30.040] And speaking of navigating new technologies and finding the right tools for growth, if you're an app business and you're seeking growth channels and strategies beyond traditional app stores, paddle.com is sponsoring today's episode and they're offering something really valuable, a five-part series filled with actionable strategies for app developers who want to drive revenue beyond the app store, which is always a good idea if you think about the walled garden nature of these things.
[00:02:30.040 --> 00:02:34.600] It's essentially a blueprint that they present with like modern web monetization for app companies.
[00:02:34.600 --> 00:02:35.800] This series is limited.
[00:02:35.800 --> 00:02:40.920] So if this sounds like something that could help you, register now at paddle.com to secure your spot.
[00:02:40.920 --> 00:02:42.200] Link is in the show notes.
[00:02:42.200 --> 00:02:45.800] Now, back to those technological rapids that we all face.
[00:02:48.040 --> 00:02:50.120] Think about it when you're building a business.
[00:02:50.120 --> 00:03:03.640] You might need something like time series data or some kind of vector database that may not be as established as a technology, but it's perfect for building with new tech, particularly embeddings, vector stores, the AI stuff, like RAGs and all of that.
[00:03:03.640 --> 00:03:13.000] You might need to learn a whole new language for communicating with your database and new ways of interacting with data that prior to this, you probably wouldn't have cared about.
[00:03:13.000 --> 00:03:15.880] Like a graph connection between data, you didn't care.
[00:03:15.880 --> 00:03:21.560] You would have just used the regular old database and a regular old approach to building software, but that's not happening anymore.
[00:03:21.560 --> 00:03:28.040] And I think the fact that we are looking at all these other things, that prevents mastery.
[00:03:28.040 --> 00:03:42.760] That is a big, big problem when you're constantly incentivized to switch tech, to learn new tech, to implement new technology into your business immediately when it appears, because you need to stay on top of what the early adopter crowd is interested in, because that's who you're building for.
[00:03:42.760 --> 00:03:48.400] And they want new tech, new ways of dealing with tech, new ways of presenting data, new ways of accumulating data.
[00:03:48.400 --> 00:03:51.600] It makes it very hard to become really good at any one thing.
[00:03:51.600 --> 00:03:55.280] And this is particularly hard when you're in the early stages of building a business.
[00:03:55.280 --> 00:04:08.400] You're not only exposed to all the potential fancy technology, and I don't just mean software stacks, I mean things like AI agentic coding, vibe coding, things that build software for you, just new things, but you just don't know about all of these things.
[00:04:08.400 --> 00:04:17.200] You don't know what this technology is really like, what the nuance is, how exactly it works, and how you can use it in an optimized, high-efficiency way.
[00:04:17.200 --> 00:04:19.760] So, how do I resist this personally?
[00:04:19.760 --> 00:04:23.680] By choosing really solid fundamentals for my own business adventures.
[00:04:23.680 --> 00:04:24.880] Always have been doing this.
[00:04:24.880 --> 00:04:41.760] When I recently built the PodScan Ideas Vault, which is a layer of software that started on top of PodScan's webhook API that constantly extracts all kinds of business ideas from hundreds of podcasts all over the world, I needed to build a new data storage system for that.
[00:04:41.760 --> 00:04:44.640] And there I was thinking, what am I going to use?
[00:04:44.640 --> 00:04:48.640] And I kind of fell back into, I'm just going to go with what I know.
[00:04:48.640 --> 00:04:51.840] I'm going to go open up a Postgres QL database.
[00:04:51.840 --> 00:04:54.720] It's going to be maybe a Redis cache, and that's it.
[00:04:54.720 --> 00:04:57.120] I'm not going to go into document-based databases.
[00:04:57.120 --> 00:05:02.880] That could have been something because there's a lot of JSON data, or even like a dedicated vector storage, because there will be embeddings.
[00:05:02.880 --> 00:05:06.480] I'm going to choose Postgres because it kind of has this built-in.
[00:05:06.480 --> 00:05:08.240] You can handle JSON well in Postgres.
[00:05:08.240 --> 00:05:13.120] You have pgVector, which is a vector storage that you can do these vector calculations in.
[00:05:13.120 --> 00:05:16.080] But in the end, it's always going to be a relational database.
[00:05:16.080 --> 00:05:19.920] And that's something that I have like 20 years of experience with at this point.
[00:05:19.920 --> 00:05:34.120] And it was a pretty good choice because it allowed me to just build the thing that I wanted to build and not feel compelled to yet again learn a new thing, like constantly learning new things all the time just because we're trying to build this extra 5% efficiency.
[00:05:29.840 --> 00:05:35.080] It's really not worth it.
[00:05:35.400 --> 00:05:43.080] So, my recommendation here, and this is very personal, but that's how I've been doing it: just go with technology that hasn't changed based on hype.
[00:05:43.320 --> 00:05:46.040] That isn't just there because people are hyping it up.
[00:05:46.040 --> 00:05:53.080] You should be making this choice based on the effect and longevity of a piece of technology.
[00:05:53.080 --> 00:05:57.080] If it's been around, if it's been safe, then it's also a safe choice to make.
[00:05:57.080 --> 00:06:04.360] If you're a Rails developer and you want to build a new business and you think you might try something else, just default to Rails.
[00:06:04.360 --> 00:06:05.880] Please just use what you know.
[00:06:05.880 --> 00:06:14.920] And even though you could go into PHP, use Laravel, or go into JavaScript, use Next.js or whatever, have fancy new automated, complicated build systems that are super weird.
[00:06:14.920 --> 00:06:15.720] It's all great.
[00:06:15.720 --> 00:06:16.520] It's all wonderful.
[00:06:16.520 --> 00:06:20.360] It's great that this stuff exists, but could well be a thing if you wanted to use it.
[00:06:20.360 --> 00:06:25.800] But you don't have to choose this technology because it's there and because everybody else is kind of using it.
[00:06:25.800 --> 00:06:29.880] You should choose the one that you already understand that helps you build the thing you want to build.
[00:06:29.880 --> 00:06:36.440] And this makes it easier, particularly if you look at how AI coding is such a normal thing for most people now, right?
[00:06:36.440 --> 00:06:40.520] Even though people don't always use agentic tools, they will use autocomplete.
[00:06:40.520 --> 00:06:43.320] That's always been a thing, I guess, in TeleSense and all that kind of stuff.
[00:06:43.320 --> 00:06:55.400] But knowing if an autocomplete suggestion is good, if it's something that is going to benefit your project or break it, well, that is only possible if you have an understanding of the underlying framework and system.
[00:06:55.400 --> 00:07:07.480] For that, you should always go with the thing you know, because if you try to autocomplete and prompt your way to a stable piece of software, you have to kind of rely on the AI's understanding of stability.
[00:07:07.480 --> 00:07:09.960] And that might not be what you need.
[00:07:09.960 --> 00:07:23.840] And if you don't know anything about coding, if you're just going to start learning the technology, learning to code while building a business, well, then going with a widely adopted and widely popular system like Laravel, PHP, or Ruby on Rails probably is a good idea.
[00:07:23.840 --> 00:07:28.160] The reverse Lindy effect is real for all kinds of new technology.
[00:07:28.160 --> 00:07:34.720] Technology that hasn't been around for a while, that's rather new, has a high risk of not sticking around for longer.
[00:07:34.720 --> 00:07:42.720] Because the Lindy effect, its inverse, says that if a technology has been around for a long time, it will likely stick around for equally as long for many reasons, right?
[00:07:42.720 --> 00:07:46.960] The inverse of it means if it's rather new, then it's volatile.
[00:07:46.960 --> 00:07:55.440] You might run into software that just stops working after a while because it just didn't get the traction people thought it needed, particularly in the vibe coding universe.
[00:07:55.440 --> 00:07:57.680] This is probably going to happen.
[00:07:57.680 --> 00:08:03.760] I think we saw it with what was it, Windserve that got acquired, and then all kinds of weird things happened.
[00:08:03.760 --> 00:08:08.160] Now, that's not necessarily exactly vibe coding, it's just AI-assisted coding.
[00:08:08.160 --> 00:08:11.760] But tools like Lovable and Bolt, they are fighting it out.
[00:08:11.760 --> 00:08:14.960] There is an arena, and only a couple of those are going to remain.
[00:08:14.960 --> 00:08:22.320] So, if you have a project on any of these, you better understand how to self-host this or get it hosted somewhere else as a backup.
[00:08:22.320 --> 00:08:26.720] These things are really new, and they might be gone in a year from now.
[00:08:26.720 --> 00:08:29.040] Now, that's current number one: technology is weird.
[00:08:29.040 --> 00:08:29.920] It's pretty much what it is.
[00:08:29.920 --> 00:08:34.880] Technology is fast, I can't stop it, and it happens to me, so I have to deal with it.
[00:08:34.880 --> 00:08:39.280] The second current that I feel for myself is both a blessing and a curse.
[00:08:39.280 --> 00:08:42.320] Software engineering is being heavily commoditized.
[00:08:42.320 --> 00:08:51.440] It's so much easier to build software now, so much faster to create working monetizable prototypes and clones of stuff.
[00:08:51.440 --> 00:08:54.240] And this has been a boon to the IndieHacker community.
[00:08:54.240 --> 00:09:02.600] Solo founders can start small niche businesses like never before, like get them into a point where the prototype can be monetized very early.
[00:08:59.840 --> 00:09:04.600] But here's the undertow to this.
[00:09:04.840 --> 00:09:11.960] It's just as easy for anybody working at a larger company with deeper pockets to build the same thing using the same technology.
[00:09:11.960 --> 00:09:19.000] Your idea can be copied, can be duplicated, and just out-executed by somebody with more time or resources.
[00:09:19.000 --> 00:09:22.840] The red flags in B2B software building are still there.
[00:09:22.840 --> 00:09:28.280] People in those companies, they need clearance for projects, they need to write specs and build integrations or whatever.
[00:09:28.280 --> 00:09:32.920] But the barrier to entry to even get started with this has dropped dramatically.
[00:09:32.920 --> 00:09:34.440] We see this in acquisitions too.
[00:09:34.440 --> 00:09:46.360] Like acquisitions of software businesses, they just take much longer in due diligence because for most companies, it's buy or build, where in the past, it's just been do I buy or do I not buy?
[00:09:46.360 --> 00:09:52.200] Now they can, for the same amount of money, likely build a similarly well-designed piece of software.
[00:09:52.200 --> 00:09:53.720] At least they think so.
[00:09:53.720 --> 00:09:56.280] And that impacts prices, that impacts negotiation.
[00:09:56.280 --> 00:09:57.800] So that is a real thing.
[00:09:57.800 --> 00:09:59.880] It's all being commoditized.
[00:09:59.880 --> 00:10:07.240] This makes bootstrapping a software business less of a solid defensive mode than it used to be in the past.
[00:10:07.240 --> 00:10:15.240] Unless, and this is crucial, unless you build distribution and a public brand around it, you're going to have a problem.
[00:10:15.240 --> 00:10:23.640] And that leads me to my third current quite directly, the ever-growing need for attention in this increasingly crowded ocean.
[00:10:23.640 --> 00:10:29.240] Now, that's a current that both pulls me along and holds me back depending on where I look.
[00:10:29.240 --> 00:10:36.600] The biggest problem for any founder is distribution at this point, because execution is easy and idea is kind of easy too.
[00:10:36.600 --> 00:10:41.320] You can have AI get you very far with both of these.
[00:10:41.320 --> 00:10:45.280] It is hard to find actual human customers for your projects though.
[00:10:45.520 --> 00:10:52.640] If you don't have the marketing dollars to just spend on paid advertising or influencer marketing, once you have that kind of money, that's great.
[00:10:52.640 --> 00:10:53.520] That works, right?
[00:10:53.520 --> 00:10:56.960] It really works, but you get solid leads from spending money.
[00:10:56.960 --> 00:10:57.760] That's the rule.
[00:10:57.760 --> 00:11:00.800] And if you don't have that money, you kind of have to do it organically.
[00:11:00.800 --> 00:11:05.200] You have to build a brand in public, share your business journey in public, attract people.
[00:11:05.200 --> 00:11:09.440] And building in public is still the cheapest way of getting attention on yourself and your business.
[00:11:09.440 --> 00:11:14.240] Finding those first couple customers, finding partnerships and evangelists, all that kind of stuff.
[00:11:14.240 --> 00:11:16.320] But it is marketing.
[00:11:16.320 --> 00:11:19.200] And that's where the strongest tension is for me.
[00:11:19.200 --> 00:11:22.320] I want to stay authentically myself as a founder.
[00:11:22.320 --> 00:11:28.000] I want to communicate very authentically what my journey is as I build my businesses in public.
[00:11:28.000 --> 00:11:33.600] But I also know that every single post I make has a marketing angle.
[00:11:33.600 --> 00:11:38.320] So let me share how this attention currently plays out in my daily routine.
[00:11:38.320 --> 00:11:45.040] Every day before my newsletter goes out, the Potskin Ideas newsletter, I share one or two ideas from it with commentary on Twitter.
[00:11:45.040 --> 00:11:46.560] And I've been doing this for the last couple of weeks.
[00:11:46.720 --> 00:11:48.640] If you follow me on Twitter, you've probably seen it.
[00:11:48.640 --> 00:11:55.680] I want people to know that, first off, there is a newsletter that might be interesting to them, and this is what they might get.
[00:11:55.680 --> 00:11:59.280] And it's a marketing activity to share what the newsletter does every day.
[00:11:59.280 --> 00:12:00.640] I'm quite aware of this.
[00:12:00.640 --> 00:12:04.240] So it feels performative on occasion to post about this.
[00:12:04.240 --> 00:12:07.920] Every day at 8 a.m., my newsletter goes out, and then I check, okay, what's in there?
[00:12:07.920 --> 00:12:08.640] What's interesting?
[00:12:08.640 --> 00:12:10.000] What could I say about this?
[00:12:10.000 --> 00:12:15.680] And as much as I actually like to see all these ideas and during the day, I just check it out because I'm curious.
[00:12:15.680 --> 00:12:18.800] I want to get some kind of insight into what's being talked about in the world.
[00:12:18.800 --> 00:12:21.440] That reaching out on Twitter, that's still marketing.
[00:12:21.440 --> 00:12:26.400] So, being a creator on social media will try to remain an authentic human being.
[00:12:26.400 --> 00:12:32.360] That is a current that sometimes pulls me towards my goals and sometimes perceivedly away from them, right?
[00:12:32.360 --> 00:12:39.800] It's hard to do marketing and stay authentic, and it's hard to stay authentic and do marketing if you're not capable of kind of unifying these two.
[00:12:39.800 --> 00:12:48.120] And another current that I feel very strongly here, particularly in our community of founders online, is being a consumer of social media.
[00:12:48.120 --> 00:12:57.480] I suffer a hard time maintaining a firm grasp on my own journey when everybody else's journey just seems to be flashing much more brightly around me.
[00:12:57.480 --> 00:13:05.480] Social media is highly selective, and people share the good stuff, they rarely share the bad stuff.
[00:13:05.480 --> 00:13:13.240] So, what we see is kind of this echo chamber of positivity-not necessarily toxic positivity, but it's selective positivity.
[00:13:13.240 --> 00:13:15.880] People share, oh, my MRR went up.
[00:13:15.880 --> 00:13:16.520] That's wonderful.
[00:13:16.520 --> 00:13:19.640] You get a screenshot, and you know, the graph goes to the top right.
[00:13:19.640 --> 00:13:22.120] Here's that, and look at this, this is how I did it.
[00:13:22.120 --> 00:13:27.640] I don't really see too many people sharing when their MRR goes down and with the screenshot that comes from that.
[00:13:27.640 --> 00:13:32.520] People do that occasionally, but it's like a what is it, nine-to-one relationship, right?
[00:13:32.520 --> 00:13:35.400] I don't really get to see them that often because people don't share them.
[00:13:35.400 --> 00:13:42.520] So, what we do see is that everybody or mostly everybody is doing well, and you just don't get to see the struggles because they're not posted.
[00:13:42.520 --> 00:13:48.360] And my own reality, where every day the MRR graph goes up and down as well, like there's always some movement.
[00:13:48.360 --> 00:13:50.440] Either way, it's a 50-50 chance.
[00:13:50.440 --> 00:13:53.720] Well, that's not represented in the social network around me.
[00:13:53.720 --> 00:13:57.160] And if it's not represented, I cannot perceive it accurately.
[00:13:57.160 --> 00:14:01.960] And if I can't perceive it accurately, my own journey is colored by a distortion.
[00:14:01.960 --> 00:14:05.720] And it doesn't even have to be envy or jealousy for this to affect you.
[00:14:05.720 --> 00:14:09.320] It's like Plato's cave: we're looking at shadows on the wall.
[00:14:09.320 --> 00:14:17.440] What we see are mirrors, silhouettes on the wall, and the reality is something behind us that we don't necessarily get to see because we only get to see the wall.
[00:14:17.440 --> 00:14:20.080] And quite literally, the Facebook wall and the Twitter feed.
[00:14:14.840 --> 00:14:21.120] It's very selective.
[00:14:21.440 --> 00:14:27.200] This kind of discrepancy is a strong current that I feel can often motivate me because I see other people doing well.
[00:14:27.200 --> 00:14:28.880] And I think I can do that too.
[00:14:28.880 --> 00:14:30.320] I want to get there too.
[00:14:30.320 --> 00:14:31.280] What do I need to do?
[00:14:31.280 --> 00:14:32.160] And then I do it.
[00:14:32.160 --> 00:14:37.760] But it can be disheartening in moments of doubt and moments of perceived failure, lack of success.
[00:14:37.760 --> 00:14:42.640] It's a strong feeling when it seems like everybody else is doing so well.
[00:14:42.960 --> 00:14:50.560] Final current that I found, and this is particularly hard, is the pull of work-life balance.
[00:14:50.560 --> 00:14:52.880] I try not to spend all day working.
[00:14:52.880 --> 00:15:01.200] I've been focusing more on balancing my own mental stability, which I derive from being with friends, family, from reading, from having hobbies, playing with my dog.
[00:15:01.200 --> 00:15:16.320] Yet combining the lack of technological stability with the pressure of social media presence, well, that makes me want to go and spend more time to reach my goals and less time away from work, which is also a goal, but one that isn't as directly perceived as like sitting in front of a computer.
[00:15:16.320 --> 00:15:27.680] So when I don't work, there's always a nagging thought, you could be spending time working, even though it wouldn't be necessarily productive or even helpful, might be distracting just working for the sake of working.
[00:15:27.680 --> 00:15:34.400] But we all understand now that you don't measure the quality of a software engineer by lines of code that they've written.
[00:15:34.640 --> 00:15:39.600] You measure by features implemented bugs fixed, efficiency gains, maybe sales made with the product.
[00:15:39.600 --> 00:15:42.480] You don't measure output, you measure impact.
[00:15:42.480 --> 00:15:45.200] Yet there's still this output-centric mindset.
[00:15:45.200 --> 00:15:46.560] And I suffer from this too.
[00:15:46.560 --> 00:15:53.600] This current that says more time working equals better results, or maybe equals a higher chance at better results.
[00:15:53.600 --> 00:15:59.360] It's kind of how we massage it into our brains, even though we know that too much work is actually detrimental.
[00:15:59.360 --> 00:16:01.880] And that's a current that I'm trying to swim against.
[00:16:02.200 --> 00:16:04.120] So it's just hard, right?
[00:16:04.120 --> 00:16:11.400] After 25 years of sitting in front of a computer, it's just so easy to fall into the same routine, check things, try to improve things a little.
[00:16:11.400 --> 00:16:14.200] It's really hard to step outside and not do that.
[00:16:14.200 --> 00:16:18.120] Your currents are probably going to look a little bit different from mine.
[00:16:18.120 --> 00:16:23.880] There might be overlap, and you might have the same ones, but feel pulled in a different direction.
[00:16:23.880 --> 00:16:27.960] You might view these forces maybe more benevolently or more malevolently.
[00:16:27.960 --> 00:16:40.440] But here's what I think is important about all of this: it's just realizing that these currents actually exist because they're often internally validated, but they're mostly external forces that are acting upon you.
[00:16:40.440 --> 00:16:44.840] People will share their MRR graphs and stories with or without you.
[00:16:44.840 --> 00:16:45.720] It doesn't matter.
[00:16:45.720 --> 00:16:48.920] Rapid developments in AI and frameworks, that's not your fault.
[00:16:48.920 --> 00:16:52.120] The fact that this causes more competition, also not your fault.
[00:16:52.120 --> 00:16:58.200] The fact that you picked an industry that now sees for some reason many people trying to build in it, that is also not your fault.
[00:16:58.200 --> 00:17:06.040] These are external forces, but we make them internal when we allow them to sweep us away without even knowing that we're moving.
[00:17:06.040 --> 00:17:15.800] The important part is to understand that these currents exist, to make them visible, to make them present, so that we can recognize them as currents and not as our own failings.
[00:17:15.800 --> 00:17:19.400] We shouldn't despair when we get pulled in a direction a little bit too much.
[00:17:19.400 --> 00:17:21.320] That's just what entrepreneurship is.
[00:17:21.320 --> 00:17:27.800] You're constantly torn from one side to the other, and you have to make different strokes to stay swimming where you want to be.
[00:17:27.800 --> 00:17:38.040] So a stronger current does make for stronger fish by the virtue of you reacting to it, but only if you know that you're swimming, only if you're aware of the water that you're in.
[00:17:38.040 --> 00:17:46.960] So, once you recognize the currents, you can choose to swim against them, swim with them, or maybe find the calm eddies where you can rest and reassess, kind of take yourself out of it.
[00:17:47.280 --> 00:17:54.640] You don't have to constantly follow all tech, you don't have to always try to work more or less.
[00:17:54.640 --> 00:17:58.400] You can just like set guidelines and act on them for a bit and just see what happens.
[00:17:58.400 --> 00:18:10.320] The currents will always be there, they change with the tides of technology, market forces, social dynamics, but awareness about them-that's your compass and deliberate action-that's your stroke, your swim stroke.
[00:18:10.320 --> 00:18:14.240] So, take a moment and feel the currents pulling at you.
[00:18:14.240 --> 00:18:18.960] Maybe name them to understand them better, then decide how you want to navigate them.
[00:18:18.960 --> 00:18:23.600] Because, in the end, you're not just trying to survive these waters, you're trying to get somewhere, right?
[00:18:23.600 --> 00:18:25.200] You're trying to build something meaningful.
[00:18:25.200 --> 00:18:28.560] And knowing the currents is the first step to charting your course.
[00:18:28.560 --> 00:18:30.560] Thanks so much for listening to the Bootstrap Founder.
[00:18:30.560 --> 00:18:34.160] Find me on Twitter at Avidka, A-R-V-I-D-K-A-H-L.
[00:18:34.160 --> 00:18:45.840] If you want to know what everyone's saying about your brand on over 3.8 million podcasts, podscan.fm tracks mentions in near real time with a powerful API that turns podcast conversations into actionable data.
[00:18:45.840 --> 00:18:59.520] And if you're hunting for your next business idea, get them delivered fresh from the podcast world at ideas.podscan.fm, where an AI extracts the best startup opportunities from 500 plus hours of expert conversations every day.
[00:18:59.520 --> 00:19:03.040] Share this with anyone who needs to stay ahead of the conversation.
[00:19:03.040 --> 00:19:03.920] Thanks for listening.
[00:19:03.920 --> 00:19:06.480] Have a wonderful day and bye-bye.

Prompt 2: Key Takeaways

Now please extract the key takeaways from the transcript content I provided.

Extract the most important key takeaways from this part of the conversation. Use a single sentence statement (the key takeaway) rather than milquetoast descriptions like "the hosts discuss...". 

Limit the key takeaways to a maximum of 3. The key takeaways should be insightful and knowledge-additive. 

IMPORTANT: Return ONLY valid JSON, no explanations or markdown. Ensure:
- All strings are properly quoted and escaped
- No trailing commas
- All braces and brackets are balanced
Format: {"key_takeaways": ["takeaway 1", "takeaway 2"]}

Prompt 3: Segments

Now identify 2-4 distinct topical segments from this part of the conversation.

For each segment, identify:
- Descriptive title (3-6 words)  
- START timestamp when this topic begins (HH:MM:SS format)
- Double check that the timestamp is accurate - a timestamp will NEVER be greater than the total length of the audio
- Most important Key takeaway from that segment. Key takeaway must be specific and knowledge-additive.
- Brief summary of the discussion

IMPORTANT: The timestamp should mark when the topic/segment STARTS, not a range. Look for topic transitions and conversation shifts.

Return ONLY valid JSON. Ensure all strings are properly quoted, no trailing commas:
{
  "segments": [
    {
      "segment_title": "Topic Discussion", 
      "timestamp": "01:15:30",
      "key_takeaway": "main point from this segment",
      "segment_summary": "brief description of what was discussed"
    }
  ]
}

Timestamp format: HH:MM:SS (e.g., 00:05:30, 01:22:45) marking the START of each segment.

Prompt 4: Media Mentions

Now scan the transcript content I provided for ACTUAL mentions of specific media titles:

Find explicit mentions of:
- Books (with specific titles)
- Movies (with specific titles)  
- TV Shows (with specific titles)
- Music/Songs (with specific titles)

DO NOT include:
- Websites, URLs, or web services
- Other podcasts or podcast names

IMPORTANT: 
- Only include items explicitly mentioned by name. Do not invent titles.
- Valid categories are: "Book", "Movie", "TV Show", "Music"
- Include the exact phrase where each item was mentioned
- Find the nearest proximate timestamp where it appears in the conversation
- THE TIMESTAMP OF THE MEDIA MENTION IS IMPORTANT - DO NOT INVENT TIMESTAMPS AND DO NOT MISATTRIBUTE TIMESTAMPS
- Double check that the timestamp is accurate - a timestamp will NEVER be greater than the total length of the audio
- Timestamps are given as ranges, e.g. 01:13:42.520 --> 01:13:46.720. Use the EARLIER of the 2 timestamps in the range.

Return ONLY valid JSON. Ensure all strings are properly quoted and escaped, no trailing commas:
{
  "media_mentions": [
    {
      "title": "Exact Title as Mentioned",
      "category": "Book",
      "author_artist": "N/A",
      "context": "Brief context of why it was mentioned",
      "context_phrase": "The exact sentence or phrase where it was mentioned",
      "timestamp": "estimated time like 01:15:30"
    }
  ]
}

If no media is mentioned, return: {"media_mentions": []}

Full Transcript

[00:00:00.320 --> 00:00:04.560] Hey, it's Arvid, and this is the Bootstrap Founder.
[00:00:09.280 --> 00:00:16.080] I was reading Brandon Sanderson's latest novel, Wind and Truth, when I came across a sentence that stopped me cold.
[00:00:16.080 --> 00:00:19.760] The sentence was, a stronger current makes for stronger fish.
[00:00:19.760 --> 00:00:21.920] And I thought, wow, that is it.
[00:00:21.920 --> 00:00:24.000] That's exactly what entrepreneurship is.
[00:00:24.000 --> 00:00:32.960] We're constantly finding these currents that either help us, they facilitate what we want to accomplish, businesses we want to build, the lives we want to create, or they oppose us.
[00:00:32.960 --> 00:00:35.520] They're trying to sweep us into more dangerous waters.
[00:00:35.520 --> 00:00:37.600] These currents change all the time.
[00:00:37.600 --> 00:00:41.200] They vary in strength, and that depends on where you are in your journey.
[00:00:41.200 --> 00:00:46.560] And I guess they're mostly invisible until we learn to actually feel them.
[00:00:46.560 --> 00:00:52.560] And somebody on Twitter asked me what my top three currents were after I shared this thought and this quote.
[00:00:52.560 --> 00:01:02.080] And it turned out to be quite a revealing exercise going through this, trying to assess what I'm exposed to, what I'm dealing with, and how I'm navigating these forces.
[00:01:02.080 --> 00:01:10.640] So let me share with you today what I've encountered and discovered about the currents that are pulling at me as I'm building PodScan.
[00:01:10.640 --> 00:01:19.040] The biggest current that I felt over the last year and a half as I've been building the software business is the rapidly changing technological landscape.
[00:01:19.040 --> 00:01:24.480] As a software entrepreneur, I think we're just permanently exposed to new technologies here.
[00:01:24.480 --> 00:01:32.160] And there's always something that you might want to learn, always something that could give you an edge if you figure it out or leave you behind if you don't.
[00:01:32.160 --> 00:01:40.880] And when I was a salaried software engineer back in the day, it was so much easier to get really good at the craft of engineering.
[00:01:40.880 --> 00:01:50.480] All day long, I was dealing with that one particular tech stack and was optimizing my approach to it, understanding it better, implementing everything that needed to be built in that stack.
[00:01:50.480 --> 00:02:01.560] But now, as a founder, there's this fleeting nature of projects and the volatility of early stage software businesses that means pivoting from one stack to another is actually quite easy.
[00:01:59.840 --> 00:02:03.960] And it's not just easy, it's often necessary.
[00:02:04.280 --> 00:02:30.040] And speaking of navigating new technologies and finding the right tools for growth, if you're an app business and you're seeking growth channels and strategies beyond traditional app stores, paddle.com is sponsoring today's episode and they're offering something really valuable, a five-part series filled with actionable strategies for app developers who want to drive revenue beyond the app store, which is always a good idea if you think about the walled garden nature of these things.
[00:02:30.040 --> 00:02:34.600] It's essentially a blueprint that they present with like modern web monetization for app companies.
[00:02:34.600 --> 00:02:35.800] This series is limited.
[00:02:35.800 --> 00:02:40.920] So if this sounds like something that could help you, register now at paddle.com to secure your spot.
[00:02:40.920 --> 00:02:42.200] Link is in the show notes.
[00:02:42.200 --> 00:02:45.800] Now, back to those technological rapids that we all face.
[00:02:48.040 --> 00:02:50.120] Think about it when you're building a business.
[00:02:50.120 --> 00:03:03.640] You might need something like time series data or some kind of vector database that may not be as established as a technology, but it's perfect for building with new tech, particularly embeddings, vector stores, the AI stuff, like RAGs and all of that.
[00:03:03.640 --> 00:03:13.000] You might need to learn a whole new language for communicating with your database and new ways of interacting with data that prior to this, you probably wouldn't have cared about.
[00:03:13.000 --> 00:03:15.880] Like a graph connection between data, you didn't care.
[00:03:15.880 --> 00:03:21.560] You would have just used the regular old database and a regular old approach to building software, but that's not happening anymore.
[00:03:21.560 --> 00:03:28.040] And I think the fact that we are looking at all these other things, that prevents mastery.
[00:03:28.040 --> 00:03:42.760] That is a big, big problem when you're constantly incentivized to switch tech, to learn new tech, to implement new technology into your business immediately when it appears, because you need to stay on top of what the early adopter crowd is interested in, because that's who you're building for.
[00:03:42.760 --> 00:03:48.400] And they want new tech, new ways of dealing with tech, new ways of presenting data, new ways of accumulating data.
[00:03:48.400 --> 00:03:51.600] It makes it very hard to become really good at any one thing.
[00:03:51.600 --> 00:03:55.280] And this is particularly hard when you're in the early stages of building a business.
[00:03:55.280 --> 00:04:08.400] You're not only exposed to all the potential fancy technology, and I don't just mean software stacks, I mean things like AI agentic coding, vibe coding, things that build software for you, just new things, but you just don't know about all of these things.
[00:04:08.400 --> 00:04:17.200] You don't know what this technology is really like, what the nuance is, how exactly it works, and how you can use it in an optimized, high-efficiency way.
[00:04:17.200 --> 00:04:19.760] So, how do I resist this personally?
[00:04:19.760 --> 00:04:23.680] By choosing really solid fundamentals for my own business adventures.
[00:04:23.680 --> 00:04:24.880] Always have been doing this.
[00:04:24.880 --> 00:04:41.760] When I recently built the PodScan Ideas Vault, which is a layer of software that started on top of PodScan's webhook API that constantly extracts all kinds of business ideas from hundreds of podcasts all over the world, I needed to build a new data storage system for that.
[00:04:41.760 --> 00:04:44.640] And there I was thinking, what am I going to use?
[00:04:44.640 --> 00:04:48.640] And I kind of fell back into, I'm just going to go with what I know.
[00:04:48.640 --> 00:04:51.840] I'm going to go open up a Postgres QL database.
[00:04:51.840 --> 00:04:54.720] It's going to be maybe a Redis cache, and that's it.
[00:04:54.720 --> 00:04:57.120] I'm not going to go into document-based databases.
[00:04:57.120 --> 00:05:02.880] That could have been something because there's a lot of JSON data, or even like a dedicated vector storage, because there will be embeddings.
[00:05:02.880 --> 00:05:06.480] I'm going to choose Postgres because it kind of has this built-in.
[00:05:06.480 --> 00:05:08.240] You can handle JSON well in Postgres.
[00:05:08.240 --> 00:05:13.120] You have pgVector, which is a vector storage that you can do these vector calculations in.
[00:05:13.120 --> 00:05:16.080] But in the end, it's always going to be a relational database.
[00:05:16.080 --> 00:05:19.920] And that's something that I have like 20 years of experience with at this point.
[00:05:19.920 --> 00:05:34.120] And it was a pretty good choice because it allowed me to just build the thing that I wanted to build and not feel compelled to yet again learn a new thing, like constantly learning new things all the time just because we're trying to build this extra 5% efficiency.
[00:05:29.840 --> 00:05:35.080] It's really not worth it.
[00:05:35.400 --> 00:05:43.080] So, my recommendation here, and this is very personal, but that's how I've been doing it: just go with technology that hasn't changed based on hype.
[00:05:43.320 --> 00:05:46.040] That isn't just there because people are hyping it up.
[00:05:46.040 --> 00:05:53.080] You should be making this choice based on the effect and longevity of a piece of technology.
[00:05:53.080 --> 00:05:57.080] If it's been around, if it's been safe, then it's also a safe choice to make.
[00:05:57.080 --> 00:06:04.360] If you're a Rails developer and you want to build a new business and you think you might try something else, just default to Rails.
[00:06:04.360 --> 00:06:05.880] Please just use what you know.
[00:06:05.880 --> 00:06:14.920] And even though you could go into PHP, use Laravel, or go into JavaScript, use Next.js or whatever, have fancy new automated, complicated build systems that are super weird.
[00:06:14.920 --> 00:06:15.720] It's all great.
[00:06:15.720 --> 00:06:16.520] It's all wonderful.
[00:06:16.520 --> 00:06:20.360] It's great that this stuff exists, but could well be a thing if you wanted to use it.
[00:06:20.360 --> 00:06:25.800] But you don't have to choose this technology because it's there and because everybody else is kind of using it.
[00:06:25.800 --> 00:06:29.880] You should choose the one that you already understand that helps you build the thing you want to build.
[00:06:29.880 --> 00:06:36.440] And this makes it easier, particularly if you look at how AI coding is such a normal thing for most people now, right?
[00:06:36.440 --> 00:06:40.520] Even though people don't always use agentic tools, they will use autocomplete.
[00:06:40.520 --> 00:06:43.320] That's always been a thing, I guess, in TeleSense and all that kind of stuff.
[00:06:43.320 --> 00:06:55.400] But knowing if an autocomplete suggestion is good, if it's something that is going to benefit your project or break it, well, that is only possible if you have an understanding of the underlying framework and system.
[00:06:55.400 --> 00:07:07.480] For that, you should always go with the thing you know, because if you try to autocomplete and prompt your way to a stable piece of software, you have to kind of rely on the AI's understanding of stability.
[00:07:07.480 --> 00:07:09.960] And that might not be what you need.
[00:07:09.960 --> 00:07:23.840] And if you don't know anything about coding, if you're just going to start learning the technology, learning to code while building a business, well, then going with a widely adopted and widely popular system like Laravel, PHP, or Ruby on Rails probably is a good idea.
[00:07:23.840 --> 00:07:28.160] The reverse Lindy effect is real for all kinds of new technology.
[00:07:28.160 --> 00:07:34.720] Technology that hasn't been around for a while, that's rather new, has a high risk of not sticking around for longer.
[00:07:34.720 --> 00:07:42.720] Because the Lindy effect, its inverse, says that if a technology has been around for a long time, it will likely stick around for equally as long for many reasons, right?
[00:07:42.720 --> 00:07:46.960] The inverse of it means if it's rather new, then it's volatile.
[00:07:46.960 --> 00:07:55.440] You might run into software that just stops working after a while because it just didn't get the traction people thought it needed, particularly in the vibe coding universe.
[00:07:55.440 --> 00:07:57.680] This is probably going to happen.
[00:07:57.680 --> 00:08:03.760] I think we saw it with what was it, Windserve that got acquired, and then all kinds of weird things happened.
[00:08:03.760 --> 00:08:08.160] Now, that's not necessarily exactly vibe coding, it's just AI-assisted coding.
[00:08:08.160 --> 00:08:11.760] But tools like Lovable and Bolt, they are fighting it out.
[00:08:11.760 --> 00:08:14.960] There is an arena, and only a couple of those are going to remain.
[00:08:14.960 --> 00:08:22.320] So, if you have a project on any of these, you better understand how to self-host this or get it hosted somewhere else as a backup.
[00:08:22.320 --> 00:08:26.720] These things are really new, and they might be gone in a year from now.
[00:08:26.720 --> 00:08:29.040] Now, that's current number one: technology is weird.
[00:08:29.040 --> 00:08:29.920] It's pretty much what it is.
[00:08:29.920 --> 00:08:34.880] Technology is fast, I can't stop it, and it happens to me, so I have to deal with it.
[00:08:34.880 --> 00:08:39.280] The second current that I feel for myself is both a blessing and a curse.
[00:08:39.280 --> 00:08:42.320] Software engineering is being heavily commoditized.
[00:08:42.320 --> 00:08:51.440] It's so much easier to build software now, so much faster to create working monetizable prototypes and clones of stuff.
[00:08:51.440 --> 00:08:54.240] And this has been a boon to the IndieHacker community.
[00:08:54.240 --> 00:09:02.600] Solo founders can start small niche businesses like never before, like get them into a point where the prototype can be monetized very early.
[00:08:59.840 --> 00:09:04.600] But here's the undertow to this.
[00:09:04.840 --> 00:09:11.960] It's just as easy for anybody working at a larger company with deeper pockets to build the same thing using the same technology.
[00:09:11.960 --> 00:09:19.000] Your idea can be copied, can be duplicated, and just out-executed by somebody with more time or resources.
[00:09:19.000 --> 00:09:22.840] The red flags in B2B software building are still there.
[00:09:22.840 --> 00:09:28.280] People in those companies, they need clearance for projects, they need to write specs and build integrations or whatever.
[00:09:28.280 --> 00:09:32.920] But the barrier to entry to even get started with this has dropped dramatically.
[00:09:32.920 --> 00:09:34.440] We see this in acquisitions too.
[00:09:34.440 --> 00:09:46.360] Like acquisitions of software businesses, they just take much longer in due diligence because for most companies, it's buy or build, where in the past, it's just been do I buy or do I not buy?
[00:09:46.360 --> 00:09:52.200] Now they can, for the same amount of money, likely build a similarly well-designed piece of software.
[00:09:52.200 --> 00:09:53.720] At least they think so.
[00:09:53.720 --> 00:09:56.280] And that impacts prices, that impacts negotiation.
[00:09:56.280 --> 00:09:57.800] So that is a real thing.
[00:09:57.800 --> 00:09:59.880] It's all being commoditized.
[00:09:59.880 --> 00:10:07.240] This makes bootstrapping a software business less of a solid defensive mode than it used to be in the past.
[00:10:07.240 --> 00:10:15.240] Unless, and this is crucial, unless you build distribution and a public brand around it, you're going to have a problem.
[00:10:15.240 --> 00:10:23.640] And that leads me to my third current quite directly, the ever-growing need for attention in this increasingly crowded ocean.
[00:10:23.640 --> 00:10:29.240] Now, that's a current that both pulls me along and holds me back depending on where I look.
[00:10:29.240 --> 00:10:36.600] The biggest problem for any founder is distribution at this point, because execution is easy and idea is kind of easy too.
[00:10:36.600 --> 00:10:41.320] You can have AI get you very far with both of these.
[00:10:41.320 --> 00:10:45.280] It is hard to find actual human customers for your projects though.
[00:10:45.520 --> 00:10:52.640] If you don't have the marketing dollars to just spend on paid advertising or influencer marketing, once you have that kind of money, that's great.
[00:10:52.640 --> 00:10:53.520] That works, right?
[00:10:53.520 --> 00:10:56.960] It really works, but you get solid leads from spending money.
[00:10:56.960 --> 00:10:57.760] That's the rule.
[00:10:57.760 --> 00:11:00.800] And if you don't have that money, you kind of have to do it organically.
[00:11:00.800 --> 00:11:05.200] You have to build a brand in public, share your business journey in public, attract people.
[00:11:05.200 --> 00:11:09.440] And building in public is still the cheapest way of getting attention on yourself and your business.
[00:11:09.440 --> 00:11:14.240] Finding those first couple customers, finding partnerships and evangelists, all that kind of stuff.
[00:11:14.240 --> 00:11:16.320] But it is marketing.
[00:11:16.320 --> 00:11:19.200] And that's where the strongest tension is for me.
[00:11:19.200 --> 00:11:22.320] I want to stay authentically myself as a founder.
[00:11:22.320 --> 00:11:28.000] I want to communicate very authentically what my journey is as I build my businesses in public.
[00:11:28.000 --> 00:11:33.600] But I also know that every single post I make has a marketing angle.
[00:11:33.600 --> 00:11:38.320] So let me share how this attention currently plays out in my daily routine.
[00:11:38.320 --> 00:11:45.040] Every day before my newsletter goes out, the Potskin Ideas newsletter, I share one or two ideas from it with commentary on Twitter.
[00:11:45.040 --> 00:11:46.560] And I've been doing this for the last couple of weeks.
[00:11:46.720 --> 00:11:48.640] If you follow me on Twitter, you've probably seen it.
[00:11:48.640 --> 00:11:55.680] I want people to know that, first off, there is a newsletter that might be interesting to them, and this is what they might get.
[00:11:55.680 --> 00:11:59.280] And it's a marketing activity to share what the newsletter does every day.
[00:11:59.280 --> 00:12:00.640] I'm quite aware of this.
[00:12:00.640 --> 00:12:04.240] So it feels performative on occasion to post about this.
[00:12:04.240 --> 00:12:07.920] Every day at 8 a.m., my newsletter goes out, and then I check, okay, what's in there?
[00:12:07.920 --> 00:12:08.640] What's interesting?
[00:12:08.640 --> 00:12:10.000] What could I say about this?
[00:12:10.000 --> 00:12:15.680] And as much as I actually like to see all these ideas and during the day, I just check it out because I'm curious.
[00:12:15.680 --> 00:12:18.800] I want to get some kind of insight into what's being talked about in the world.
[00:12:18.800 --> 00:12:21.440] That reaching out on Twitter, that's still marketing.
[00:12:21.440 --> 00:12:26.400] So, being a creator on social media will try to remain an authentic human being.
[00:12:26.400 --> 00:12:32.360] That is a current that sometimes pulls me towards my goals and sometimes perceivedly away from them, right?
[00:12:32.360 --> 00:12:39.800] It's hard to do marketing and stay authentic, and it's hard to stay authentic and do marketing if you're not capable of kind of unifying these two.
[00:12:39.800 --> 00:12:48.120] And another current that I feel very strongly here, particularly in our community of founders online, is being a consumer of social media.
[00:12:48.120 --> 00:12:57.480] I suffer a hard time maintaining a firm grasp on my own journey when everybody else's journey just seems to be flashing much more brightly around me.
[00:12:57.480 --> 00:13:05.480] Social media is highly selective, and people share the good stuff, they rarely share the bad stuff.
[00:13:05.480 --> 00:13:13.240] So, what we see is kind of this echo chamber of positivity-not necessarily toxic positivity, but it's selective positivity.
[00:13:13.240 --> 00:13:15.880] People share, oh, my MRR went up.
[00:13:15.880 --> 00:13:16.520] That's wonderful.
[00:13:16.520 --> 00:13:19.640] You get a screenshot, and you know, the graph goes to the top right.
[00:13:19.640 --> 00:13:22.120] Here's that, and look at this, this is how I did it.
[00:13:22.120 --> 00:13:27.640] I don't really see too many people sharing when their MRR goes down and with the screenshot that comes from that.
[00:13:27.640 --> 00:13:32.520] People do that occasionally, but it's like a what is it, nine-to-one relationship, right?
[00:13:32.520 --> 00:13:35.400] I don't really get to see them that often because people don't share them.
[00:13:35.400 --> 00:13:42.520] So, what we do see is that everybody or mostly everybody is doing well, and you just don't get to see the struggles because they're not posted.
[00:13:42.520 --> 00:13:48.360] And my own reality, where every day the MRR graph goes up and down as well, like there's always some movement.
[00:13:48.360 --> 00:13:50.440] Either way, it's a 50-50 chance.
[00:13:50.440 --> 00:13:53.720] Well, that's not represented in the social network around me.
[00:13:53.720 --> 00:13:57.160] And if it's not represented, I cannot perceive it accurately.
[00:13:57.160 --> 00:14:01.960] And if I can't perceive it accurately, my own journey is colored by a distortion.
[00:14:01.960 --> 00:14:05.720] And it doesn't even have to be envy or jealousy for this to affect you.
[00:14:05.720 --> 00:14:09.320] It's like Plato's cave: we're looking at shadows on the wall.
[00:14:09.320 --> 00:14:17.440] What we see are mirrors, silhouettes on the wall, and the reality is something behind us that we don't necessarily get to see because we only get to see the wall.
[00:14:17.440 --> 00:14:20.080] And quite literally, the Facebook wall and the Twitter feed.
[00:14:14.840 --> 00:14:21.120] It's very selective.
[00:14:21.440 --> 00:14:27.200] This kind of discrepancy is a strong current that I feel can often motivate me because I see other people doing well.
[00:14:27.200 --> 00:14:28.880] And I think I can do that too.
[00:14:28.880 --> 00:14:30.320] I want to get there too.
[00:14:30.320 --> 00:14:31.280] What do I need to do?
[00:14:31.280 --> 00:14:32.160] And then I do it.
[00:14:32.160 --> 00:14:37.760] But it can be disheartening in moments of doubt and moments of perceived failure, lack of success.
[00:14:37.760 --> 00:14:42.640] It's a strong feeling when it seems like everybody else is doing so well.
[00:14:42.960 --> 00:14:50.560] Final current that I found, and this is particularly hard, is the pull of work-life balance.
[00:14:50.560 --> 00:14:52.880] I try not to spend all day working.
[00:14:52.880 --> 00:15:01.200] I've been focusing more on balancing my own mental stability, which I derive from being with friends, family, from reading, from having hobbies, playing with my dog.
[00:15:01.200 --> 00:15:16.320] Yet combining the lack of technological stability with the pressure of social media presence, well, that makes me want to go and spend more time to reach my goals and less time away from work, which is also a goal, but one that isn't as directly perceived as like sitting in front of a computer.
[00:15:16.320 --> 00:15:27.680] So when I don't work, there's always a nagging thought, you could be spending time working, even though it wouldn't be necessarily productive or even helpful, might be distracting just working for the sake of working.
[00:15:27.680 --> 00:15:34.400] But we all understand now that you don't measure the quality of a software engineer by lines of code that they've written.
[00:15:34.640 --> 00:15:39.600] You measure by features implemented bugs fixed, efficiency gains, maybe sales made with the product.
[00:15:39.600 --> 00:15:42.480] You don't measure output, you measure impact.
[00:15:42.480 --> 00:15:45.200] Yet there's still this output-centric mindset.
[00:15:45.200 --> 00:15:46.560] And I suffer from this too.
[00:15:46.560 --> 00:15:53.600] This current that says more time working equals better results, or maybe equals a higher chance at better results.
[00:15:53.600 --> 00:15:59.360] It's kind of how we massage it into our brains, even though we know that too much work is actually detrimental.
[00:15:59.360 --> 00:16:01.880] And that's a current that I'm trying to swim against.
[00:16:02.200 --> 00:16:04.120] So it's just hard, right?
[00:16:04.120 --> 00:16:11.400] After 25 years of sitting in front of a computer, it's just so easy to fall into the same routine, check things, try to improve things a little.
[00:16:11.400 --> 00:16:14.200] It's really hard to step outside and not do that.
[00:16:14.200 --> 00:16:18.120] Your currents are probably going to look a little bit different from mine.
[00:16:18.120 --> 00:16:23.880] There might be overlap, and you might have the same ones, but feel pulled in a different direction.
[00:16:23.880 --> 00:16:27.960] You might view these forces maybe more benevolently or more malevolently.
[00:16:27.960 --> 00:16:40.440] But here's what I think is important about all of this: it's just realizing that these currents actually exist because they're often internally validated, but they're mostly external forces that are acting upon you.
[00:16:40.440 --> 00:16:44.840] People will share their MRR graphs and stories with or without you.
[00:16:44.840 --> 00:16:45.720] It doesn't matter.
[00:16:45.720 --> 00:16:48.920] Rapid developments in AI and frameworks, that's not your fault.
[00:16:48.920 --> 00:16:52.120] The fact that this causes more competition, also not your fault.
[00:16:52.120 --> 00:16:58.200] The fact that you picked an industry that now sees for some reason many people trying to build in it, that is also not your fault.
[00:16:58.200 --> 00:17:06.040] These are external forces, but we make them internal when we allow them to sweep us away without even knowing that we're moving.
[00:17:06.040 --> 00:17:15.800] The important part is to understand that these currents exist, to make them visible, to make them present, so that we can recognize them as currents and not as our own failings.
[00:17:15.800 --> 00:17:19.400] We shouldn't despair when we get pulled in a direction a little bit too much.
[00:17:19.400 --> 00:17:21.320] That's just what entrepreneurship is.
[00:17:21.320 --> 00:17:27.800] You're constantly torn from one side to the other, and you have to make different strokes to stay swimming where you want to be.
[00:17:27.800 --> 00:17:38.040] So a stronger current does make for stronger fish by the virtue of you reacting to it, but only if you know that you're swimming, only if you're aware of the water that you're in.
[00:17:38.040 --> 00:17:46.960] So, once you recognize the currents, you can choose to swim against them, swim with them, or maybe find the calm eddies where you can rest and reassess, kind of take yourself out of it.
[00:17:47.280 --> 00:17:54.640] You don't have to constantly follow all tech, you don't have to always try to work more or less.
[00:17:54.640 --> 00:17:58.400] You can just like set guidelines and act on them for a bit and just see what happens.
[00:17:58.400 --> 00:18:10.320] The currents will always be there, they change with the tides of technology, market forces, social dynamics, but awareness about them-that's your compass and deliberate action-that's your stroke, your swim stroke.
[00:18:10.320 --> 00:18:14.240] So, take a moment and feel the currents pulling at you.
[00:18:14.240 --> 00:18:18.960] Maybe name them to understand them better, then decide how you want to navigate them.
[00:18:18.960 --> 00:18:23.600] Because, in the end, you're not just trying to survive these waters, you're trying to get somewhere, right?
[00:18:23.600 --> 00:18:25.200] You're trying to build something meaningful.
[00:18:25.200 --> 00:18:28.560] And knowing the currents is the first step to charting your course.
[00:18:28.560 --> 00:18:30.560] Thanks so much for listening to the Bootstrap Founder.
[00:18:30.560 --> 00:18:34.160] Find me on Twitter at Avidka, A-R-V-I-D-K-A-H-L.
[00:18:34.160 --> 00:18:45.840] If you want to know what everyone's saying about your brand on over 3.8 million podcasts, podscan.fm tracks mentions in near real time with a powerful API that turns podcast conversations into actionable data.
[00:18:45.840 --> 00:18:59.520] And if you're hunting for your next business idea, get them delivered fresh from the podcast world at ideas.podscan.fm, where an AI extracts the best startup opportunities from 500 plus hours of expert conversations every day.
[00:18:59.520 --> 00:19:03.040] Share this with anyone who needs to stay ahead of the conversation.
[00:19:03.040 --> 00:19:03.920] Thanks for listening.
[00:19:03.920 --> 00:19:06.480] Have a wonderful day and bye-bye.