I am not a developer. But I have built more than ten personal apps in the past year, from a step tracking tool to a fitness dashboard to a content calendar that plugs directly into Buffer’s API. Right now I am working on an app to manage the wildly diverse needs of my houseplant collection. All of this came together through AI coding tools, and the experience has been equal parts humbling and liberating.<\/p>\n
Vibe coding is the practice of describing what you want in plain language and letting an AI write the code for you. Andrej Karpathy coined the term on X in early 2025, and Collins Dictionary named it their Word of the Year shortly after. The premise is simple: you focus on what you want to build, and the AI handles the syntax.<\/p>\n
That said, great power comes with great responsibility. I know people far smarter than me who have vibe coded customer-facing products, but I would tread carefully there without an engineering background. Walk before you run, as the saying goes.<\/p>\n
There are certain things best avoided when you vibe code, even if they are only intended for you or a handful of people. Handling real money, storing other people’s sensitive information, or anything with legal compliance requirements (medical, financial, GDPR obligations) should be off the table for now. Start small, and start safe.<\/p>\n
You can vibe code with surprisingly little. The first decision is where your tools will live. Building your own apps does not actually require you to put them on the internet or host them somewhere. They can live exclusively on your device, though the catch is that you cannot easily open them on your phone, and building this way might require a slightly more advanced AI tool.<\/p>\n
Browser-based building means everything happens in a web app. You sign in, describe what you want, watch it build, and click publish. This is the lowest barrier to entry by far, and hosting is often included, so deployment becomes a single click.<\/p>\n
Local development, on the other hand, means your files live on your laptop and you use AI tools that integrate with your terminal or code editor. This approach gives you more control and keeps everything private, but it requires a bit more setup. I currently use Claude Code, GitHub, and the terminal daily, and I will not pretend the first week was not intimidating.<\/p>\n
Most vibe coding guides stop at describe what you want to Claude. The reality is a bit more complicated, but not much. Where non-developers actually get stuck is a little further along: where to put your files, when to back things up, and what to check before you put something on the internet.<\/p>\n
Here is the unglamorous truth: you need a basic folder structure. You need to know that your code should be backed up somewhere like GitHub. And you need to understand that publishing something publicly means anyone can access it. These are not difficult concepts, but they are the scaffolding that keeps your work from disappearing.<\/p>\n
When you prompt an AI to write code, be specific about what you want and what you do not want. Instead of saying make a dashboard, say create a single-page dashboard with a line chart showing daily step counts from a CSV file. The more context you provide, the better the output.<\/p>\n
Also, do not be afraid to iterate. Your first prompt will rarely produce perfect code, and that is fine. Ask the AI to explain what it wrote, request changes, and test as you go.<\/p>\n
Even if you are only building tools for yourself, security matters. Do not hardcode passwords or API keys into your code. Use environment variables instead. And if you are pulling data from third-party services, make sure you understand what permissions you are granting.<\/p>\n
The good news is that AI tools are getting better at flagging potential security issues. The bad news is that they are not infallible. A little paranoia goes a long way.<\/p>\n
Start with something small and personal. A tool that tracks your daily water intake. A script that renames files in bulk. A simple calculator for a recurring task. The goal is not to impress anyone; it is to build confidence and familiarity.<\/p>\n
Once you have a few small wins under your belt, you can start thinking bigger. But even then, keep the scope manageable. The worst thing you can do is start with a massive project and get discouraged when it does not work immediately.<\/p>\n
Vibe coding is not going to replace developers, and it is not meant to. But it is opening doors for creators, marketers, and anyone else who has ideas but lacks traditional coding skills. The tools will keep getting better, and the barriers will keep getting lower.<\/p>\n
So if you have been peering down the how-the-heck-am-I-supposed-to-do-this chasm, take the plunge. Start small, ask for help, and do not be afraid to break things. You might surprise yourself with what you can build.<\/p>\n","protected":false},"excerpt":{"rendered":"
I am not a developer. But I have built more than ten personal apps in the past year, from a step tracking tool to a fitness dashboard to a content calendar that plugs directly into Buffer’s API. Right now I am working on an app to manage the wildly diverse needs of my houseplant collection. […]<\/p>\n","protected":false},"author":1,"featured_media":696,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[115],"tags":[878,881,880,879,734],"class_list":["post-697","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-how-to","tag-ai-coding-tools","tag-citizen-developers","tag-no-code","tag-non-developers","tag-vibe-coding"],"_links":{"self":[{"href":"https:\/\/tick.blue\/blog\/wp-json\/wp\/v2\/posts\/697","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tick.blue\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tick.blue\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tick.blue\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/tick.blue\/blog\/wp-json\/wp\/v2\/comments?post=697"}],"version-history":[{"count":0,"href":"https:\/\/tick.blue\/blog\/wp-json\/wp\/v2\/posts\/697\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/tick.blue\/blog\/wp-json\/wp\/v2\/media\/696"}],"wp:attachment":[{"href":"https:\/\/tick.blue\/blog\/wp-json\/wp\/v2\/media?parent=697"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tick.blue\/blog\/wp-json\/wp\/v2\/categories?post=697"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tick.blue\/blog\/wp-json\/wp\/v2\/tags?post=697"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}