WEBVTT 00:00:00.000 --> 00:00:02.459 Imagine for a second that you're absolutely starving. 00:00:02.560 --> 00:00:05.139 You've got two options for dinner. Option A is 00:00:05.139 --> 00:00:09.339 this trendy five -star restaurant. You walk in. 00:00:09.460 --> 00:00:11.820 The service is instant. The food appears like 00:00:11.820 --> 00:00:14.820 magic. It's delicious. How good so far? But you 00:00:14.820 --> 00:00:17.320 have to admit, the kitchen is a total black box. 00:00:17.379 --> 00:00:19.280 You have no idea what's in the sauce. Right. 00:00:19.280 --> 00:00:21.140 And if you asked to see the recipe, they'd probably 00:00:21.140 --> 00:00:24.379 kick you out. Exactly. That's most AI tools today, 00:00:24.839 --> 00:00:29.839 like notebook LM, fast, polished. but opaque. 00:00:30.320 --> 00:00:33.560 Now option B, you're in your own kitchen, it's 00:00:33.560 --> 00:00:36.619 hot, it's messy, maybe you burn the toast, but 00:00:36.619 --> 00:00:39.060 you bought every single ingredient yourself. 00:00:39.200 --> 00:00:41.200 You know exactly what's going into that meal. 00:00:41.420 --> 00:00:43.859 And that, right there, is the trade -off Surf 00:00:43.859 --> 00:00:47.159 Sense is asking us to make. Welcome back to the 00:00:47.159 --> 00:00:50.090 Deep Dive. Today, we aren't just looking at another 00:00:50.090 --> 00:00:52.009 productivity app. We're looking at a tool that 00:00:52.009 --> 00:00:55.070 is trying to fundamentally shift the power dynamic 00:00:55.070 --> 00:00:57.530 between you and your data. We're talking about 00:00:57.530 --> 00:01:00.049 SurfSense. And this is so much bigger than just 00:01:00.049 --> 00:01:02.530 organizing files. The core theme here is really 00:01:02.530 --> 00:01:05.049 digital sovereignty. That's a heavy term. It 00:01:05.049 --> 00:01:08.230 is. But it boils down to a simple question. Do 00:01:08.230 --> 00:01:11.390 you own your thoughts? Or are you just renting 00:01:11.390 --> 00:01:14.799 them from a server somewhere in California? SurfSense 00:01:14.799 --> 00:01:17.920 is making a very bold pitch that you should be 00:01:17.920 --> 00:01:20.390 the chef in your own kitchen. even if that means 00:01:20.390 --> 00:01:22.689 you have to do the dishes. Even if it means doing 00:01:22.689 --> 00:01:25.329 the dishes yourself. I love that framing. So 00:01:25.329 --> 00:01:27.269 here's the roadmap. We're going to break down 00:01:27.269 --> 00:01:30.730 how this whole local AI thing works in practice. 00:01:30.890 --> 00:01:32.870 We'll look at the setup, the ability to actually 00:01:32.870 --> 00:01:35.189 edit your source documents, which is a feature 00:01:35.189 --> 00:01:38.290 I didn't know I needed, and the reality of running 00:01:38.290 --> 00:01:40.409 this offline. And we have to be honest about 00:01:40.409 --> 00:01:43.109 the fiction points because, you know, spoiler 00:01:43.109 --> 00:01:45.700 alert. Cooking at home takes longer than ordering 00:01:45.700 --> 00:01:47.540 takeout. It really does. We're going to get into 00:01:47.540 --> 00:01:50.540 the slow processing, the loud laptop fans, and 00:01:50.540 --> 00:01:52.359 why the audio features might be a total letdown. 00:01:52.439 --> 00:01:54.159 But let's start at the beginning. When you first 00:01:54.159 --> 00:01:57.280 open SurfSense, it feels different. It's dark. 00:01:57.400 --> 00:02:00.140 I mean, you open ChatGPT, and the UI is trying 00:02:00.140 --> 00:02:01.700 to be your best friend immediately. How can I 00:02:01.700 --> 00:02:04.060 help you today? Right. It's very eager. SurfSense 00:02:04.060 --> 00:02:07.739 just opens and it's quiet. It's empty. It felt 00:02:07.739 --> 00:02:09.639 a little like moving into a new house before 00:02:09.639 --> 00:02:13.199 you've unpacked any boxes. Just... white walls. 00:02:13.520 --> 00:02:16.099 That emptiness is intentional, though. It forces 00:02:16.099 --> 00:02:18.900 a mental shift. Most of us treat AI like a junk 00:02:18.900 --> 00:02:20.819 drawer. We just dump everything in and hope for 00:02:20.819 --> 00:02:23.479 the best. And SurfSense says no. SurfSense says 00:02:23.479 --> 00:02:26.439 no, you need to curate this. The whole interface 00:02:26.439 --> 00:02:30.139 is built on two concepts, spaces and sources. 00:02:30.319 --> 00:02:32.659 OK, let's talk about spaces. To me, that just 00:02:32.659 --> 00:02:34.759 sounds like a fancy word for folders. Is there 00:02:34.759 --> 00:02:37.180 a real difference? There is. And it's actually 00:02:37.180 --> 00:02:40.240 crucial. A space isn't just a folder. It's a 00:02:40.789 --> 00:02:43.490 A context container. A context container. Yeah. 00:02:43.490 --> 00:02:45.650 And your normal cloud drive, you might have a 00:02:45.650 --> 00:02:48.949 folder called work stuff with random PDFs. Do 00:02:48.949 --> 00:02:51.370 that in Surf sense. And the AI is going to get 00:02:51.370 --> 00:02:53.289 confused. It might hallucinate. Because it doesn't 00:02:53.289 --> 00:02:55.770 know what lens to look through. Exactly. It needs 00:02:55.770 --> 00:02:58.210 boundaries. The source we look at had this great 00:02:58.210 --> 00:03:00.930 example about naming. You can't just call a space 00:03:00.930 --> 00:03:03.810 test. Right. If you do that, the AI has no semantic 00:03:03.810 --> 00:03:06.449 anchor. It doesn't know if bank means a river 00:03:06.449 --> 00:03:08.949 bank or a financial institution. The example 00:03:08.949 --> 00:03:12.349 in the guide was Remote work tips, productivity, 00:03:12.569 --> 00:03:15.930 and health, which is a mouthful. It is, but look 00:03:15.930 --> 00:03:18.250 what it does. You're basically prompt engineering 00:03:18.250 --> 00:03:20.669 before you even ask a question. You're telling 00:03:20.669 --> 00:03:23.569 the system, hey, limit your scope to just this. 00:03:24.030 --> 00:03:26.550 You're priming the engine. So you're whispering 00:03:26.550 --> 00:03:29.590 the intent to the AI before you even upload a 00:03:29.590 --> 00:03:31.909 file. That's interesting. It makes you be more 00:03:31.909 --> 00:03:34.490 organized. It does. It's not for the lazy. It 00:03:34.490 --> 00:03:36.770 asks you to think about why you're saving something. 00:03:37.390 --> 00:03:39.949 So we have our box. We've named it with intention. 00:03:40.289 --> 00:03:42.349 Now we have to fill it. And this is where I think 00:03:42.349 --> 00:03:43.930 a lot of people are going to hit their first 00:03:43.930 --> 00:03:45.689 speed bump. Yeah, you're going to hit the processing 00:03:45.689 --> 00:03:48.389 wall. The dreaded progress bar. When you upload 00:03:48.389 --> 00:03:51.729 a PDF, it's not just storing it. It's indexing 00:03:51.729 --> 00:03:54.810 it locally on your machine. It's turning every 00:03:54.810 --> 00:03:57.969 word into vectors, which is just math the AI 00:03:57.969 --> 00:04:01.099 can read. And that takes horsepower. And there's 00:04:01.099 --> 00:04:03.560 a file limit, right? Something like 300 pages? 00:04:03.840 --> 00:04:06.159 Right. So you can't just upload a massive textbook 00:04:06.159 --> 00:04:08.780 in one go. The system will choke. You've got 00:04:08.780 --> 00:04:11.379 to split it up. But once that file is in there, 00:04:11.819 --> 00:04:13.840 something happens that I have not seen in other 00:04:13.840 --> 00:04:16.160 tools. And I think this is the aha moment. On 00:04:16.160 --> 00:04:18.759 the Editor feature. The document isn't static. 00:04:19.000 --> 00:04:21.079 No, it's a game changer for anyone who deals 00:04:21.079 --> 00:04:24.069 with messy data. You can actually type inside 00:04:24.069 --> 00:04:26.269 the source document. You can. Think about why 00:04:26.269 --> 00:04:29.050 that matters. A PDF is usually locked, right? 00:04:29.110 --> 00:04:31.790 It's like a photograph of text. But say you upload 00:04:31.790 --> 00:04:35.420 a scan from 1990. the OCR might mistake an S 00:04:35.420 --> 00:04:37.939 for a five. So you get FIFE offense instead of 00:04:37.939 --> 00:04:39.920 SurfSense. Exactly. And if you feed that garbage 00:04:39.920 --> 00:04:42.040 into a normal AI, it might get confused. It's 00:04:42.040 --> 00:04:45.000 just noise. In SurfSense, you can literally open 00:04:45.000 --> 00:04:48.079 the text layer, see that error, and just fix 00:04:48.079 --> 00:04:50.779 it. So you are scrubbing the data clean before 00:04:50.779 --> 00:04:53.139 the AI even touches it. It's the garbage in garbage 00:04:53.139 --> 00:04:55.199 out principle. You're cleaning the vegetables 00:04:55.199 --> 00:04:57.600 before you cook. You're ensuring the answer is 00:04:57.600 --> 00:04:59.699 actually accurate. I can see that being huge 00:04:59.699 --> 00:05:01.379 for researchers. But, you know, we don't just 00:05:01.379 --> 00:05:03.800 live in a world of PDFs. Half my reading is just 00:05:03.800 --> 00:05:06.660 watching YouTube videos. And SurfSense knows 00:05:06.660 --> 00:05:10.019 that. It calls itself a digital binder. It's 00:05:10.019 --> 00:05:11.720 trying to flatten the information hierarchy. 00:05:12.220 --> 00:05:14.060 It doesn't care if the data came from a hardcover 00:05:14.060 --> 00:05:16.720 book or a YouTuber. It's all just data. Tell 00:05:16.720 --> 00:05:19.269 me about the video workflow. Because my watch 00:05:19.269 --> 00:05:21.910 later playlist is basically a graveyard where 00:05:21.910 --> 00:05:24.589 content goes to die. We all have that graveyard. 00:05:25.089 --> 00:05:27.170 Yeah. SurfSense changes that. You take the URL 00:05:27.170 --> 00:05:29.889 for, say, a 45 -minute video on home office economics, 00:05:30.110 --> 00:05:32.290 and you just paste it in. And it doesn't just 00:05:32.290 --> 00:05:34.410 save a link. No. It rips out the transcript. 00:05:34.589 --> 00:05:36.329 It pulls all the spoken words and turns them 00:05:36.329 --> 00:05:38.730 into text. So now, in your remote workspace, 00:05:39.149 --> 00:05:41.670 you've got a PDF guys, a blog post, and the full 00:05:41.670 --> 00:05:44.329 text from that video. And the AI sees them all 00:05:44.329 --> 00:05:48.060 as equal. That's the moment of wonder. You can 00:05:48.060 --> 00:05:50.160 ask a question, and it can pull a quote from 00:05:50.160 --> 00:05:53.339 page 10 of a PDF and combine it with a tip from 00:05:53.339 --> 00:05:56.740 the 20 -minute mark of a YouTube video. It synthesizes 00:05:56.740 --> 00:05:59.560 across formats. That is powerful. It's like having 00:05:59.560 --> 00:06:01.819 a research assistant who watches the videos for 00:06:01.819 --> 00:06:04.259 you. But, okay, having the data is one thing. 00:06:04.339 --> 00:06:06.639 Getting good answers out, that's where I usually 00:06:06.639 --> 00:06:09.019 struggle. I'll admit it, I'm a lazy prompter. 00:06:09.279 --> 00:06:12.439 To summarize this prompt, we all are. But with 00:06:12.439 --> 00:06:15.009 a tool like this, Precision really pays off. 00:06:15.269 --> 00:06:17.709 It has this mentions feature, kind of like on 00:06:17.709 --> 00:06:20.949 social media. It's critical for local AI. You 00:06:20.949 --> 00:06:22.350 have to remember this is running on your laptop, 00:06:22.509 --> 00:06:25.250 not a supercomputer. If you ask a generic question, 00:06:25.569 --> 00:06:27.730 it has to scan everything. It's inefficient. 00:06:28.089 --> 00:06:31.529 Very. But with mentions, you point the flashlight. 00:06:31.629 --> 00:06:34.910 You type the at at symbol. And I can say, at 00:06:34.910 --> 00:06:37.250 YouTube video, what did it say about chair height? 00:06:37.430 --> 00:06:40.639 Exactly. You're telling the AI, ignore the PDFs, 00:06:40.660 --> 00:06:43.579 focus only on this. It's constraints -based prompting. 00:06:43.680 --> 00:06:46.259 It gets you bitter answers faster. The guide 00:06:46.259 --> 00:06:48.600 had some great examples. One was asking for a 00:06:48.600 --> 00:06:51.839 comparison table. Yes. Create a table comparing 00:06:51.839 --> 00:06:55.220 the advice at PDF and at video. And the result, 00:06:55.319 --> 00:06:58.959 was it good? The content was accurate, but visually 00:06:58.959 --> 00:07:00.959 it was a little rough. Squished was the word 00:07:00.959 --> 00:07:03.189 I saw. Very squished, yeah. You had to scroll 00:07:03.189 --> 00:07:05.529 sideways to read it. It doesn't have that polished 00:07:05.529 --> 00:07:08.230 design you'd get from Google. But the information 00:07:08.230 --> 00:07:10.670 was spot on. It correctly identified that the 00:07:10.670 --> 00:07:13.970 PDF focused on time blocking while the video 00:07:13.970 --> 00:07:16.790 was all about disk ergonomics. That's a high 00:07:16.790 --> 00:07:18.810 level synthesis that would take me 20 minutes 00:07:18.810 --> 00:07:21.870 to do by hand. And it did it in seconds. Another 00:07:21.870 --> 00:07:25.009 great one was the quiz generation. Oh, for students 00:07:25.009 --> 00:07:29.089 this must be gold. It is. Create 10 multiple 00:07:29.089 --> 00:07:32.620 choice questions based on at textbook. and it 00:07:32.620 --> 00:07:36.000 generates a test with an answer key. That's amazing 00:07:36.000 --> 00:07:39.180 for active recall. But the thing that really 00:07:39.180 --> 00:07:42.379 builds trust for me is the citations. The little 00:07:42.379 --> 00:07:44.300 numbers. The little numbers. When it gives you 00:07:44.300 --> 00:07:45.980 an answer, there's a little number at the end 00:07:45.980 --> 00:07:48.060 of the sentence. And when you click it, it doesn't 00:07:48.060 --> 00:07:50.399 just take you to the document. It highlights 00:07:50.399 --> 00:07:52.600 the exact sentence in the source text where it 00:07:52.600 --> 00:07:54.660 got that information. That's the accountability. 00:07:54.779 --> 00:07:57.620 That's checking the chef's work. Precisely. It 00:07:57.620 --> 00:07:59.860 makes it really easy to spot hallucinations. 00:08:00.479 --> 00:08:03.800 If the AI says the moon is made of cheese, and 00:08:03.800 --> 00:08:05.939 cites page four, you can click and immediately 00:08:05.939 --> 00:08:07.959 see it actually says the moon is made of rock. 00:08:08.100 --> 00:08:10.639 Okay, so we've got our spaces, our data is clean, 00:08:10.800 --> 00:08:13.420 we're prompting with the at symbol, but does 00:08:13.420 --> 00:08:16.319 this tool live on an island? Or does it connect 00:08:16.319 --> 00:08:18.860 to anything else? It's surprisingly social for 00:08:18.860 --> 00:08:21.920 a privacy tool. It integrates with Gmail, Google 00:08:21.920 --> 00:08:26.620 Drive, Discord, and This is the big one, Notion. 00:08:26.800 --> 00:08:29.300 Notion users are a passionate bunch. I say that 00:08:29.300 --> 00:08:31.379 as one of them. It's a whole lifestyle. Yeah. 00:08:31.500 --> 00:08:34.879 And SurfSense taps right into it. The guide detailed 00:08:34.879 --> 00:08:37.679 a use case with messy meeting notes that I think 00:08:37.679 --> 00:08:39.980 will resonate. Walk us through that because getting 00:08:39.980 --> 00:08:42.299 notes out of Notion is usually a pain. Well, 00:08:42.460 --> 00:08:44.740 normally you'd have to export to PDF. download 00:08:44.740 --> 00:08:47.259 it, re -upload it, it's friction. With SurfSense, 00:08:47.360 --> 00:08:49.460 you just connect it directly to a specific Notion 00:08:49.460 --> 00:08:51.519 page. And then you can prompt it, like, look 00:08:51.519 --> 00:08:54.120 at meeting notes and list my to -dos. And it 00:08:54.120 --> 00:08:56.419 spits out a clean list with due dates. It turns 00:08:56.419 --> 00:08:58.620 that mess into an action plan. Yeah. And it's 00:08:58.620 --> 00:09:01.000 a live connection, so if you update Notion, SurfSense 00:09:01.000 --> 00:09:03.100 sees the changes. That is incredibly useful. 00:09:03.399 --> 00:09:05.559 But now we have to talk about the elephant in 00:09:05.559 --> 00:09:09.179 the room. or the server in the room. The local 00:09:09.179 --> 00:09:11.419 mode. This is what separates SurfSense from everything 00:09:11.419 --> 00:09:13.179 else, isn't it? It's the whole point. It is. 00:09:13.220 --> 00:09:15.840 I mean, with chat GPT, your data gets sent to 00:09:15.840 --> 00:09:18.539 a massive server farm. Your tax returns, your 00:09:18.539 --> 00:09:21.600 diary, it all leaves your house. Which creates 00:09:21.600 --> 00:09:23.879 a vulnerability, even if you trust the company. 00:09:24.039 --> 00:09:26.519 Exactly. SurfSense says you don't need to trust 00:09:26.519 --> 00:09:28.779 them. You can download the brain, the actual 00:09:28.779 --> 00:09:31.740 AI model, like Llama 3, directly onto your laptop. 00:09:31.919 --> 00:09:34.220 So I can literally just turn off my Wi -Fi. You 00:09:34.220 --> 00:09:38.169 can pull the ethernet cable. Be on a plane. It 00:09:38.169 --> 00:09:41.830 will still work. Total privacy. The data never 00:09:41.830 --> 00:09:44.450 leaves your hard drive. That sounds like magic. 00:09:45.049 --> 00:09:47.049 But there has to be a catch. You can't run a 00:09:47.049 --> 00:09:49.470 supercomputer on a MacBook without some consequence. 00:09:49.669 --> 00:09:52.190 And the catch is your hardware. These brains 00:09:52.190 --> 00:09:54.549 are heavy. They need a lot of RAM, a lot of GPU 00:09:54.549 --> 00:09:57.210 power. So if I'm on a five -year -old laptop... 00:09:57.210 --> 00:09:59.730 It's gonna struggle. The fans will spin up like 00:09:59.730 --> 00:10:02.580 a jet engine. Your battery will drain. And it's 00:10:02.580 --> 00:10:04.820 going to be slow. How slow are we talking? Instead 00:10:04.820 --> 00:10:06.480 of an instant answer, you might wait 30 seconds. 00:10:06.700 --> 00:10:09.200 The interface itself might lag. Your computer 00:10:09.200 --> 00:10:11.139 is doing the work a data center normally does. 00:10:11.399 --> 00:10:13.460 You can feel the weight of it. So that's the 00:10:13.460 --> 00:10:16.279 trade -off, privacy for performance. And patience, 00:10:17.059 --> 00:10:19.580 which brings us to the rough edges. We promised 00:10:19.580 --> 00:10:22.320 we'd be honest about this. Yes. And the source 00:10:22.320 --> 00:10:24.360 material was pretty brutal about some of the 00:10:24.360 --> 00:10:26.419 failings. The biggest ones seemed to be audio. 00:10:26.759 --> 00:10:30.179 Yeah. We talked about Notebook LM and its audio 00:10:30.179 --> 00:10:33.220 overview feature, which is amazing. It generates 00:10:33.220 --> 00:10:35.779 a podcast on the fly. SurfSense claims to do 00:10:35.779 --> 00:10:39.480 it, too. But in testing? It failed. Repeatedly. 00:10:39.559 --> 00:10:42.279 Just error messages. The author tried to generate 00:10:42.279 --> 00:10:45.399 a summary of that remote workspace, and it just 00:10:45.399 --> 00:10:47.480 wouldn't compile. And when it finally did work? 00:10:47.519 --> 00:10:49.919 The reports say it sounded robotic, like an old 00:10:49.919 --> 00:10:52.960 GPS voice. It sounded like a computer reading 00:10:52.960 --> 00:10:55.600 a text file. So if you want a smooth audio summary 00:10:55.600 --> 00:10:59.299 for your jog, This is not the tool. No, stick 00:10:59.299 --> 00:11:01.159 to Notebook LM for that. This is for reading 00:11:01.159 --> 00:11:03.440 and analyzing, not listening. In the general 00:11:03.440 --> 00:11:05.860 performance, you mentioned that heaviness. The 00:11:05.860 --> 00:11:08.600 word used was clunky, like buttons taking five 00:11:08.600 --> 00:11:10.480 or six seconds to respond. That doesn't sound 00:11:10.480 --> 00:11:13.500 like much, but in 2024, six seconds is an eternity. 00:11:13.700 --> 00:11:16.539 It breaks your flow. You click save and you have 00:11:16.539 --> 00:11:19.379 to wait. It's a constant reminder that this is 00:11:19.379 --> 00:11:22.259 complex software running locally, not some slick 00:11:22.259 --> 00:11:25.480 web app. Functional, not beautiful. A tool for 00:11:25.480 --> 00:11:28.639 a workbench. Not a toy. Exactly. And for some 00:11:28.639 --> 00:11:31.000 people, that's a deal breaker. If you want that 00:11:31.000 --> 00:11:34.500 seamless, Apple -like experience, you will be 00:11:34.500 --> 00:11:36.679 frustrated. So let's bring this all together. 00:11:37.139 --> 00:11:39.460 We have a tool that gives you total data ownership, 00:11:39.860 --> 00:11:42.720 but it's slow, a bit clunky, and some features 00:11:42.720 --> 00:11:47.210 are half -baked. Who is this actually for? I 00:11:47.210 --> 00:11:49.669 think it's for two very specific groups. First, 00:11:49.970 --> 00:11:52.830 the privacy absolutists. Lawyers, researchers 00:11:52.830 --> 00:11:55.250 with sensitive IP, or just anyone who hates the 00:11:55.250 --> 00:11:58.169 idea of big tech scanning their data. For them, 00:11:58.230 --> 00:12:00.789 this is the only game in town. Right. And the 00:12:00.789 --> 00:12:03.590 second group is the organizers. The people who 00:12:03.590 --> 00:12:05.669 want to curate a library, who want to fix the 00:12:05.669 --> 00:12:08.009 typos, who want to build a second brain that 00:12:08.009 --> 00:12:10.450 is actually theirs, they'll put up with the friction 00:12:10.450 --> 00:12:12.190 for the control. It really does come back to 00:12:12.190 --> 00:12:14.389 that cooking analogy we started with. It does. 00:12:14.750 --> 00:12:16.690 SurfSense is home cooking. It's messy. You have 00:12:16.690 --> 00:12:18.870 to chop the onions yourself. The fans will spin. 00:12:19.309 --> 00:12:21.409 But you made the meal. You know what's in it. 00:12:21.490 --> 00:12:24.590 And the cloud tools are fast food. Convenient, 00:12:24.809 --> 00:12:26.769 tasty, but you're eating what they serve you. 00:12:27.049 --> 00:12:29.360 And look, sometimes you just want a burger. There's 00:12:29.360 --> 00:12:31.500 nothing wrong with that. I use cloud AI every 00:12:31.500 --> 00:12:33.940 day for quick things, but for the important stuff. 00:12:35.299 --> 00:12:37.539 You might want a home -cooked meal. I think that's 00:12:37.539 --> 00:12:40.399 the perfect way to fame it. It's not about one 00:12:40.399 --> 00:12:42.700 being better. It's about the right tool for the 00:12:42.700 --> 00:12:45.500 job. Exactly. So here's our challenge to you, 00:12:45.500 --> 00:12:47.679 the listener. Don't try to switch your whole 00:12:47.679 --> 00:12:51.100 life over to SurfSense today. Just try one small 00:12:51.100 --> 00:12:54.860 project. Just one. Maybe it's your tax prep or 00:12:54.860 --> 00:12:58.679 planning a vacation. Create a space. Upload three 00:12:58.679 --> 00:13:01.740 or four documents, try fixing a typo in the editor, 00:13:02.139 --> 00:13:03.919 and just see how it feels. See if the friction 00:13:03.919 --> 00:13:05.879 is worth that feeling of ownership. You might 00:13:05.879 --> 00:13:07.860 find you actually like being the chef. And if 00:13:07.860 --> 00:13:10.419 your laptop fan starts sounding like a helicopter. 00:13:10.960 --> 00:13:13.000 That's the sound of privacy. Thanks for diving 00:13:13.000 --> 00:13:14.600 in with us. We'll see you in the next one. Take 00:13:14.600 --> 00:13:14.779 care.