0:01 I believe the important thing isn't age 0:03 , but rather whether our Vibe Coders 0:06 have the ability to identify problems. 0:10 Today is the day the second dream was 0:12 realized. 0:14 >> The quote I got for building an app was 0:16 this much. So, there is someone who 0:18 decided to build it themselves. The age 0:21 they first started coding was fifty. 0:25 They weren't a major in the field, 0:26 either. They are still working a 0:28 full-time job. Their job is quite 0:30 unique. It was my first time talking to 0:32 someone with this profession. This 0:35 person’s special job will be revealed 0:36 at the end of the video. They went 0:38 around in circles while self-studying 0:40 for five years. From HTML to Flutter, 0:43 No-Code, ChatGPT, and Cursor, they 0:45 spent five years self-studying before 0:48 meeting To-The Class. And they launched 0:51 two apps they built themselves. They 0:54 also filed for patents twice. The first 0:56 time, it cost about 3 million won 0:58 through a patent attorney, but for the 1:01 second patent, they wrote the 1:02 specification with Claude and filed it 1:05 themselves for 655,000 won. This is the 1:07 story of Park Jae-hong, a student in 1:10 our coding class today. I asked how 1:12 they turned ideas into apps, how they 1:15 refined patent specifications with AI, 1:17 and the secret to not burning out over 1:19 five years. If you watch until the end, 1:23 you will see the two dreams Park 1:24 Jae-hong wrote in their graduation 1:26 album as a child. They achieved both. 1:29 Hello. I am To-The-Jay. If you are 1:31 hesitating to start Vibe Coding because 1:34 of your age or for no reason at all, 1:36 please watch this video until the end. 1:38 Now, let's welcome Park Jae-hong. Hello 1:41 . Yes. 1:42 >> Hello. Yes. 1:43 >> Hello. Hello. Yes. 1:45 >> Nice to meet you. Could you please 1:46 briefly introduce yourself? I 100%agree 1:49 with the experts who say that the era 1:51 of the "super-individual" has opened 1:54 thanks to AI, and I am Park Jae-hong, a 1:57 57-year-old who is still an office 1:59 worker, developing various apps through 2:02 Vibe Coding while dreaming of becoming 2:04 a billionaire. Yes. 2:06 >> Nice to meet you. Yes. First, I'm 2:08 curious about when and why you started 2:10 coding, and could you explain how you 2:13 found out about our To-The coding class 2:16 ? 2:16 >> About six years ago, I had to transfer 2:18 at Seoul National University of 2:19 Education Station, and as soon as the 2:21 doors opened on Subway Line 2, people 2:23 started sprinting. They were probably 2:25 running anxiously to catch the Line 3 2:27 train. Seeing that situation, I thought 2:31 , wouldn't they not have to run if 2:33 someone provided them with train 2:35 arrival information? I thought it might 2:39 be profitable to patent this idea and 2:41 sell it, so I filed a patent around 2:43 January or February 2022, and it took 2:46 about a year through a patent attorney. 2:49 I received the patent certificate in 2:52 January 2023. So, as a next step, I 2:56 selected five mobility companies—like 2:58 Kakao, TMAP, SK, and others at a time 3:01 when shared electric scooters were 3:04 booming—and sent them the patent 3:06 introduction video and the patent 3:09 certificate by mail. "Buy my idea," I 3:12 said. Yes. 3:14 >> But as you know, it didn't work out. I 3:17 didn't get any response. 3:18 >> Yes. Yes. Patents don't really get 3:20 responses that quickly anyway. Yes. 3:21 >> Yes. Then I thought, maybe it would be 3:24 easier to sell if I made it into an app 3:26 , so I requested a quote. The result 3:29 that came back was that the development 3:31 cost alone was 100 million won. I guess 3:35 I was too ignorant about the 3:36 development field; I thought maybe 3:38 around 10 million won would be a bit 3:40 burdensome but manageable, but after 3:42 receiving that quote... 3:44 >> Right. Oh, I was completely devastated. 3:46 >> That’s a very bold investment. It’s 3:48 something where you don't even know if 3:51 it will work out. Yes. Yes. 3:53 >> I also didn't have the money. 3:56 >> But since I had already put in so much 3:58 cost and it had taken over a year, it 4:00 felt like such a waste to give up, so I 4:02 thought, "In that case, let me try 4:04 developing it myself." 4:07 >> And so began my five years of 4:08 struggling with self-taught coding. 4:10 >> Ah, what led you to discover "To The J" 4:13 ? I’ve been a subscriber to your 4:16 videos since you first started. 4:18 >> I remember the very first one. 4:21 >> With the keyboard, right? That's right. 4:24 Yes. 4:24 >> You were showing it and talking about 4:27 it. It was so impressive. "Who is this 4:31 person?" It was very unique. 4:34 >> Since then, I’ve kept watching as a 4:37 subscriber. 4:38 >> Yes. Then I found out that your lecture 4:40 videos had been uploaded. But I didn't 4:42 have the courage to start. Was it 144 4:44 lectures? It was so many. There were so 4:48 many, and since I have a full-time job 4:50 and I want to enjoy my weekends, I was 4:52 worried about whether I could handle 4:55 the course, so I joined late. 4:58 >> I’m so grateful you remember the very 5:00 first video, and did you encounter the 5:02 TTJ 17-step profit pipeline course 5:04 after your five years of self-study? I 5:06 think it was almost the end of my 5:08 self-study period. Because I had been 5:10 studying only by piecing together 5:12 necessary information from online 5:14 development courses and YouTuber videos 5:16 , yes. 5:18 >> Even though I felt like I had studied a 5:20 lot, I felt a sense of unease because 5:22 things weren't systematic, but after 5:24 encountering your lectures, I felt I 5:26 needed to give it a try, so I went 5:28 through the course about three times. 5:33 You explained things so well and made 5:35 it so interesting that the lectures 5:37 were incredibly beneficial, and I 5:39 learned about a world I knew nothing 5:42 about—the development field—and 5:44 discovered that with just one skill, 5:46 there are so many ways to build income 5:48 streams. 5:50 >> Yes. 5:50 >> The concept of the "micro-app" was 5:53 truly shocking to me. Yes. Yes. Even at 5:56 that time, yes. 5:57 >> Yes. Yes. I only thought that apps or 6:00 websites with high-level technology and 6:02 numerous features were the ones that 6:04 succeeded. 6:07 >> But you showed me the reality that even 6:09 simple notepad or calculator apps could 6:10 generate massive revenue, and it was 6:12 like being hit on the back of the head 6:14 —I realized you were no ordinary 6:15 person. There weren't any other 6:19 YouTubers who shared stories like yours 6:21 , Todo-Jane. I’ve watched many 6:23 different lectures, but 6:24 >> Yes. 6:26 >> you approached it from a completely 6:28 different level, so I think your 6:31 lectures were a great opportunity for 6:33 me to finally organize all the 6:35 disorganized information and materials 6:38 I had been collecting. 6:41 >> Thank you. If you don't mind me asking, 6:43 are you 57 years old this year? 6:45 >> Yes. Yes. That is correct. I was born 6:47 in '69. 6:48 >> So, you started coding in your early 6:52 50s, which is quite a milestone; I’m 6:56 curious if you faced any barriers in 7:00 that process. 7:02 >> I saw someone in a video you introduced 7:05 earlier say the same thing, and they 7:07 mentioned it didn't matter at all. I 7:10 feel the same way. I’ve rarely 7:13 thought to myself, "I'm already 57 or 7:15 58." What's important isn't age, but 7:17 rather whether we, as Vibe Coders, have 7:20 the ability to identify problems— 7:22 that's what I believe. The situation of 7:25 people running around in subway 7:27 stations years ago was the same even 30 7:29 years ago when I was a college student, 7:31 yes. 7:32 >> It will likely be the same six years 7:33 from now. But six years ago, I looked 7:36 at that situation, drew an idea from it 7:39 , and developed an app. The ability to 7:43 observe a situation and extract a 7:44 question mark from it—isn't that 7:46 what's more important? Regardless of 7:49 age. The era of Vibe Coding has arrived 7:52 , where anyone can easily create web 7:54 apps, so I think all sorts of things 7:56 will start pouring out. The key will be 7:59 whether we can truly create apps or 8:01 websites that are beneficial to society 8:03 . 8:04 >> Then, wouldn't it be a good idea to 8:06 cultivate the ability to identify and 8:08 address the inconveniences around us 8:10 instead of just letting them slide? 8:12 Thank you for your wonderful words. By 8:14 the way, if you don't mind me asking, 8:17 is your line of work related to IT or 8:19 perhaps planning? 8:21 >> Oh, it's not? 8:22 >> Not at all. I think I can talk about 8:25 that at the very end. 8:26 >> Yes. Yes. Understood. I heard you 8:29 created an app yourself, could you 8:31 please introduce it to us? 8:33 >> The app is called "Don't Run." Well, I 8:37 made it six years ago after seeing 8:38 people running around in the subway 8:40 station. Office workers commute every 8:44 day, taking the same bus stops and the 8:46 same bus routes, and boarding the same 8:48 subway lines in the same direction at 8:51 the same stations. It's the same for 8:54 commuting back home and transferring; 8:56 they move along the same patterns every 8:59 Monday through Friday. 9:01 >> So, I saved that same route onto a 9:03 single button. Yes, yes. So when you 9:05 need it, you just press that one button 9:07 , and it informs you by voice, like " 9:09 arriving in X minutes." 9:10 >> Until now, you always had to select the 9:13 departure and arrival points in subway 9:15 apps, and that process is actually 9:17 quite tedious. When you do it every 9:19 single day. 9:20 >> So, the idea was sparked by bundling 9:23 those daily repetitive actions into one 9:25 . 9:25 >> Yes. And do you have one more app? 9:28 >> Yes. Yes. Yes. The second one is an app 9:31 called "Running Food." 9:33 >> Hmm. Since I go running, I wanted to 9:36 see at a glance how much I worked out 9:39 in a month. 9:40 >> I use Google Calendar and check it 9:44 often. 9:45 >> Every time I check it, I thought it 9:47 would be great if my running records 9:48 were on there. While trying to solve 9:51 that problem and talking with AI, I 9:53 learned that when you run, you lose 9:55 certain nutrients that must be 9:57 replenished through food. I learned 10:00 things like that, and realized these 10:02 needs differ for everyone. 10:05 >> I found that it can be calculated more 10:07 accurately depending on your gender, 10:10 age, and weight. 10:12 >> I also learned how much was consumed, 10:14 and that's how the app started and came 10:16 to be. 10:18 >> And I saw in the photos that you can 10:20 take a picture of food with the camera 10:22 and the AI calculates the calories—is 10:23 that feature available too? I've made 10:27 some promotional videos, a few dozen 10:28 seconds long, for the "Don't Run" app 10:30 and the "Running Food" app I mentioned. 10:33 I can show you; this is the "Don't Run" 10:37 app. If you take a look, yes, a button 10:40 is generated. I've set the route. 10:42 >> Arriving soon, Gwanak No. 6, entering 10:44 the station, current location is Guro 10:46 Digital Complex Station. 10:47 >> This kind of voice alert is also 10:49 possible in the background, yes. 10:50 >> So if I'm wearing earphones, it will 10:52 keep notifying me. 10:53 >> Yes, that's correct. The second one is 10:55 Running Food, and I actually worked out 10:58 today. If you do it like this, today's 11:00 running record pops up. I ran 11km, it 11:02 took an hour, so I search for food. 11:05 Then the AI coach explains the food 11:08 briefly. 11:11 >> When I record that I'm going to eat 11:12 this, a supplement score appears. With 11:15 the food I had today, I only got a 22% 11:19 score. I filled in all the nutrients 11:22 consumed by exercise today with food. 11:26 >> Now the food shows up, confirming that 11:28 all the nutrients are 100%filled, and 11:31 it's an app that roughly shows calories 11:33 and how much body weight was lost today 11:36 . 11:37 >> That fits very well. Yes. 11:38 >> What platform did you use to build this 11:41 ? Like Flutter or Xcode? 11:43 >> That's right. It's Flutter. 11:45 >> I'm curious how long it took. 11:47 >> Ddeuji-mas took almost a year. 11:49 >> Hmm. Yes. Without a plan, I just built 11:53 features as needed, which caused errors 11:55 and trial and error, so it took nearly 11:57 a year. But this one was made in almost 12:00 10 days. 12:00 >> In just 10 days? 12:02 >> The functions were made in 10 days, but 12:03 as I got a bit more ambitious, it took 12:05 two and a half months. 12:06 >> Is the app you filed a patent for 12:09 Ddeuji-mas? 12:10 >> It's both. 12:11 >> You filed for both, I see. 12:12 >> What was the process like when you 12:14 filed them? 12:15 >> For Ddeuji-mas, as I mentioned earlier. 12:19 I was introduced to a patent attorney 12:22 back then, so there were some costs 12:24 involved. At the time, it was around 12:28 1.5 million won, and a year later there 12:31 was a success fee concept, so it cost 12:33 about 3 million won in total. 12:36 >> Just for the filing? 12:37 >> Up to the examination for registration. 12:39 >> It got registered. Yes. So it cost 12:41 about 1.5 million won. Yes. But this 12:44 time for Running Food, yes. 12:46 >> I thought about asking for help again. 12:48 >> Yes. But with AI getting so much better 12:53 , I thought it might be possible. This 12:56 time, let's try it through AI. 12:58 >> Self-service. 13:00 >> Let's try to register it. So. 13:03 >> That's how I started, but when I talk 13:07 to a patent attorney, it's hard to ask 13:10 them to add this or that or emphasize 13:14 certain points. 13:16 >> Yes. Because contacting them every time 13:19 to explain things in detail is, well. 13:21 >> It's tiring work. Yes. And. 13:25 >> So when doing it with AI, there's none 13:27 of that, but the slightly disappointing 13:29 part is, can you trust the AI? 13:33 >> To figure it out, I instructed it to 13:36 analyze the project carefully. I give 13:39 it instructions, saying I'm going to 13:41 register for a patent myself. "Analyze 13:44 this carefully and create a 13:46 specification from the perspective of a 13:48 patent attorney." That’s how I 13:50 request it. And it creates it for me. 13:52 After that, I close the Claude window. 13:56 I have it analyze the project the same 13:57 way again and create a specification as 13:59 an expert patent attorney, but since I 14:01 already have one, I tell it to review 14:03 it and supplement it if anything is 14:04 missing. As you likely know, the reason 14:08 I close the window and start fresh is 14:10 that when you keep chatting in one long 14:12 session, it sometimes starts to lag or 14:14 say weird things. I think I did it 14:16 about seven times. 14:18 >> Closing the window, reopening it, 14:20 giving the initial specification to 14:22 Claude, and telling it to refine it. So 14:25 you repeated this process about seven 14:27 times. Seven 14:28 >> times, so you don't really need to do 14:30 more. 14:31 >> At 14:32 >> this point, it's pretty much perfect. 14:34 >> Yes. I got that, and with the final 14:37 version, I registered for the patent 14:39 myself. I learned this recently too, 14:42 that there's patent filing and then 14:44 there's patent examination. 14:46 >> Yes. Yes. I didn't request the 14:48 examination yet; I only did the filing. 14:51 The examination doesn't proceed until I 14:53 specifically request it. The reason for 14:55 only filing is because of the filing 14:57 date. 14:58 >> When similar patents clash in the 15:01 office, 15:02 >> it comes down to which one was filed 15:04 first. 15:05 >> Who filed it first. Yes. 15:07 >> Since priority is important, the 15:09 strategy is to just file to secure the 15:11 date quickly, because you never know if 15:13 the app will be successful or not 15:14 anyway. 15:15 >> Yes. Ah, that’s right. Yes. I figured 15:17 there was no need to spend high costs 15:19 on the examination yet. That's what 15:21 that friend told me. AI told me that 15:23 for the examination, if the app does 15:25 well later and copycat apps appear, I 15:26 can give them a warning, and if they 15:28 still don't stop, that's when I request 15:30 the examination. 15:32 >> Since I already filed it in advance, 15:33 >> Exactly. When the examination happens, 15:36 I have the priority of the filing right 15:37 , so the rights belong to me. So it 15:39 taught me that strategy. AI, or Claude, 15:42 can help reduce costs that way. 15:45 >> Oh. Yes. Yes. Actually, I learned today 15:48 for the first time that you can file 15:50 for a patent yourself, so this feels 15:52 like a huge tip. Yes. I heard that you 15:56 didn't just stop at filing, but used AI 15:58 for everything from the app name to the 16:00 logo, and built things up with AI. Do 16:03 you have any of your own know-how in 16:06 that process? Well. My know-how is that 16:10 for "Didi-mus," the logo was created by 16:14 GPT. And while I came up with the name, 16:17 for "Learning Food," both the logo and 16:20 the name were created by Claude. 16:22 >> Yes. For the Running Food app, the 16:25 image and name suggested at once were 16:28 just accepted as they were. However, 16:30 there was one thing before that. Just 16:32 like when making a patent specification 16:34 earlier, I made it understand exactly 16:36 and thoroughly what kind of app this is 16:38 , and then asked it to create a logo 16:40 and name that suits it. 16:42 >> The initial process of making it 16:43 understand is very important. Yes. Yes. 16:46 Yes. Other than that, I don't think I 16:48 had any special know-how. What I would 16:51 like to add is that for Running Food, 16:55 before giving instructions to make it, 16:58 I personally asked it to reflect colors 17:02 suitable for an exercise and health app 17:06 and to create a good design. Ah, well, 17:11 there are many people who can't launch 17:13 even with AI's help, but the fact that 17:16 you completed, launched, and even filed 17:18 for a patent makes me think you are 17:21 certainly exceptional and have a 17:23 special ability to produce results. It 17:26 seems like know-how, motivation, and 17:28 mindset are important—do you have 17:30 anything special in those areas? When I 17:33 started this five years ago, I began 17:37 with HTML, CSS, and JavaScript, and 17:40 then, as I mentioned, I greedily tried 17:44 to do both iOS and Android without 17:47 knowing how, and when I finally pulled 17:51 bus or subway APIs and displayed them 17:54 on my screen, that was the best feeling 17:58 ever. I couldn't make any more progress 18:02 , so I tried easier things like Notion 18:05 or Bubble, but the downside was that 18:07 they were too slow. There were many 18:10 twists and turns as I looked around, 18:13 and then I met GPT. Was it in 2022? In 18:17 December, I heard AI could do coding, 18:19 so I thought, "Oh, maybe I can survive, 18:21 " and that's when I met Cursor. 18:25 >> Thanks to Cursor, I studied and built 18:28 the app, but because I added features 18:32 here and there without a plan out of 18:35 greed, errors and crashes occurred, so 18:38 I decided to simplify it, removed 18:42 everything, and that’s how this 18:45 current model came to be. Because I 18:49 went about it in such a disorganized 18:51 way, the process was difficult. It took 18:54 a lot of time, and even while using AI, 18:57 it took a whole year. Although there 19:00 were difficult parts, I don't think I 19:02 ever considered this process to be hard 19:04 . That's because I spend a lot of time 19:06 imagining what it will be like when the 19:08 app is released. While using this app, 19:10 I think, "This is so convenient.""Who 19:12 on earth made this?" Thinking things 19:14 like that, imagining all sorts of 19:15 things. 19:16 >> I’ve already thought of some add-ons 19:19 to attach to this. 19:21 >> Buses and subways don't only exist in 19:23 Korea; they're in Japan, the US, and we 19:25 could go global. 19:27 >> Thinking about things like this keeps 19:28 me up all night, even if I haven't 19:30 built them yet. 19:31 >> Not at all. 19:32 >> So, I’ve actually enjoyed this whole 19:35 process; I don’t think I’ve ever 19:38 felt it was difficult. You mentioned 19:41 the mindset of not giving up, and I 19:43 realized that if you do work that’s 19:45 fun, you can last longer than others. 19:49 On my phone’s lock screen, yes. 19:51 >> There’s a Chinese idiom written there 19:54 : "Bulgwang-bulgeup." 19:55 >> Yes. What does it mean? It uses the 19:58 character for "no." The second is " 20:01 madness," and the last is "reach." 20:04 Meaning, if you aren't "mad" about 20:05 something, you can't reach your goal. 20:07 You have to be crazy about your work to 20:09 succeed. It's a really cool phrase. 20:11 It’s cool, but it doesn’t tell you* 20:15 how*to go crazy. 20:16 >> It seems like it just left that as 20:18 homework for us. 20:18 >> Yes. 20:19 >> So, how do I go crazy for something? I 20:22 pondered this and recently realized, " 20:24 Ah, it would be easy if I did work I 20:26 enjoyed." If you find work that is fun 20:31 and makes your heart race, it seems you 20:34 can endure the process longer, even if 20:37 it's arduous. I get excited just 20:40 imagining when this will be released. 20:43 So I have to complete it. "This will be 20:45 solved soon." I think I’ve come this 20:48 far with that mindset. Shouldn't we 20:50 find work like that? There are many 20:52 people who succeeded after spending 20:54 many long years finding such work, 20:55 right? Looking at them, it seems they 20:58 were doing what they loved. I believe 21:00 the key is finding that kind of work. 21:02 >> So, Jaeyong, you’ve produced great 21:04 results, and we have high expectations 21:05 for you moving forward. In that vein, 21:08 is there anything you’d like to see 21:10 from To-Do-Jae Coding Class, or any 21:12 specific lectures you need? I see a lot 21:14 of courses for "live coders" out there 21:17 these days. Lectures are good, of 21:20 course, but I believe experts like you, 21:24 To-Do-Jae, have professional networks 21:27 from your fields or workplaces. Right? 21:31 But live coders are mostly non-majors, 21:34 so it feels like they’re all 21:36 struggling alone in their own separate 21:39 battles. So, since it’s just 21:43 beginning, if you could create a 21:45 community to bring those people 21:47 together, where you could act as a 21:50 leader, listen to their hardships, and 21:53 offer help— 21:56 >> You could use that to create new 21:58 lectures, and so 22:00 >> If you could run a community where we 22:03 could all gather, yes. 22:06 >> I think it could become a community for 22:08 great vibe coders in Korea. 22:11 >> I’d like to make that suggestion. 22:13 >> Yes. Thank you for your kind words. I 22:15 will take what you’ve said, plan it 22:18 out, and work to materialize and 22:20 execute it quickly. Yes. Thank you so 22:23 much for participating for so long. And 22:26 thank you for sharing such good news; 22:28 could we perhaps meet again once 22:30 you’ve completed your next great 22:32 project? I’m currently preparing a 22:36 web project. I’ve done it. 22:38 >> It’s a bit tricky to drop a spoiler, 22:40 but there’s something here that I 22:42 could even patent. 22:43 >> It might be a little hard to describe, 22:45 but it’s a space for writing. 22:48 >> It will likely be a platform where 22:51 people can write, serialize their work, 22:53 and ultimately create finished pieces. 22:57 >> Yes. 22:57 >> Right now, within a month, it has 22:59 planned it all out so incredibly well. 23:02 >> Yes. Claude did such a great job. I 23:04 just told Claude, "I want to do 23:05 something like this." If I just give it 23:08 a rough idea, it handles the planning 23:10 and maps out the entire design, and 23:11 I’m just watching in awe. It’s just 23:14 so good. 23:15 >> Technology has improved that much; 23:17 it’s been about 10 days, and the 23:19 framework is almost complete. It still 23:22 needs some refinement, but it should be 23:24 ready for deployment in a month or two, 23:26 so if you invite me back, I’ll come 23:28 out and show it off. 23:30 >> I’d be very grateful if you did that, 23:31 and I’m looking forward to it as well 23:33 . Lastly, I’d like to share something 23:36 —back when I graduated from what we 23:39 called "elementary school" at the time. 23:42 >> There was a section in our graduation 23:43 album for writing down our dreams. So, 23:46 I wrote down two dreams. 23:49 >> A great detective, and one was to 23:51 become Korea's next Edison. 23:54 >> I had written those two things down. 23:57 >> Back in elementary school, I enjoyed 24:00 reading the Sherlock Holmes and Lupin 24:02 mystery series; the process of a 24:04 detective showing up at a crime scene 24:07 with a pipe, finding a single clue, and 24:09 tracking the culprit to the end was 24:12 just so fascinating. 24:15 >> I thought, "I want to become a cool 24:16 detective like that." Yes. That was the 24:18 dream I had. About 20 years later, in 24:22 1999, I passed the police officer 24:25 recruitment exam. 24:27 >> I became a police officer and... 24:30 >> I entered the Major Crimes Unit. Yes. 24:33 It’s not an easy place to get into, 24:36 but after one year, I joined the 24:37 violent crimes squad. 24:39 >> And there were robbery and assault 24:41 cases in the district. 24:43 >> They happened three times in a row. 24:46 >> There were no leads, and it was a case 24:48 that seemed destined to become a cold 24:50 case. 24:50 >> Yes. 24:51 >> But by repeatedly meeting with the 24:54 victims, I found clues and was able to 24:57 apprehend the culprit. So that day, the 25:00 dream of being a great detective I had 25:03 cherished 20 years prior... 25:05 >> I achieved it. 25:08 >> Yes. Yes. And my second dream isn't 25:12 about creating lightbulbs or 25:15 phonographs like Edison to exert a 25:19 great, positive influence on the entire 25:23 world, but today is the day I'm 25:27 officially unveiling two apps I created 25:31 based on my own ideas. Thanks to you, 25:36 Two J. 25:36 >> The honor is mine. Yes. Today is the 25:39 day I achieved my second dream. I 25:42 wanted to express my gratitude because 25:45 ever since I started coding five years 25:49 ago, as a non-major, I haven't had 25:51 anyone around me to talk to about 25:54 coding, computers, or AI. But having 25:59 this time to talk freely in this 26:01 channel, filled with people who are 26:04 truly interested in these topics, after 26:06 years of silence, felt like letting out 26:09 a pent-up dam, and I want to say how 26:12 happy and wonderful this time has been. 26:15 Thank you. I also had a very meaningful 26:18 and truly happy time thanks to all the 26:20 great things you shared. Thank you. 26:23 >> Thank you. Lastly, do you have any 26:26 questions for the tutor? I heard you 26:29 started coding in your 50s, so I'm 26:32 curious about how your family reacted 26:34 back then. And now that you've released 26:37 two apps, I'm curious about how your 26:39 family views it now. 26:42 >> Well, regarding my family, I think my 26:44 wife probably felt the most frustrated. 26:48 She probably thought, "Why not just 26:50 stick to your stable job?"" 26:52 >> Why do you keep signing up for courses? 26:54 "" 26:56 >> When we suggest a trip, you always say 26:58 you're busy." 26:59 >> Despite all that, she silently 27:01 supported me for over five years 27:03 whenever I said I wanted to do 27:05 something, and even today, when I told 27:07 her I had my first interview, she 27:09 handed me a sedative. She told me to 27:11 take it before I go. Ah. 27:15 >> So, I want to express my gratitude to 27:17 my wife for her silent support and also 27:19 for giving me this opportunity. 27:22 >> Unlike in the beginning, 27:24 >> now the reaction is just about at the 27:28 level of "Oh, so he's actually doing 27:32 something." 27:33 >> I don't think much has changed. It's 27:36 just like, "Oh, Dad is doing an 27:38 interview?"—that's about as far as it 27:41 goes. 27:43 >> I'm sure many more good things will 27:44 happen to you in the future. Thank you 27:46 so much for your time today, and I wish 27:48 you continued success and nothing but 27:50 good things ahead. Thank you. Yes, 27:52 thank you. 27:53 >> Thank you. 27:54 >> Great work today. Thank you. How was 27:56 Jaeyong’s story? This part of his 27:59 talk stayed with me today. "What 28:01 matters isn't your age, but your 28:03 ability to identify problems." You said 28:04 the people running at Seoul Nat'l Univ. 28:06 of Education Station 30 years ago were 28:08 doing the same thing 6 years ago. 28:09 Everyone saw it, but only one person 28:12 turned it into an app. You all probably 28:15 have something that annoys you every 28:16 day on your way to work, too. That 28:18 could be the next app. And we will 28:21 actually prepare the Five-Coder 28:23 community that Jaeyong suggested. We 28:26 will make sure to share the news on the 28:28 Two-Day-Jay channel first. If you're 28:32 curious about the process of building 28:33 an idea, launching it, and generating 28:35 revenue, it's all in the two revenue 28:37 pipes created with five coding sessions 28:39 . The 17-step revenue pipe course 28:43 through coding, which consists of 144 28:45 lessons that Jaeyong took, is the 28:47 predecessor to the five coding sessions 28:50 I'm mentioning now. But the fact that 28:53 he watched that course three times must 28:55 mean it's quite interesting. If you 28:58 take this current course on two revenue 29:00 pipes with five coding sessions. We 29:02 will also provide you with access to 29:04 that 17-step course that Jaeyong 29:06 watched three times. In short, you can 29:09 take them all. Anyone can do it, even 29:11 without any prior experience. The link 29:13 is in the description box below the 29:15 video and in the pinned comment. Park 29:18 Jaeyong's next project, a writing 29:20 platform, might already be out. We will 29:22 make sure to invite him again when 29:24 another good opportunity arises. The 29:26 next people to turn imagination into 29:28 reality are all of you. Thank you for 29:31 watching the video until the end. This 29:33 was Two-Day-Jay.