# a gap year in vermont

source: https://samliu.dev/writing/a-gap-year-in-vermont
posted: 17 nov, 2026

i spent a year in vermont at [hack club](https://hackclub.com) after high school. not to be a broken record (many of my peers have said the same) it was one of the best, most unexpected, very much life changing (insert more adjectives) experience i've had.

![local concert & community gathering](/writing/a-gap-year-in-vermont/01.webp)

local concert & community gathering

### hack club's hard to describe...

on paper, hack club is a global nonprofit that supports teenagers to ship technical projects. we run online programs that reward teens for shipping projects and run life-changing events like hackathons where people form their closest friendships and have formative experiences.

to me, hack club is a community of technical folks obsessed with niche problems and creative solutions, building cool stuff not because they're asked to, but because they can.

these programs and events fall under our "YSWS model" (you ship, we ship). there is no correct way to run a program or event. [the system is crazy flexible](https://notes.deven.dev/posts/the-plan-for-hack-club-world-dominance), and it's up to us to figure out what sticks.

![campfire flagship. on a beach in LA making s'mores with propane torches since we couldn't set up a campfire](/writing/a-gap-year-in-vermont/02.webp)

[campfire flagship](https://flagship.hackclub.com). on a beach in LA making s'mores with propane torches since we couldn't set up a campfire

it's so rare to have the opportunity and freedom to experiment and see where random ideas take us. it's not asking for permission, or sitting in meetings to predict what will work. there was no ceiling to what i could do and learn, and i had full control over the vision and execution of my programs.

---

one such program...

we ran the world's largest hardware hackathon for teens, and somehow pulled it off in china? [fallout](https://fallout.hackclub.com) began as a "what if there was a hardware hackathon in shenzhen..." then "wait, why don't we just do this??." we did! it was awesome, and then 2 weeks before the event...

"oh shoot we have twice the amount of people coming than planned?"

we flew to china and locked tf in. i'm beyond grateful for the incredible fallout team, and our local partners: the (many) hotels, venue, vendors, and the bus driver i had to call at 11pm. fallout was the most stressful thing i've ever done, but it was incredibly worthwhile as shenzhen is such an inspiring place to build.

if you're curious about the participant's perspective (way less stressful...) you should watch our [recap video](https://youtu.be/dTGFOKblRc4).

![group photo at the end of fallout!](/writing/a-gap-year-in-vermont/03.webp)

group photo at the end of fallout!

### some advice to future gap-years

consume with salt, as usual. in no particular order

if you're considering a gap year:

- there's no ceiling to what you could learn and do
- you'll meet the coolest people, skilled in different ways
- it'll be the hardest thing you've (probably) done, but you'll actually do it
- living alone is scary, but you get so much freedom. you'll learn a lot and there's friends to support you!
- you should [apply](https://manifesto.hackclub.com) even if you think you're not good enough. no one is good at everything and it never hurt to give it a shot

it's impossible to sum up everything i've learned, but here's some key points... **everyone will do things differently, so you should probably think about it**. i've found these to be pretty true in the stuff i do:

- build the program you personally would want to participate in
- weighted projects aren't everything. build the program because it's what you want to see, not because it'll maximize WPs. oftentimes you'll get more WPs just because it's a great program.
- there's no correct way to do things. if someone "succeeds" by doing things one way, it does not mean other ways are wrong. challenge the status quo
- walk up to others to get their thoughts, or asking how their program is doing
- you will fail! focus on identifying and fixing the issue
- [eighty-twenty rule](https://en.wikipedia.org/wiki/Pareto_principle)
- [ninety-ninety rule](https://en.wikipedia.org/wiki/Ninety–ninety_rule) (this one is so important)
- good dashboards are so important
- numbers often say more than vibes. graph it out
- build tight feedback loops and flexible programs. ship early, ship often AND review early, review often
- get the WP into the db within the first 2 weeks of launch
- cap R&D time to a month for large programs, then force yourself to launch regardless of the state
- there is no correct way to make a dashboard, but there are wrong ways...
- do not use ai to come up with methods for analyzing data (ai writing calculations or code for dashboards is okay, but the underlying method should be by humans)
- [keep it simple stupid](https://en.wikipedia.org/wiki/KISS_principle). fillout + airtable is sufficient for smaller programs
- keep teams small and flexible
- be wary of fake work and productive procrastination
- don't build infrastructure/tooling for a hypothetical audience
- don't build infrastructure/tooling with "it'll be org-wide" in mind
- build infrastructure/tooling as you need it, specific to your uses
- your site can be the fanciest thing in the world, but if the core flow is broken, it's not working
- kill dead programs and events. if it's not worth it stop doing it
- oftentimes it's faster to just do the work than to make a tool that speeds up doing the work. (this is a very easy trap for review and reviewer tooling)
- sleep on it instead of working at 3 am

![spontaneous trip to a fast food restaurant in NYC](/writing/a-gap-year-in-vermont/04.webp)

spontaneous trip to a fast food restaurant in NYC
