All Activities
March 28, 2026 · Central Market, Hong Kong · 4 min read

Claude Code Community Day: Hong Kong

A photo-led recap from the Claude Code Community Day I co-hosted at Central Market: setup help, first projects, younger builders, and 40 people opening the tool.

Claude CodeAIHong KongCommunityLunatechs
40+ Attendees
1 10-Year-Old Builder
7 Lunatechs Meetup
Claude Code Community Day group photo at Central Market, Hong Kong
Central Market, Hong Kong. Laptops open, tables packed, and people still waving for the group photo.

Lunatechs Meetup #7 · March 28, 2026

Forty people brought laptops, questions, and half-formed ideas.

I co-hosted this as one of the Lunatechs organizers in Hong Kong. The premise was simple: help people get Claude Code installed, open a project folder, and start.

I am not a developer. Claude Code made me feel like I could build things that were out of reach a month earlier. I wanted people to see that path without pretending it was effortless.

This was not a polished demo day. It was laptops, chargers, half-finished prompts, and someone asking what to try next.

The spark

Claude Code was different because it worked inside a folder.

ChatGPT was the first big shift for me. Claude Code shifted something else: it could read a project, edit files, run commands, and keep going.

That mattered because I was already building things I did not expect to build: Mandarin tools, progress tracking, study flows, and small systems I could not have built alone.

Eric and attendees at tables with laptops during Claude Code Community Day
Most of the work happened table by table, with laptops open.

What people needed

The event was mostly setup help and first projects.

01

Setup help

Installation, auth, and the right project folder can stop someone before the work begins.

02

First projects

People brought app, workflow, and automation ideas. Sitting together made the first prompt easier to write.

03

Younger builders

A 10-year-old came because a 15-year-old had built a game. That was probably my favorite detail of the day.

04

Starter kit

I put together presentations, reference cards, and guides to help people get past the blank-page and first-setup problem.

The room

Central Market was crowded with laptops.

Some people paired up. Some debugged setup. Some were trying to understand why Claude Code felt different from a chat window.

I moved table to table, answered what I could, and watched what people tried first.

Small group discussing Claude Code around a laptop at Central Market
Questions got better once Claude Code was open on someone’s own project.
Eric with two young Claude Code Community Day attendees
The younger builders were not waiting for a perfect curriculum.
Claude Code Community Day attendees smiling with laptops at Central Market
Small groups formed naturally around laptops, questions, and half-built ideas.

What I noticed

Beginners wanted to try it, not hear another AI forecast.

People wanted to know what to install, what folder to open, what to ask first, and what to do when the command failed.

That is still the best way to learn these tools: open a real folder and keep someone nearby who can help when it breaks.

Claude Code Community Day attendees working at outdoor tables in Central Market
Not a lecture hall. More like a temporary build space.

Around the tables

The orange Lunatechs mascot made the rounds.

People came to learn, but it was not stiff. There were jokes, side conversations, quick photos, and a lot of people asking for help without making it a big deal.

That made setup questions easier to ask.

Claude Code Community Day attendees with orange Lunatechs mascots
The Lunatechs mascot became a tiny recurring character at the tables.
Eric taking a selfie with Claude Code Community Day attendees working on laptops
Builders, laptops, and a lot of setup tabs.
Group photo from Claude Code Community Day in Hong Kong

Closing note

I left wanting more laptop-first events in Hong Kong.

Hong Kong needs more rooms where people can ask basic questions out loud. Watching someone install Node, fix a path error, or make one tiny app run is the part people remember.

People left with the tool installed and one less reason to be intimidated by it.