Transcription
Vibe-coding is a new trend that blows the minds of programmers and not only. Writing code relying only on intuition and AI – is it a revolution or complete nonsense? For whom and for what is Vibe-coding suitable? What to choose: Cursor or GitHub Copilot? What mistakes do beginners make? Let's discuss in today's episode. Don't switch channels. I am Anna Naumova, a career expert, certified profiler, and entrepreneur. I launched cool projects at Apple and VKontakte. Thanks to twenty years of experience in IT and living in the USA, I founded a consulting company and launched a popular YouTube channel with a million views, and also helped thousands of experts build successful careers and businesses in the States. And if you also dream of a career change, then visit my website annanumova.com and sign up. So, today I have Fyodor Menshakov as my guest, co-founder and CTO at Dovira AI. This is an AI tool for resume adaptation. Hello, Fyodor. Thank you so much for joining me today.
Hello. Thank you for inviting me. I follow your channel. I really like it. Thank you. Well, now you are part of my channel. And I hope that today you will tell and show a lot of useful things to my listeners, subscribers, and viewers of the channel. Tell me about yourself. What do you do, where do you live, what do you do?
Yes. I am a developer with over ten years of experience. That is, throughout my career, I have worked in various organizations, both large corporations with billion-dollar market caps and startups at different stages. For example, one of the last startups where I worked as a staff solution architect recently had an exit, just last year. And, accordingly, my solutions, my code now works in over 200 banks and financial institutions worldwide. Also, I launch my own products. Now we have such a flagship, Dovira AI, which deals with resume adaptation.
Oh, very relevant. Another tool, right? But we did it well. We will definitely talk about it. I'm very interested. I always study different tools. I think viewers of my channel will also find it useful, I hope. So, please write in the comments if you have tried it. Or maybe some promo, a discount for the podcast viewers. It's a free tool.
There is a free mode, and there is a paid one. One of our competitive advantages is that it's cheaper. It's a super minimalistic tool, with a bit of a vibe-coding vibe. And it occupies a certain niche. We already have thousands of clients. It's very pleasant when people write to you. It's one of the big motivators. "Thank you, we found a job."
Great. Great. That's really nice.
Great. Well, let's talk about that a little later, because our topic today is vibe-coding, right? And it unexpectedly turned out that Fyodor also has a tool that can be useful to the channel's viewers. Tell me, you live in the USA, right?
Yes, yes, yes. I came to the USA a year and a half ago. Well, a little less. I arrived in March under the O-1 visa program and now live in North Carolina.
North Carolina. We know North Carolina from Masha Podolyak. I think that's also a familiar name to my channel's viewers, because Masha and I have had many different live streams. We had a live stream very recently. Okay, tell me, what is vibe-coding and where did this name come from?
Yes, this is exactly the situation when a meme got out of control. So, in principle, it was a humorous name when the first tools appeared that could generate code in agent mode. Immediately, people, for those who haven't encountered it, it's a serious mind-blower. How it works, it writes something itself, something runs. We will look at it. And many people who have no experience in programming, in development, saw an opportunity, rushed into it. And so the term vibe-coding appeared. Now it may carry a somewhat negative connotation. Well, because coding in the classical, classical sense, that is, in the initial, let's say, is when a person tries to develop something using AI tools without any knowledge in programming, in development processes. So, this process has both pros and cons. And, accordingly, this something is presented as low-quality. But this is not necessarily the case. So, in principle, it's just tools in skilled hands. You can create any code of any quality, of any level, both for corporations and for startups.
So, the fact that it's low-quality is not true? So, you can create quality code too, right?
You can create quality code, and you can create low-quality code. It just depends on who is doing it at this stage.
Well, it seems to me that regular code can also be made high-quality or low-quality, and it also depends on who is doing it. For example, if I do it, it will be low-quality. If Fyodor does it, it will be high-quality.
Well, possibly, possibly. Yes, it also depends on people, but in any case, it will be faster. Faster almost always. Although, for example, just the other day, a new study was published, a randomized, very high-quality study, where they took developers and gave them tasks to do with AI and without AI, and then measured productivity. And here's what happened. It became popular just a couple of days ago. It's being discussed a lot now in AI circles and software circles. And according to the results, the development speed slowed down by 20%. But if you look into the study itself, not the headlines published in Telegram channels, we see that for those people who have experience working with these tools, productivity increased relative to their own performance without these tools. So, it turns out that four out of sixteen people who participated in the studies increased their productivity. The rest either remained the same or decreased. However, the quality was similar, and accordingly, the number of bugs, defects, and code quality was the same.
Yes.
So, this is a very interesting study, but another important point is that it was conducted six months ago. So, and now six months is a very long time. And six months is January, right? Well, January, the beginning of the year. Since then, tools and infrastructure for development have advanced significantly. Firstly, new models have appeared that generate code more qualitatively. Secondly, the tools themselves, like Copilot, Wonsurf, Cursor, and others, have become better. MCP servers have also appeared, which are debatable, but I use them, they don't give me a productivity boost.
Let's go back a bit, because you started talking about some complex things. So, for a mom or dad, how would you explain what vibe-coding is? Or anyone's mom or dad.
Okay. If we don't get into marketing, and don't start selling it, then in general, it's a programmer on your computer to whom you give tasks, and they do them. But it's a very specific programmer, and they may not always do it well. Sometimes they might try to trick you, but most of the time your tasks will be completed. At the same time, you might not know the specifics of their work and just give tasks. So, this is vibe-coding in its purest form.
So, a programmer who is not your friend, right?
Or maybe a very good friend, and they prank you periodically. So,
Listen, that's an awesome name. I'll write it down and remember it. A programmer in your computer, right? So, my own little helper, right? A little helper programmer who, well, if they want to, they'll mess up, right? And if they don't want to, they'll play, right? Or not mess up. Great, great.
For whom and for what is vibe-coding suitable, and what tasks does it solve?
Well, in general, any tasks related to writing code can be solved. The only thing is that depending on the context, in any discussions, you need to immediately establish the context where it is applied and, well, to roughly understand the environment. So, the effectiveness of vibe-coding can vary depending on where it is. That is, for example, where it is and who is doing it? For example, some project manager who has no programming knowledge, but understands business, understands processes, understands how it all works, just doesn't know how to code, right? And they are starting some startup. That's where the maximum efficiency will be. It can be hundreds of times more productive. Because the person understands how to do it, they don't know how to do it, and they will do it, in principle, and they don't need programmers, they don't need investments. They can already go with a ready-made prototype, MVP, or proof of concept and ask for money or look for programmers who will develop it further. So, it's super. It's a game-changer in this niche. And how investments will go in the future is a question. A question.
Also, some experienced project manager can copy someone else's product, right? It will be even easier when and it will cost almost nothing, in principle. And copying becomes almost free. Well, not free, but not thousands, not tens of thousands of dollars, as before, or even hundreds of thousands of dollars.
Yes. Great option. What else? And on the other end. If we imagine a gradation, this is the most favorable case of use. And the most unfavorable is corporations with complex legacy code and narrow specialization. So, here the profit will be the smallest. And it's even very noticeable when you communicate with people online or in person who work in such areas. They are often very skeptical because it hardly helps them in their work. Or it helps, but it's not as simple as you and I launching Wonsurf after some time and doing something in it. So, here preparation is needed, processes need to be set up, additional tools are needed. In general, it's very difficult. And getting a boost is not easy.
And if we talk about programmers, how much can programmers be a good target audience for vibe-coding? Such good, talented ones, like you, for example, experienced ones.
Well, for programmers, it again depends on where. If, for example, a new product or a new feature is being launched, or a new part of an existing product, and a programmer, well, this is an ideal case. If a programmer who is not narrowly specialized, a generalist, let's say, they have a specialization, I don't know, for example, backend, like me, but at the same time, I have experience in DevOps, and front-end, and DBA. Well, in general, everything that surrounds it. And I just understand, I can do it myself, but with AI, it will be faster for me. So, that's also a very good case when using tools.
Yes.
Again, narrowly specialized ones will need special solutions tailored to their area.
And can vibe-coding be used outside the IT industry? For example, for manicure specialists, or builders, can they use it for themselves? The question is about coding, like creating their own application. But theoretically, they can create a website, right?
Well, there are website builders that do that just with a mouse, right? So, in principle, you don't need coding. But some advanced ones who can figure it out themselves, in principle, yes, yes, yes. But, but again, I'm not sure that a completely detached person can do something with the current level of technology that will reach production.
What about teachers, for example? Students, right? For example, to create some kind of educational program for students, pupils, for children. Could something like that be possible? For example, a teacher who has never coded, and suddenly decided to package their knowledge differently. Could that be a case?
Well, maybe, yes. Why not? So, if a person, well, figures it out, reads how it works, takes some tool that doesn't require deep knowledge in the subject area, in programming, can they do it? No.
Well, the question is, it will depend on the person. So, I just decided I wanted to make an app for myself. Probably not going to work, right? You'll have to read something, watch something.
Yes, interesting. If anyone watching us now has ideas on how and who else can use vibe-coding, please write in the comments. We want to create, you know, an encyclopedia for dummies, for non-IT professionals.
Super.
I can add about IT professionals.
Yes.
I literally had such an experience that business people, completely technical people, I showed them, set up the environment, showed them how it works, showed them the tools, and literally in an evening or two, they wrote something to me, they were already doing it themselves. So, in principle, if you give some impetus, if a person is smart and open to new knowledge, then yes.
Yes, yes. They figured it out themselves. Yes, yes, yes. And I can even advise those who want to do this and don't know where to start: start with some basic computer science, which will be very useful for understanding, well, the big picture, right? You need to understand what's happening. There's a super classic course on YouTube from Harvard, CS50, it has about 10 lectures. If you watch it, you'll be able to talk to this computer, to the programmer on your computer, in the same language.
Super. For some, you know, starting with basic computer science sounded very brutal. I immediately imagined some Master's Degree in Computer Science, where you have to dedicate 2 years to learning and spend a lot of money at Harvard. But you're talking about a course, right? You mean a course of a few months, right? Not an education.
The course is literally on YouTube, on all platforms. It's free, there are just a few lectures. But on the other hand, maybe it's a bit brutal. You'll have to watch about 10 hours of lectures. Yes, but on the other hand,
Well, 10 is not 2 years.
Well, yes. So, on YouTube, there's a 10-hour Harvard course on Computer Science.
Well, approximately. I don't remember exactly.
Yes. Listen, I'll look for the link, or maybe you'll send it, and I'll add it to the description of this video. For those who don't know how to search. Super. Okay. You've already touched on this topic a little, talking about legacy code, but maybe let's summarize again, and maybe you can give some other examples of who and for what tasks vibe-coding is definitely not suitable for. First of all, the biggest obstacle to using vibe-coding can be security compliance. That is, not all companies, corporations, especially banks, can allow this. So, if you're not allowed to do it, there can be big problems, in fact. Because, although many allow it, here's the big problem: there are LLMs that you can deploy locally, on bank servers, for example, but they are all worse, much worse, than the top models from market leaders. So, you can't use them as well as models from Anthropic or OpenAI. Therefore, if the company doesn't allow it, then you don't use vibe-coding. You can ask ChatGPT something, for example. That's not quite vibe-coding. Although, yes, it's been about a year, it's no longer considered cutting-edge technology. If you program with ChatGPT, you're a bit behind, right? So, you're not vibing.
Okay. So, companies with strict security compliance, right? We're crossing them out.
Who else is it not suitable for? Narrowly specialized specialists for whom there are no specialized tools yet. That is, in fact, if a company develops something very internal, and LLMs haven't had enough examples of it, they might have some internal frameworks, internal, well, anything, they just won't get such a benefit. That is, they will need to deploy their own infrastructure so that the LLM has their libraries in context. Well, it's quite complicated. So, it might not work just like that.
Well, I think that's for now, yes. I think that's always the case, yes, some tools, they start broadly, and then they start appearing, like now GPT for finding employees, right? Or something else, a tool for manicurists, right? And then it goes vertically. So, I think for now, there's probably no vibe-coding for, I don't know, DevOps, right? But I think it might appear very soon.
Well, Combinator has several companies that specifically do vibe-coding for DevOps.
Oh, wow. I just said that, right? I didn't peek.
That was a trend last year. You can make money on it.
Well, some kind of vibe-coding for designers, I don't know, mobile interfaces, right? For specific ones.
Well, for designers too. Vibe-coding, like image generation, has now reached a new level. That is, you can generate pictures very well now. But generating interfaces is a more difficult task. And now, a solution that we could say: "Okay, we can now generate interfaces." There isn't one yet, but if it appears again, it's a potential unicorn.
So, this is an area where, well, it's very hot.
Yes. Write it down, guys, write it down. And what about financiers? Can you create some databases with vibe-coding? I don't know, some financial reports, or is it all super insecure and won't work at all?
Well, it depends on what we mean by vibe-coding. That is, if it's specifically code generation, then in principle, the domain area doesn't matter. You can create programs for teachers and code for financiers. It will be the same code, in fact. For example, if we're talking about tools, it's no longer quite vibe-coding. It's just new interfaces, a new user experience that is now being implemented in AI. That is, for example, when we can write some request and get a report, right? Instead of making charts in Excel, but literally right away: "Give me the quarterly report with these parameters, according to these criteria for the top 10 of our subcontractors, for example," and you have a report, you click send and send it. So, in principle,
Is this vibe-coding or is it,
Well, it's not vibe-coding, it's more of a new user experience that LLMs are currently providing, right?
Yes.
Well, such things are almost everywhere now. It's being implemented at full speed.
Yes. So, such agents, right? Well, not exactly agents, it's more like augmented databases for.
And some presentations, accordingly, so that we can generate a presentation based on a user request.
Yes. Still, yes, it seems that you can do everything with vibe-coding, right? Maybe there's something else. So, compliance, narrowly specialized professions and things that don't exist yet, but will likely appear soon. What else, who else is it not suitable for?
Well, that's a good question. So, it also depends on the company culture and the people. So, people, because it requires reconfiguring processes anyway. Even if processes aren't reconfigured, at least developers will have to reconfigure their processes. And if people are not ready, and if the company is not organizationally ready for it, it can also be a stumbling block. And again, it's investments, so again, reconfiguring companies, reconfiguring processes, finding new people or training old ones. So, these are costs, these are investments, and they are still risky, because this story is new, and it's not very clear what the outcome will be. Will it be a 20% increase in productivity, or will it be 200%? That's a big difference, but we'll see, it's developing very rapidly. And, accordingly, with every new model, every six months, we move to the next level.
Yes. So, you said that developers need to reconfigure. Do developers themselves want such innovations, or are they more conservative?
Well, it depends on the person. There are evangelists who immediately saw the prospect, "Let's go, let's go," and there are those who accept such things very reluctantly. You can see it in any chats, on any forums. This discussion always happens. There are always those for, and always those against. And in general, the arguments are quite relevant from both sides, because, well, in this case, at this stage of development, AI tools for code generation cannot replace a developer in principle. You can make it so that some product manager or some completely non-technical specialist can create a proof of concept. But then they will need tech people in some form, for development. So, it's impossible for now. But on the other hand, judging by the dynamics, I wouldn't be sure about job security for developers now, because if, for example, we take ChatGPT 3, which appeared about 3 years ago, what is 3 years, right? Not much. It could do one out of ten tasks, which, well, based on my personal experience, now the latest tools can do eight out of ten tasks. Approximately. So, two out of ten tasks that won't fail, that's a lot. That means you have to check all tasks, and that takes time and resources. Yes, but the progress is obvious.
Yes. So, how do you feel about vibe-coding? I see great prospects, including for techies. I believe the industry will change under the influence of AI tools, but I'm not sure how yet. So, it can go in different directions. If, for example, we don't know the ceiling of modern LLMs, maybe this is already the ceiling, and further improvements will be incremental, not exponential, then it will be one path. And in principle, well, I like this path the most. Developers get jobs, there are more jobs, the work becomes more interesting, we offload unnecessary, uninteresting tasks to AI. We think more ourselves, we do more creative work. That's one path. Or, if it becomes several times "smarter" than it is now, in quotes, then it might be possible to replace them completely. Then some teacher will say: "Please make me a CRM or some Coursera, which will be only for our institute, for our university, and with some requirements."
Yes. And they will get a link in an hour. "Here, use it." Are you on the conservative side or the ambassadorial side in these debates?
Well, in any case, I'm an ambassador, because I use it. At this stage, I see great technical challenges in organization, in application architecture. For example, the efficiency of professional development depends on the architecture. Strangely enough, some architectural principles that we used in classical development now facilitate vibe-coding, while others hinder it. So, if your projects are initially done correctly, or rather, incorrectly, according to architectural principles that are more conducive to vibe-coding, then it will go easily and smoothly. If you have some old legacy, then you have to try hard.
Okay. And tell me, what if I decide to vibe-code, right? I have absolutely no knowledge. You've already said that you need to go through, well, at least, yes, it's desirable to watch the ten-hour course from Harvard. In general, what knowledge is needed to start writing this code via Vibe?
Well, to start, nothing is needed. Especially if it's some tools that are beginner-friendly, right? So, you can just start writing, without watching anything, and something might even turn out. So, you probably won't be able to create a large, complex system, because it has its limitations in terms of context, and the architecture will be bad, in general, there will be some issues with.
with security, but overall it's all solvable. And if your idea takes off, then you'll just hire people to fix it. >> Uh-huh. So, like, no technical knowledge is needed to start vibe-coding, right, to go to the websites of these tools, right, download these tools and start using them intuitively, or do you need to prepare something in advance, read manuals, take some courses, or something like that? Well, there are different tools, and there are tools where you don't even need to download anything, you just do it right on the website. >> Uh-huh. Ah, well, tell me, yes, about the tools and how to choose them, right, maybe from the most beginner-friendly to some more advanced ones. Can you name, like, three, maybe five tools, right? >> Well, again, this is a very hot area, and tools are constantly appearing. So we can just divide them into several groups. Uh, for example, for amateurs, for non-techies, and for techies. So we can make two groups, right? And for non-techies, it's like Lavable, Bolt, and so on. They appear very often. In principle, I don't follow them very closely because I don't use them, but I know that people use them and even showed me, and it even works. The results, in principle, you don't need to set up an environment, you don't need to set up computer science, you don't need anything at all. You write what you want. And if you're lucky, and you're lucky more often than not, it does it. Sometimes it even does it correctly. Then you click the deploy button, and it's deployed. You can send a link, look, I have my own website, for example. >> Uh-huh. >> Uh-huh. Super. Yes, it's >> Lavable Bolt. What else can you recall here from such amateur tools? Well, these are the ones that appeared first, and they are more mature, but in general >> I can't recall, but 100% there are more hyped ones now. >> Uh-huh. Uh-huh. Okay. Yes. Uh, then for techies, >> well, for techies, there are several tools that are the most common. These are Aut, Asforsor, and then from these, for example, the most common ones. >> Ah, well, the leaders here are WCPf and Copйil. They are roughly the same. I actively used both. And now I've settled on Winserf. Well, only because it's cheaper. For me, because I'm an early adopter, and I have a very good subscription that is now cheaper than Cursor's, actually. >> Uh-huh. Roughly what amounts are we talking about? For those who >> not roughly, I can say exactly for me. WiF is $10 a month, and there are quite good limits. >> I very rarely exceed them. If I exceed them, I buy another $10 and it's enough. Well, you have a special one. But if you walk in from the street now, how much would it be approximately? >> I think $20 and then >> a little less. Yes. Cursor also had the same until recently, but now they've changed their pricing policy, and the limits have become much smaller, and accordingly, it has become significantly more expensive. And this has put off a lot of people. If you read Reddit, there were a lot of dissatisfied people about this. Well. And Copйil, again, this is a very good story, like how not to do it. They appeared first, they had all the resources, they had GitHub, they had code, well, huge code repositories, and they messed it all up. So, in fact, until the end of last year, they were the worst in this trio. In terms of code generation quality, usability, and number of features. Now they are catching up, well, because Microsoft has huge resources, but they are catching up, and they could have made it so that no one else appeared, they could have become the standard. Well, in fact, >> I don't know, now, ah, it's July, right, maybe someone from the future will watch, and Copay has caught up, and it has become good, but not now. Uh-huh. >> So I know people use it, but it's worse, it's literally worse than Winserf and Cursor in terms of generation. >> Why is that? Because a large organization is slow, and startups are usually the fastest, agile, right, they overtake, or is there another reason? >> I I have no explanation for how this could have happened. Well, probably. They were the last to add agents. Well, in fact, they used Copilot like a GPT chat where you don't have to copy. And it was supposed to understand your project, to have access to all your classes, files, but it didn't work. >> Uh-huh. Well, this is a common story, when large organizations, they don't even see beyond their own zone, and they are so big, heavy, clumsy, and they react poorly to new things and changes. And often startups emerge that are more flexible, mobile, agile, fast, nimble, right, and launch some cool solutions. Well, for example, a great example is Slack, right, Slack, which launched as a very niche messenger startup, right. What is Slack now? It's a unicorn. Everyone uses Slack, which killed, well, Skype. Or, for example, Amplitude analytics, it was also a small analytics startup for small companies. And they made services much cooler than, say, Google Analytics, right. And many have now switched to Amplitude. This is a very common thing now, or Miro, for example, right. Who would have thought, right, that someone would need virtual boards, right, but a small startup from Penza, as far as I know, right, or from some small town in Russia, they created such a giant unicorn. So it's a common story, right, so well done Winserf, well done Lavable, well done Cursor, yes. >> Yes. Respect. Yes. >> And maybe thanks to Copay for giving us such variety. >> Uh-huh. Yes. Well, we'll keep watching. Uh, well, can you show how it works? Something simple, quick. If we can do something right now, >> yes, >> cobble it together in 5 minutes. >> Well, let's, let's try. Well, it usually takes a couple of hours. By the way, about Tools. >> Uh-huh. >> A couple of hours. I'll say right away. Now people will drop off, say, we won't watch. Yes. Regarding some interesting ones now, uh, after Cursor changed its pricing policy, Cloud CD has become very popular, but it's a slightly different tool. It's for super professionals. I haven't tested it enough for generation quality yet, but it's practically without an interface, or with a minimal interface, not as convenient as Cursor or something like that. You give text instructions, click a button, a black box does something, and then you have ready code, done. It's a different experience, but many say it generates well, and it's more expensive, so you have to pay $100 or $200 a month. So, that's about it. >> Uh-huh. Understood. Okay. >> Well, I read about it, but I haven't tried this method yet. In principle, it might be the future. Ah, well, everything changes quickly in this industry. >> Super. >> So let's see. >> Yes, try, yes, share the screen. >> Yes, this is Winserf. >> This is Winserf, yes. Ah, well, mine >> looks scary for beginners. >> This is a professional program, accordingly. Maybe it will look scary, but in general, it's just code that you can close and not look at at all if you don't want to. So, in fact, it's files that you can close and not look at them. >> But for a developer, it's generally familiar to work with. And both Winserf and Cursor are IDEs based on VS Code, which is very popular. I used it even before the appearance of ITS. So, in principle, it's very familiar. So here I've pre-generated a Next.js project. Uh, well, for those who want, it's basically one command in, here it is visible on the screen. It's one command. You copy it from the internet, type it, and, well, it works. So. Why is computer science needed? Because at least you know that there's a terminal, there's code. Something like that, so you don't get lost. Although everything here is very simple. So. And I connected CCD in two clicks, and accordingly, all our changes that are there will immediately appear directly on the site. So we'll leave the link, and whatever happens, happens. We can do something >> like this. But to be honest, for the sake of experiment, I didn't think about the topic in advance. Let's come up with something together and try to generate something together. >> Uh-huh. Good topic. Ah, well, look, since we have a channel for job seekers, let's come up with something that job seekers can generate for themselves. I don't know, maybe some responses, resumes, what can be simpler. Some letter to a recruiter, maybe a website, a presentation, a business card of your experience, maybe something else. Well, let's, let's, let's. A website, a business card website, a presentation. And, for example, I immediately have an idea, a business card website that should be generated from your resume. You upload your resume, and you get a business card website. Yes, that's cool, but we won't do that in 10 minutes because of connecting PD, well. >> But we can make a business card website. So, if I want it without a resume, and then >> let's >> we can add this functionality in the second version. >> So, uh, basically, Winserve. And what do we need to do? We have a cascade, which is, basically, an agent model. We can choose some models. Unfortunately, after Winserf was bought by OpenAI, they don't use the latest Anthropic models. But Sonet 3.7 is generally okay. Although the fourth is much better. So, we can just write something banal. So, what's my configuration? Here, uh, there are several MCP servers that I use. This is, uh, context, uh, one of the problems when you do it yourself and don't use any MCP servers, LLMs sometimes don't have the latest documentation updates, some latest libraries. And those who work with it encounter this. This MCP server solves this problem. And, sequential thinking, it becomes a bit smarter with the MCP server. It breaks down the task into subtasks and solves it by itself. Well, and that's it. Basic basic settings. Nothing additional here. So, we can start, right? So, what do we want? We want it like this. Like this, like this, and we'll write it in Russian. Create a business card website for a developer. >> For a developer >> which one? >> Which, I don't know, will help with job search. And just the context, if you give a little non-technical context, it sometimes makes a nice appearance and writes some selling points. >> Uh-huh. Write in English, otherwise it will be in Russian. >> English, yes? >> Yes. >> All content should be in English. Make the website interesting and selling. Do you feel the vibe-coding selling vibe? I'm already waiting to see what comes out. >> I'm curious myself. Well, let's do it exactly like this. >> Uh-huh. So, we'll add some more prompts to it later. Yes, >> yes, yes, yes. First, I'll look at what's already in the project to understand what we're working with. >> Well done. >> Let's look at the project structure. So, you see, you don't even need to understand. And this is a certain magic. So, a developer who is doing something, and then he also does the code, right? It's code, right, if I understand correctly? >> It's Winserf? >> No, I mean, the AI model is yours, Code. Yes, >> it's Code, yes, but the wrapper is Winserf's plus MCP servers. So, >> Uh-huh. >> requests to LM go to Code, but Winserf itself also does something. But again, >> Uh-huh. >> 3 billion companies. Well. >> Understood, understood. Uh-huh. >> And I downloaded it for free. Well. >> Yes. So. Well, what's here? So, it says: "Execute commands." It's creating folders in our project. >> Uh-huh. >> Because I wrote to it: "Create beautiful code with good decomposition, good architecture." Again, I didn't describe it, I just said: "Create good architecture." As you understand it. >> What's its idea of good? Oh, it's written something, look. >> Well, yes, yes. Something has appeared. But again, you don't have to look at it, but in general, developers who develop professionally, they look at it. And this is like a pull request. A pull request is when you've written some functionality, and before committing it to the codebase, you create such a representation and look at it yourself, or other developers look at it before it gets in. >> Uh-huh. Uh-huh. A review, right? >> Yes. Yes. A review, in fact. And, uh, it's very convenient to do here. And after each, after each request, accordingly, you do this. So, it's creating >> Uh-huh. Yes. Hero, in general, it looks interesting, this whole process and the whole experience. >> Uh-huh. So it's also a designer, right? So it's not just a developer, it's like a developer plus designer. Yes. It's a developer plus designer, but I don't have >> a copywriter >> and a copywriter, it's better than me, 100%. >> Well. But here's a life hack. If you have a design or a template that you like, you can take a screenshot and literally paste it into this window. >> Ctrl C and write: "Do it like this." And it will do it. >> Uh-huh. Or "use my corporate colors or my logo." Yes. No problem. >> Can I use my photo, right? >> Well, you'll need to insert the photo into the application, accordingly, and yes, and say, "insert the photo here as a logo." >> Well, we'll try something now. Let's let it finish generating, we'll run it, and then we can do something to make it more interesting. But again, I asked it to make it interesting right away, so we'll see how it did. Uh-huh. It's taking a long time to write, it's kind of slow. >> Well, this is really >> it's trying, right, >> like honey with spoons, right? So, in principle, this is a miracle happening now, to write this before, to generate it, it was simply an impossible task without >> And now, well, yes, yes, it's slow because it will write a lot of code, >> so you can't see it now, but in general, here, how many lines? 40 lines, right? And these green numbers, plus 100, minus 0, these are the lines of code it has generated. So, 100, 200, 300 lines of code it has already generated. >> Well, and it's not that little >> to write them would be >> longer, even if you copy. Here's another 100. >> And look at skills, look at skills, 100 lines of code projects. It wrote 119. And notice, we didn't say: "Give me skills, give me projects." So, >> well, ideally, in the task, you need to write the structure you want, but if you want a truly full-fledged, truly vibe vibe, then you need to write like this, >> right? Well, if we wanted to make a project with a resume, then we would have to upload the resume, right, put it in some folder, well, and ask it to create a website based on the resume, right? No, no, the idea is that you go to the website, there's a button to upload your resume, you upload your resume, and right on the website >> yes, and you have a website that you can embed, you can add Stripe, a subscription, so that, >> you can have a free version, some paid one. Well, the development has already started. Ah, this is already like a startup, like a website generator based on resumes, right? >> Something like that, >> yes, I understand. And I meant simpler, right, I want my business card website based on my resume, accordingly, I'm already listening. Yes, yes, yes, yes. >> Uh-huh. Because here >> here it's collecting some, well, clearly not understandable experience, right? Yes. So I think everyone needs a website with their personal experience, which can be taken from the resume. Well, and contacts, and so on. Listen, it's cool. I still had a question: "And to connect payment gateways?" Yes, you said Stripe can be connected. How easy is it to connect to such sites? >> Well, you write: "Connect Stripe," and it connects Stripe. Literally, add Stripe. But to connect Stripe, you need, besides having a Stripe account, you also need, well, keys, right, all that. So it will ask for all that, right? >> And it won't ask for it, as I assume. Most likely, it will make it environment variables, and you'll have to go to the website later, get these keys, and then copy them into environment variables. Well, again, this is the risk of vibe-coding. When you don't understand anything, you don't understand where to store them safely. >> And, for example, if they, well, this is a classic example. If someone inserts the keys into this code, it will all work, but everyone who visits the site will see these keys. >> Right. Right. That's scary, right? And to lose access to Stripe, well, it's not very good, especially if you have, >> ah, well, large turnover, somehow. Uh-huh. >> 100%. But again, most likely, it will do it correctly. This is a very banal example. There are less obvious security issues that can arise, but specifically with Stripe keys, it will most likely be fine. Well, we can try. And see where it adds them. Just, well, I understand how it can be done, and how it cannot. That's why specifically I have an advantage in vibe-coding. It's not, well, not so dangerous. >> Well, yes, yes. I'd better not do that. And >> well, you can create a website and go to investors, right, and then hire someone and let them think about such trifles. >> Or just put a link. Yes, just a link, not integrate a payment gateway into the website, right, but, for example, click here, and a Stripe payment gateway opens, which is, as it were, isolated. >> Well, yes, >> a separate window. You'll still need to do something on your end, because, well, you can set up Stripe and just send me money, right, but you probably want it to subscribe, its status to change, the interface to change, that it's already a premium subscriber or something like that. You can just do something like "buy coffee," and give me $5, $10, or well, yes, that's easier, but you'll still need your keys, >> so it knows who exactly to send to. >> Uh-huh, I understand. So, what's happening here? Errors. Sorry for the error, but look how polite it is. Let's fix the format. And who told it that there's an error? So, is it checking itself, or what's happening? Yes. Yes. >> Well, we see here, it added contact, it's red, there's some error. Well >> uh-huh. >> And who did it tell? Before, before whom did it apologize? >> Well, we're waiting for it, and it, you see, wrote incorrectly the first time. >> Uh-huh. Let's fix the errors. Yes. >> Ah, by the way, by the way, it finished. Here we can >> finished. Well, >> yes, here, just show how it works for those who do it. Well, we see exactly everything it wrote. >> Uh-huh. Skills, project experience contact footer page. How clever. It's missing a table of contents. Yes >> well, footer is there. Ah >> and head, I understand. So, just like menus, right? >> I don't know, let's see. >> Let's see. Yes, >> let's. So. I accepted everything, didn't look. Well, usually I look, because. So, let's do this. >> Run the site. >> You're typing, right? >> Uh-huh. Well, again, I know how to run it without it, but in general, it also handles it. Here's even a plus, because when it starts, if any errors appear, it will catch them immediately and start correcting them immediately. >> That, what's here >> here, here's something red, right? And here >> Uh-huh. And I like it so much, listen, it's so polite, and you tell it: "Fix it." It says: "Of course, of course, let me fix it." Yes, I just remember, you know, when you talk to a developer, something's wrong again, you don't like it. "You're annoying me with your..." And it's like: "Well, of course, I'll fix everything with pleasure." Yes. >> Well, yes. >> So, >> moreover, here, here the errors are, I don't know, uh, well, you see, it's gray now. So, it's saying itself to fix it. If I press Tab now, it will fix it. >> Uh-huh. Uh-huh. >> So, in fact, it's just apostrophes in the text. Ah, well, you can't put them in JSON. >> Uh-huh. >> So, something, something, something it's stuck and something doesn't like it. Although, maybe it's compiling for a long time. >> It says "running." >> Well, "running," yes, but it's still quite long. So, it says "Ready." Let's see if it's really ready. >> Let's. No, not ready. Well, no, this is a super classic vibe-coding. So, >> I'm copying the error. Well, in principle, I understand what kind of error it is, but let's, for the sake of experiment, not fix anything. >> Uh-huh. >> And I tell it: "Look what you've done." Let's accept it further. Wow! >> Oh! That's something. Uncy. >> And why didn't it insert the pictures? >> Well, it didn't insert pictures because we don't have them. But we can generate them and say: "Insert pictures." >> I thought it would suggest something, right? Like? Listen, cool. Cool. And this should be a photo, apparently, right? Here in a circle. >> Wow, totally cool. That's magic. That's something. Yes. And how long did it take? 10 minutes for us to create such a website. >> Me. >> Again, I didn't ask for this, right? It thought it would be nice to do. >> Uh-huh. >> Well, most likely, it's not sending it anywhere. Ah, but you can work on it. You can add some booking here. It will all be done very quickly. We can just do this with the resume, it's a good idea. Do you want me to send you my resume, I'll add it now, well, I don't know, yours or maybe someone else's. We can take a resume and based on it, have it fill out this website. >> Uh-huh. Yes, let me send it to you now. >> Listen, it looks good, right? Correct, >> it looks really good. Yes. Let's see how it will >> on mobile. Let me send you mine. >> Uh-huh. The menu doesn't work on mobile. Well, >> well, never mind. Vibe-coding. >> Uh-huh. >> Well, listen, it's not bad. I sent you my resume on Telegram. Try to do it, maybe run it, let it generate there, and we'll continue talking. Ah, and then we'll show the result. The same website for a developer, but with my >> Okay. >> with my information, right? >> Let me start the generation now. So, I've added the resume, and right now I'll write. Well, your resume. Hmm, take the data from the resume and fill out the website. Well, the work has begun. We'll see what happens later. Uh, by the way, it will be a working link. I'll even send you the link. You'll have my website like this. >> Black color, blue. Well, you can, >> like boys over pink ones. >> Well, if there's spare time, we can play with colors, basically, in the style of vibe-coding. Make this website for a girl. You can write that. And let's see what stereotypes it has built-in. >> Well, I can roughly imagine, yes, since it made a blue-black developer,
Yes, probably, hypothetically assuming that there will be a man there, then I think the garden for girls will be frankly some kind of pink, so bright. Listen, cool, right? And in general, what is happening now? Now we, uh, asked our, our friend, a computer programmer, uh, to upload, to use, to make a similar business card website based on my resume. We will look at how it looks a little later. In the meantime, I would like to move further along with our questions, and at the end of the broadcast, we will definitely show how it looks. Super, right? Well, Fedya, tell me, what are the main mistakes beginners make in web coding? Well, as we discussed earlier, the most dangerous, the most problematic thing is security, because people don't understand how it works. That's why I advised studying computer science a little, at least. If you are going to engage in web coding more or less professionally, then this will not be superfluous. And security, that is, keys, some access, some security issues. This is important. The second point is understanding. Well, if you look at some criticism of web coding on Reddit or, well, somewhere on the internet in discussions on some Discord servers, then the first thing will be security. The second will be costs, the cost of hosting. Because, uh, de facto standard for web coding is not mandatory, but very many use it, such hosting, for example, as Vercel. It has a very good business, well, not good, an interesting business model. I constantly use it for myself, but people who don't understand how it works can end up spending a lot of money. And, accordingly, such stories have happened. That is, when your application takes off, well, or rather, when you launch an application, it costs you nothing. You can use it on a free tariff for up to 1,000 clients, then it will be $30 per month. These are literal prices. And you will have an extended tariff, and you can use it for several thousand. But if your application suddenly takes off and you have hundreds of thousands of clients or, God forbid, millions, then it seems like success, and then your costs become cosmic, that is, very expensive. And in fact, you may not even be earning yet, but already $100,000 in dollars. That is, these are literal stories that have happened. Listen, right? So if you plan to scale and grow, right, it's better not to use, right, web coding. Use it, but host it. Someone should be nearby who, who, who will help you with this at this stage. Because he is very polite. He will say: "Yes, okay, thank you." But he won't tell you: "Well, dude, you'll pay $100,000 next week, let's think of something else." Listen, this is a big problem, actually, with these ChatGPTs, which seem to say: "Well, ChatGPT will replace a nutritionist, a psychologist, and so on." I personally now have a nutritionist and ChatGPT. And ChatGPT always praises me. Oh, well done, you have such a calorie deficit. Oh, well done, you ate so much protein. Yes. And my nutritionist looks: "Anya, you understand, right, that this is some kind of bullshit, right? Well, and so on, right? So it always praises. On the one hand, it's cool, but it lacks critical thinking, and you kind of believe it: "Oh, cool, right, let me have, I don't know, 200g of protein, right, but critical thinking says that no, that's too much, right? You shouldn't eat that much protein, right, 100g is enough, and so on. Here. And it's the same with web coding. Right? So it's missing, right, some kind of brakes. And here you need, well, for now, you need a person who will stop you at some point and say: "No, stop." Or, about psychologists, you often hear: "Well, I've replaced my psychologist with ChatGPT." Yes, ChatGPT also always praises. It's great when you are praised, praised, praised, right, but there are some moments when you need, well, to give some kind of magical kick, right, for you to progress, right, but ChatGPT, it doesn't really do that. It keeps praising you, how well you're doing, because it sells. It's the first thing it does, if you notice, it praises, and the last sentence is designed to keep you talking: "Do you want this, do you want me to do that, do you want me to do that?" So, well, it's actually built into the settings. And in order for you to continue the conversation, well, it gets you hooked, basically, it gets you hooked. 100% hooked from all sides. And, uh, actually, I saw statistics on the areas of use of LLMs and ChatGPT and over time, and psychological help became almost the first place. That is, people just talk to it. Well, specifically, it's strange to me, because I just understand how it works. And, well, you understand that you are talking to an algorithm. And there is no empathy here. But again, if a person doesn't know, then, in principle, they are chatting with a friend on Telegram. Especially if no one has ever praised you, and now someone has started praising you, right, imagine, right, you get hooked, like drugs. Finally, someone is praising me. Yes, no one praised me, and now someone is praising me. Yes, listen, yes. Okay. What else, well, about the risks, so keys, access to security, hosting costs? Are there any other risks to consider? If you build websites or projects this way? Well, you need to understand that over time, it will work worse, that is, with an increase in context, if you just do it like we did now, make me a website. And we didn't write anything. It did it, in principle, okay. But then we will start refining it, and problems will start to appear. But again, this is a very simple application, so there will be no problems here, and you will make yourself a website, there will be no problems. Well, if we, for example, were to create an application that, well, like generates this website from your resume, so you upload it, the client uploads their resume there and gets a link to a website that they can customize, put in their resume, and have an online portfolio like this. So, in principle, it's a cool business feature, interesting, but this project becomes more complex, and without experience, it can't be finished. Although something like this can probably still be finished, but again, you will want some additional feature later, another feature, it will become complex, large. And if you don't understand architecture, processes, well, all that, you will need additional people, then you need to understand that there is such a risk and you might not be able to finish it purely with web coding. There are some models that can delay this moment, but for now, it's like this. Uh-huh. Well, that is, yes, it's not suitable for some large-scale scaling. That is, if you are still planning to do, well, for example, if you are planning to make a presentation for investors and a prototype that you will show to investors, then it's super, right, it will work. You can whip it up yourself and show it, to attract investment and to make this project, well, in a normal way. If you think that you will do this now, whip it up yourself, and then you will scale it, there are huge risks that it will all fall apart, and you will still have to build everything from scratch. Well, then by the time you grow, you will lose your audience, lose your base. Yes. That's a big risk. Uh-huh. Well, not necessarily for investors, but you can also do it for the first clients, to gather feedback. Well, imagine, we did it, and you, and tomorrow you already have feedback. Well, literally. So, this is very cool. And clients really tried it. You're not sending presentations, but a link to a working one. So, this is cool. In general, web coding can be done further, but it will no longer be pure web coding, it will be generation, and code generation, but there must be a technically savvy person who understands how it works. And the more technically savvy they are, the fewer risks there will be. So at this stage, Uh-huh. But on the other hand, it opens up opportunities for small teams. For example, literally a team of, uh, a co-founder product owner who knows their niche, a designer, a developer, and they can compete with very large teams of dozens of people who work in a standard flow. So very small teams can create a quality product very quickly. Uh-huh. Super. Uh, listen, well, probably the final question about web coding. Tell me, what do you think, will it become mainstream or will it remain a niche tool? Again, it depends on the definition of web coding. If it's a somewhat humorous, slightly negative definition, then, probably, it will remain so. But if we are talking, yes, if we are talking about AI generation, code generation through AI, then this is already a reality, and it's not going anywhere. It's like blockchain, there are many, many coins that have been scammed, but blockchain is already with us, this technology is not going anywhere. The same with AI for code generation, well, it does it very well. We've seen that, well, in some cases it does it very well, in some cases it does it well, and in some cases poorly. And the cases where it does it very well will become more numerous with the development of technology. So the industry will change 100%, it's already with us. How it will change, we can only guess for now. Uh-huh. How then does it differ from code generation through AI with the help of AI? Well, probably, from who is doing it. That is, web coding is initially done by a non-technical person, but just a person who has the opportunity. This is the standard definition of web coding. If a technical person does it, then it's more like self-irony, right? That is, when you can do it the same way, but you are web coding, that is, you can do it without AI, but with AI, it will be faster. Right. So you think that web coding specifically, when code is generated by a person without technical knowledge, will remain niche and not become mainstream. Well, do I understand correctly? It depends on the development of technology. That is, if, uh, market leaders or some new startups appear, release tools that are significantly better than the current ones, then, in principle, it can change. Then programmers won't be needed either. That is, we can create very complex products in the same way as we created the resume website. Right. But there are no such technologies yet, and I think something like that will appear. Because, well, I don't see a theoretical limit, a ceiling, that we've reached it and there's a wall ahead. I think everything is developing very rapidly. And in general, maybe, at some stage, in 5 years, in 5 months, I don't know, in 15 years, you will be able to generate scalable, secure, good code in this manner. Plus, maybe they will stop praising and it will start asking questions, for example, to gather requirements, to advise on some issues, so that you make some decisions. You say yes, no, yes, no, okay, you fill in some data, upload some documents, right, and it generates everything perfectly, everything works, for example. Well, Uh-huh. Why not? On small websites, it already works like that, right? Well, asking questions is exactly what's missing, both from simple ChatGPT and from web coding tools, right? They just go and do it without questions. OpenAI released a new model that will ask questions. That is, it's not available to everyone yet, only in Pro. No, I don't think it's only in Pro, but not to everyone. It's currently in beta testing. I don't have it yet, but I saw in the news that they are working on it. Oh, that's great, because when I work with Claude, I mostly work, I have a paid subscription to Claude. I ask him every time, please ask me 10 questions. Before giving me any answer, ask me 10 questions, right? Only after that can we continue talking to him, because it turns out to be, you know, unsolicited advice from a grandmother on a bench often. So, an advanced user, right, that's a good topic. See, I have ChatGPT plus critical thinking and a human brain. I think for now, this combination works. Yes. But it can be done with agents, in principle. And we even had such a functionality when generating a resume, it asked questions, well, it didn't catch on, it became too complicated, not very stable, but it can be done like that too. Uh-huh. Well, tell me, tell me about your, your project. You have a tool for generating resumes, adapting resumes. Tell me how it, well, how it works, everyone probably understands. How does it differ from other resume builders, like Lyra Jobs and so on? How are you, how are you better? Uh-huh. Well, uh, first of all, it's a very dense niche, and in principle, you can find a solution for any taste, down to, I don't know, I think even if you don't like the color, you can find a solution with the color you want. Uh, we occupy a slightly different niche than, for example, they position themselves as all-in-one tools, which are like CRM for job searching, where you sit down and work in it. So, it's cool, in principle, it can work, but people are lazy. Well, I'm lazy too. And it all seemed complicated, so the idea itself was to make a slightly more, uh, modern version of Teal and simplified. So, in fact, launching and getting an adapted resume takes two clicks. Literally. So, you copy the job description. That's how I used it. For example, a recruiter wrote to me on LinkedIn, I say: "Is there a job description?" He says: "Yes, of course." They send it, I copy it, I copy it right from the conversation, into our tool, I say: "Generate resume," I edit something if I don't like it, if I like it, I just say: "Download." And in a minute, they get the ideal candidate for the job, like: "Wow, we were looking for you." So, it's not always true, because sometimes you can embellish. But the main idea was this. So, we wanted to make a tool that would be simpler, easier to use, and not a CRM in the swipe style. So, Uh-huh. In this regard, it worked out. And an additional, additional, uh, our difference is that we have the ability to customize generation. So, for example, how much, how much the AI will embellish your resume for this vacancy, you can choose, say, no, then it won't embellish, medium, it will slightly, and maximum, it will make you an ideal candidate, even if you are not one. But this is the person's choice, not a recommendation. In general, everyone has their own strategy, but sometimes this works. And what I lacked in other, in other tools. We have the ability to customize generation specifically for you. So, for example, how I used it, I wrote that, uh, use auto-generation, if the vacancy is not in Charlotte, add that I am ready for relocation. And it turned out that it wrote that if the vacancy is from New York, I am ready for relocation, for example. Uh-huh. And similarly, I wrote, since I have, well, a lot of different experience, and depending on the vacancies, it's very convenient to use, well, for example, I can speak from my own example, but in fact, well, we see logs that people use it in a similar way, that if there is, you can literally write in human language and write, if the company is a startup, please add my personal projects to the resume. If the company is a corporation, don't add it, for example, and it effectively generates a resume for you, a kind of meta-level. That is, if you have a lot of experience, it thinks about which experience to include to make it more attractive. Yes. Cool. In general, good responses, good conversion. How much does it cost? How much does it cost? That's a good question. That's a good question. The founder of the company doesn't know how much it costs. No, no. I just, I just don't know how much it costs today. You have dynamic pricing. Well, actually, the price, pricing now, well, we, uh, uh, uh, uh, are testing different, different options, right? Well, what's the range? Well, actually, it's $4 per week. $4 per week or $15 per month. It's very cheap, because, yes, we have promotions, there are some promo codes. And, by the way, this was one of the, one of the ideas. We wanted to make it cheaper, because, in principle, I understand, well, how it works. We have to pay for LLM, for servers, for marketing, it's a lot. But we have very well optimized technical costs for hosting and LLM costs. That is, our resume agent builds directly, but it is very optimized, and it turns out to be inexpensive for us, the resume generation itself, so we can make the price lower. And the biggest expenses are actually on marketing. Yes. Listen, well, that's a really good price. I wanted to ask you for a discount, but I realized that there's nothing to ask for here. Yes, it's so good. Well, we can, we can give a discount. I think that from four dollars, a discount. Well, per week. What is $4? I think in the US you can't buy anything. What can you buy for $4? A bun, maybe, right? And not a very good one, right? And not even the best one. Yes. Yes, yes. Yes. Therefore, I think that we will do without a discount. Listen, such a question, probably the last one about how we are doing now and you will show what I got, a kind of business card, my resume, and, uh, and in general, the topic of resumes is so interesting, and you are also involved in it. This adaptation of resumes to vacancies. Recruiters, on the other hand, build their ATS systems, identify adapted resumes, written by ChatGPT, right, so it's some kind of fight of robots. And from all sides, everyone is trying to deceive each other. Some build fences, others try to climb over these fences. What will happen to resumes? I've been asking myself this question for a long time and asking all my guests. Will the resume in its current form die out? Because there is a lot of, well, as you yourself say, dishonest, embellished, and so on. I think not. Globally, it definitely won't die out, because a lot of processes are built on it. That's the first thing. And secondly, different, different industries develop differently. So, for example, in Software Development, you have agents who apply for you, customize anything, but, for example, in some more conservative industries, people may not have resumes at all. And some people don't even know about ChatGPT or know, but don't know that you can generate resumes there. So they just don't have this information. Therefore, we are so smart. Yes. Yes. Therefore, just as there is social stratification, there is technical stratification. And in this, in this area, software and specifically the tech industry has moved forward. And, well, again, how, without a resume? Well, it won't work. Perhaps it will be just one of the factors. If now it's some kind of main factor for preliminary candidate filtering, then, perhaps in the future, it won't be the main one, but one of them. For example, they will analyze social media profiles, GitHub, and so on. I've seen startups that filtered candidates based on some links. Uh-huh. Listen, I just remembered, I had an interview with Olga Ovcharenko, and she works in the city hall of Austin. And she says that they still use Excel files. So they don't even have ATS systems at all. She says: "What ATS, what filters?" We accept all resumes, we enter them into Excel, and that's it. So there, well, in less advanced industries, there is manual labor, they don't even have any filters. I think that there, yes, there is still a long way to go, yes, to these resumes compiled by ChatGPT. Therefore, yes, guys, if you want to find a job and hack the system, go to industries where ChatGPT hasn't gotten yet. And be very unique there, build your most embellished resume, and you will definitely be hired. 100% 100% somewhere in the settings, a person who will deal with resumes, already a big plus. And if it's also customized, and if it also has a link to the website that we will make according to your idea and mine, which we, yes, you will definitely be top-notch, yes, the very ones with a QR code, so directly. Well, a QR code, probably difficult, right? It won't output it. Well, on a printed resume, you can make a printer. Directly into the printer, yes, it goes, yes. Well, to print, I think people can in general. PDF. Well, yes. Here, I think that's where they print, friends. Yes. Listen, cool, cool. Well, are you ready to show what we got? Yes, let's see now. I haven't looked, but something, something, something even exists. But for some reason, it considered you a frontend developer. Well, let me be a frontend. No, no, something, something, something didn't generate, something is wrong, yes, but this is web coding, so just leave it like that and talk for half an hour and let it generate, it won't work, because why, it, for some reason, couldn't read your documents, and it only understood your name by the filename. What a smart thing. Well, let's do it. So it couldn't parse your resume PDF. Yes. Yes. By the way, it parses normally. Well, I don't know. That's a good question now. I've been living with it for many years. Maybe it doesn't parse. At least, I definitely uploaded it to Claude. And when I asked how suitable I was for this position, it seemed to read it. Well, but now, let's do it, so I don't know what's there. I just Ctrl A and copied the text here at all, well, in general. Uh-huh. This is very useful. How useful is it? Wow! See, it noticed that you are a product with ten years of experience, not a frontend developer. Uh-huh. Well done, well done. Yes. Uh-huh. Up-to-date information. Well, this, by the way, can be seen immediately. Uh-huh. Oh, see, you've already passed. Yes, yes, yes, yes. Oh, cool, cool. Yes, super. Oh, download CV even. So, contact. Well, most likely, nothing will happen, right? But it will happen? No, look. Yes, yes. Well, it surprises, but it won't work. Well, although, although, although it will. Well, how? Ah, everything, it updated, right? React is still with me. Well, it's, it's working on it now. Ah, I see. Uh-huh. Uh-huh. And here are the skills, something went, Oh, Prod. Yes, here, here it goes, yes. Research, team leadership, analytics. Everything, I already want to hire you. Well done. Well done. How true is this? Is everything, everything, everything true? Yes. Yes. So it didn't make anything up? Yes. Absolutely nothing made up. Yes. Yes. Well, I don't know about reducing Job Search Time by 50%. Here, I don't know, I don't have such direct data, I don't know how to measure how much faster people find jobs with me. Is this information in the resume or did it make it up? Yes, yes, this is information from the resume. So it took it from there. Right. Yes. So, product management. Uh-huh. Well, I don't know the percentage either, it put it in itself, because I, well, I don't have such information in my resume. Mmm, analytics is correct, right? Mmm, well, I probably don't know Excel that well. It has a good opinion of me. Well, okay, let it be. Uh, well, SQL, let's be more modest, 75%. Well, this can be done, you can literally ask: "Make Excel 86%", and it will do it, so it? Yes, yes, I understand. Yes, listen, cool. Yes. Uh-huh. Uh-huh. This is also clearly not mine. F, yes. Well, here, here you probably need links. If, in principle, well, there are some links to projects, then Uh-huh. Then you can send them to him, and he will add them, describe them. So, Aha. Well, let's look at Experience. The most important thing is actually what it put at the bottom. Well, I think it's still working on it. Ah, it's still working, I see, yes, because, uh, it's working on the experience. Uh-huh. Uh-huh. Yes, because this is the most important thing. This is my experience. Ah, look, yes, founder. Everything is super. Yes, present. Cool, cool. Yes. Principal. Uh-huh. Super. Senior. Excellent. Senior. Oh, it's beautiful. And download full resume, super, get in touch. Let's see, what's there? Yes, it didn't put my, uh, location, it didn't write it. Well, it says you are ready for relocation. Yes, but where is my location? What am I a guest? No, but it put it all in. Oh, how smart. So now everyone will call me. Well, I'll publish it now and it will call. It will call. Well, okay, let them call. Yes, listen, cool, cool. I really liked everything. Super, well done. Well, this is Wiсёрf, well done. Wiсёрf, yes. Death portfolio. Yes, well, let's assume it will change everything. I believe it. Already, yes, it's already changing marathon Runner. And I like it. It chose from all the things that I'm really proud of. I like that it called me a marathon runner. Yes, it chose it itself. I have no. I just copied the resume. Uh-huh. Which was. Let's do it right away. Yes, but it, uh, picked out some milestones from my resume. I have it written somewhere in hobbies. Or not in hobbies, or somewhere in Achievements. I decided to add it recently. I thought, let it be, maybe someone will be interested that I'm a marathon runner, but it's not anywhere in the experience. And it chose it. Cool. Cool. What I'm proud of. Well, it's lucky that sometimes it can guess wrong and write something not quite right, but on the other hand, you can ask it to fix it and in general, Yes, yes, we can play with the color, with some design, with something else. I'd love to play, but we don't have time now, yes, we've already kept our viewers, so let's. Very cool. I really liked the tool. Super. I just want to, you know, sit down and continue working and be creative there and add and photos, change the color, pictures, add some other interesting things. Because my resume actually has a lot. I have a large resume. I'm not a proponent of a one-page resume for myself personally. Yes, I have some narcissistic component that my resume is two pages. I wrote a lot there, to know the rules, to break the rules, you need to know them. Yes, yes, yes, yes. Therefore, yes, I have a lot. I have volunteering, and hobbies, and some other things that are important to me. Super. Well, then my last traditional question to all my guests. What can you wish to those who are currently looking for a job? I'm sure many are doing just that right now. First of all, don't give up. I understand that this can be a very exhausting, difficult process, but I can say that all the guys who were looking for a job, with whom we came, they all found one. That is, despite all the difficulties, that is, directly, well, I really liked it, in some chat they wrote that the only way to get a job is to go and embarrass yourself. That is, you go and embarrass yourself, and you become better, better, better with each interview, and at some point, you will be better than the competitors, and you will get a job. So it is. Well, what, yes, on this positive note, we will end. I wish all of you to go and embarrass yourselves. I will also embarrass myself. Here, Fedya, I wish you too. I think you've already found a job, right, but you've already embarrassed yourself, right? Do I understand correctly? Well, yes. I have a lot of experience in this. A lot of experience. I also have a lot of experience. I also embarrassed myself for many years in the US, so I think nothing can embarrass me anymore. I don't care at all what they say about me. Cool, listen, thank you so much. It was incredibly interesting. Personally, it became much clearer to me what web coding is. Honestly, I haven't delved into it yet. I've heard a lot about it, but somehow I haven't gotten around to it. So, I'll probably try such tools for dummies myself, like Lavable. I'll see how it works. Yes. And I liked the idea of watching a ten-hour course on YouTube. I think that's also a super idea, even, well, for those who just generally want to get a little closer, more seriously involved in it. So, thank you so much. Thank you for your time. Thank you to everyone who watched, who watched until the end. Please write your comments, questions, wishes, your opinion about web coding, your experience, if you have already tried something. Tools. So let's create a large knowledge base, because the tools are developing very quickly, new things are constantly appearing. And today this is relevant, and we are recording this episode in July 2025, and in six months, perhaps, it will already be an outdated episode, right, so we will have to record a new one. So, thank you so much. Thank you for inviting me. Have a good time of day. Goodbye. Thank you. Thank you everyone. Bye.