Claude Code · Non-Technical · Hackathon
Five hours. From "what's a CLI?" to a working product in production. No CS degree, no bootcamp, no "I've been coding since I was 12" backstory. Just me, a terminal I was scared of, and Claude Code.
If you've been watching tutorials and feeling like everyone skipped a chapter you didn't get — this one's for you.
Most Claude Code tutorials start with "open your terminal" like that's a normal Tuesday for everyone. It isn't. So let me give you the real version.
Here's what you actually need before you can do anything fun:
The funniest part? You can ask Claude Code itself to install Git for you. Just type claude in your terminal, hit enter, and ask it: "can you install Git for me?" It'll figure out the commands. If you get an error about admin permissions on Windows, right-click PowerShell and run it as administrator. Done.
This is the part that took me the longest to wrap my head around — Claude Code isn't an app you double-click. It lives inside your terminal. Every time you want to use it, you open the terminal and type claude. That's it.
Here's where most non-techies give up: they stay in the terminal, can't see what's happening, and assume coding just feels confusing forever.
It doesn't have to.
Download VS Code. Open the folder you're working in. Now you can see every file Claude creates, every change it makes, every line of code on your screen — instead of squinting at terminal output.
This was the unlock for me. Suddenly I wasn't flying blind. I could watch Claude build something file by file, and when it broke, I could actually point at the broken thing and say "fix that."
If you've never touched a code editor in your life, that's totally fine. You don't need to understand the code. You just need to see it move. That's the difference between Claude Code and tools like the Claude desktop app — the desktop chat is great for thinking and planning, but Claude Code is where you actually ship.
I went into a hackathon at Temasek Shophouse having never pushed anything to prod. Ever. I arrived at 7am — the official start was 10.00am. I was the first participant. The security guard was genuinely puzzled.
By lunch, I had a live product. Here's roughly how it went:
Set up the folder, opened it in VS Code, ran claude, told it what I was building in plain English.
Watched it scaffold the whole thing. Said "yes" a lot when it asked permission to run commands. Said "no, redo this part" when it went off the rails.
Hit a wall. Asked the person next to me what a "spawn" was. Got humbled. Kept going. (Shoutout Sayyid — this was his 59th hackathon. That energy is contagious.)
Connected GitHub, pushed the code, deployed it.
It worked. In the real world. On the real internet. I almost cried.
The thing nobody tells you is that prompt-based coding is mostly about being clear, not being technical. If you can write a good brief for a designer or a VA, you can write a good prompt for Claude Code. The skill transfers.
What I couldn't have done alone: figure out the vocab. Words like CLI, repo, spawn, fork, prod, staging — these get fired at you constantly and nobody stops to define them. That's not your fault. That's the industry's fault.
Quick glossary: CLI = the black box you type into. Repo = a folder for your code. Prod = the live version users see. Staging = the practice version. Spawn = starting a new process. That's it. That's the whole lesson.
A lot of what gets called "technical" is just vocabulary you haven't been taught yet.
Once you know the words, the wall comes down. And once the wall comes down, tools like Claude Code become genuinely accessible to anyone running a business, a team, or a side project. I've seen 55-year-olds build AI workflows from scratch and business owners ship internal tools they used to pay agencies $20k for.
The gap isn't intelligence. It's exposure. And exposure is fixable.
There's also something worth naming plainly: some techies deliberately use jargon as a moat. The jargon isn't incidental — it's the whole identity. That's elitism, it's annoying, and it actively pushes out the exact people who'd benefit most from being in the room. If you're on the receiving end of this: ignore it. Find safe spaces and attend those instead. There are enough good humans in this space — go find them.
If you're a non-techie trying to learn anything technical, hackathons beat courses, tutorials, and "watch me code" YouTube videos every time. Here's why:
I attended with Jess and Tracy from the Courage Chapter. Tracy is on Windows — her methods look completely different from mine, she was dealing with consoles and terminal stuff I'd never had to touch before. That's the other secret of hackathons: you see the edges of your own map.
Stop watching. Open your terminal tonight. Type claude. Ask it to build the smallest possible version of something you actually want — a script that renames your files, a tiny website, a tool that scrapes one page. Anything.
The first time it works, something clicks that no tutorial can give you. You stop being someone who watches techies build things and start being someone who builds things.
That shift is worth way more than 5 hours.
Cowork SG is a free community where non-techies share what's actually working with Claude — no jargon, no gatekeeping. Join us on WhatsApp.
Join Cowork SG Free →