An event is a consumable.
The speaker performs, the audience receives, everyone feels briefly connected, and the room dissolves. Even a good workshop can become a lesson purchased for an evening. People leave with inspiration and return to separate projects.
A meeting is different. A meeting assumes there will be another meeting. It has insiders—not as a status hierarchy, but as people who inherit unfinished work. Participants arrive carrying what changed since last time. The room has memory.
I do not need another social network that makes technical people present themselves more efficiently. I want a mechanism that helps us make something together.
Stop negotiating in comment threads
Most gatherings begin with an unnecessary argument disguised as coordination:
- Which evening works?
- Which place?
- Which project?
- Which activity comes first?
- Who has equipment?
- Who only wants to observe?
A comment thread is a poor interface for this. Proposals become prose, votes become reactions, and changed preferences are scattered across time.
The meeting tool should represent the choices directly. People can suggest time windows, venues, activities, and sequences. A person may be available for one part and not another. An activity may require a minimum number of participants, a tool, a vehicle, a quiet room, or daylight.
The result is not merely a calendar event. It is a small plan with dependencies.
Hidden cards before visible consensus
Early ideas can be fragile. When every proposal appears immediately, the first confident suggestion anchors the group. Quieter participants edit themselves around it.
I want hidden activity cards.
Each person privately proposes something tangible: test a board, review a schematic, repair a machine, practice a song, walk to photograph a site, write a paragraph, compare two models. The cards can be revealed together after everyone who wants to contribute has done so.
Then the group composes the meeting from actual intentions rather than the momentum of the first message.
Hidden does not mean anonymous by default. It means unanchored during proposal. Once revealed, the person who proposed an activity can explain what it needs and whether they want to lead it.
Promise attention instead of demanding it
One product idea in this family is “Calendly meets Twitter”: a person does not merely send a video or essay and hope the recipient enters an engagement funnel. The recipient promises a time to read or watch it.
That promise changes the exchange.
The sender no longer needs to keep pushing. The recipient does not have to pretend that saving a link is attention. The system can record a modest commitment:
I will give this twenty minutes on Saturday morning.
The appointment belongs to the recipient. It can be moved or declined. No streak, guilt counter, public score, or automatic escalation is needed. The purpose is to make attention intentional.
This same mechanism can support a meeting. Before arriving, a participant can promise to inspect one artifact. During the meeting, the author gets a prepared collaborator instead of a room full of first impressions.
Bring an accomplishment
Status meetings are hated when “status” means performing productivity for a manager.
Among independent builders, a status meeting can be liberating. Nobody assigns the project. The recurring question is simply:
What became more real since we met?
The answer can be small:
- one failing test;
- one measured waveform;
- one paragraph;
- one corrected diagram;
- one package soldered badly enough to teach something;
- one decision abandoned with reasons.
This creates continuity without pretending every participant is on the same project. Over time, common needs appear. One person has a board and needs firmware. Another has a model and needs a physical test. A third knows how to photograph the result. Collaboration grows from demonstrated edges, not networking theater.
Event and meeting need each other
Events are not bad. A public event can introduce an idea, welcome newcomers, celebrate a result, or teach a bounded skill. The mistake is expecting a sequence of events to become a working group automatically.
The relationship should be explicit:
- A public event opens a door.
- A follow-up invitation names a concrete meeting.
- The meeting has a small recurring cadence.
- Participants bring artifacts and commitments.
- Finished work returns to a public event when it is ready to be shown.
A colorful flyer can help, but the flyer should lead somewhere more durable than another flyer.
The smallest useful product
The first version does not need avatars, a metaverse, or a feed. It needs:
- participant availability;
- proposed place;
- hidden activity cards;
- reveal and ordering;
- requirements for each activity;
- one promise-to-review slot;
- a recurring next date;
- a compact record of what was made.
Files and links can attach to activities, not float in a general stream. Notifications should serve commitments rather than manufacture urgency.
The product succeeds when participants stop discussing the product because they are busy doing the thing it arranged.
Events entertain. That is valuable.
Meetings remember. That is how something gets built.