← All articles

Community and hobbies

A First-Timer’s Guide to a Community Hack Night

Find out what to ask, bring, and expect at a community hack night, even if you are new to coding or do not have a project yet.

Illustration for a first-timer’s guide to a community hack night: neighbors sharing laptop ideas around a table at a community hack night.

Check the event’s format before you go

A community hack night might mean working on a shared project, pairing on personal ideas, testing a prototype, or gathering to learn together. The format depends on the organizer, so read the event details and ask what a first visit looks like. Find out how long it runs, whether people work in teams, and if you need a laptop or any software installed. A quick answer can prevent you from preparing for a project sprint when the evening is meant for introductions and show-and-tell.

Ask who the event is designed for. Some nights welcome people who are curious but new to coding; others assume attendees already know particular tools. If the description is vague, say what you are interested in and ask whether there is a suitable way to take part. You can also ask about the venue, Wi-Fi, outlets, and whether observing for a while is fine.

You can contribute without arriving with a finished idea

A useful first goal is simply to understand what the group is working on. You might help read instructions, try a prototype, take notes, improve a short piece of documentation, sketch an interface, or ask questions that reveal what a newcomer finds confusing. Those options depend on the project and the team, so offer your interest and let people say what would help. You do not need to claim skills you do not have or volunteer for more than you can finish.

If you have an idea, describe the problem you hope to explore in one or two sentences. Ask whether anyone wants to work on it before planning a large build. A small first step, such as listing questions or making a rough sketch, is easier for other people to join than a fully defined project with hidden decisions already made.

Arrive ready to ask and listen

When you arrive, find the organizer and ask how people usually get started. A simple introduction can include your name, what brought you there, and one thing you would like to learn. Then listen to the group’s expectations for the evening: where to share work, how to ask for help, and when people plan to wrap up. If you are unsure what a project needs, ask before changing files or steering the discussion.

If you do not have a laptop, cannot install software, or need a quieter place to focus, tell the organizer early. The group may have a way to participate or may be able to clarify limits before you make the trip. Bring only what the event asks for and avoid installing unfamiliar tools or extensions unless you understand the source and trust it.

Keep shared work and personal information safe

Before opening a project, ask whether it is public or private and what you are allowed to change. Do not share passwords, access keys, private code, or someone else’s user data in a group chat, screenshot, or demo. If you see credentials or personal information in a file, do not copy or repeat it; tell the project owner privately and follow their instructions. Ask before photographing a screen or posting a person’s work online.

Give feedback on the work rather than the person. Try questions such as “What did you want this button to do?” or “Would it help if I tested this flow?” Accept that a team may choose another approach. A community event is a place to learn how people collaborate, not a promise that every idea will be used.

Leave with one clear next step

Near the end, ask what was completed, where the group keeps notes, and whether anyone owns the next task. If you want to return, find out when the group meets again and what would make a useful follow-up. You can also leave after one conversation or one small contribution. A successful first night is not measured by how much code you write; it is knowing what the group does, meeting a few people who share your curiosity, and deciding whether the next session sounds worth attending.

Meet someone new on HMU