After seeing the offline activities of the Internet, I mentioned in the group that Kaiyi can handle the offline venue. So, let's start brainstorming a few ideas.
The ideas and thoughts can be developed according to the following structures:
- The purpose of the plan, why we need to do it, and its necessity.
- The content of the plan, what others can hear, and what we can talk about.
- The structure and form of the plan, how long to sit together, how many parts, whether it is mainly listening or interactive.
- The advantages, disadvantages, technical deficiencies, and hidden risks of the plan.
- Whether the plan can be sustained.
Purpose of the plan#
We can organize controlled communication activities with minimal effort, such as interactive discussions with listeners and technical sharing. If it's only once, it can be an offline meeting with listeners. If it's periodic, such as weekly, biweekly, monthly, or quarterly, it can be related to technical sharing.
We don't have to consider long-term plans. If I have three opportunities to organize offline activities, the audience is my own listeners, and we can expand around the program.
Meet the needs of listeners for cohesion and companionship,
Meet the desire of guests and hosts to try something new.
Content of the plan#
First time#
It can be a meeting with listeners, where the host greets everyone, and each person introduces themselves and discusses technical and workplace topics together. It's like an offline version of podcast recording.
Add some visuals. Talk about what Xinbao has seen recently and share your thoughts. Talk about the viewpoints Xinbao has written recently. Record remotely on-site, the technical detours I have taken over the years, and the strange workplace things I have encountered. Wait, aren't we a chat show?
For example, if we have recorded a program recently, did everyone listen to it? For example, last year, Aryu mentioned a few points, repeat and expand on them.
Prepare some questions, ask and answer them yourself, related to the program.
Periodic#
After the first time, if it goes well, we can continue:
- Ask Teacher Hai to talk about what ast-grep is and what it can do.
- SimonHe wrote some plugins, what are they used for? Historical guests who are independent developers can talk about their experiences.
- For libraries, for example, Kobe's devtool, ZhiZi can talk about new features in Vue, and Smart can talk about implementing Svelte.
- Innei's blog content, etc.
Workshop#
It can be a workshop, where guests have 15-30 minutes to do a simple tool together,
- Learn the new features of Vue 3.x in 30 minutes.
- Learn how to make a simple blog using Svelte/Next.js/Astro in 30 minutes, etc.
Technical sharing meetup#
It can be a technical sharing session, supplementing the podcast chat.
It can be a topic discussion or offline program recording.
Structure of the plan#
It's about to be revealed:
Check-in, self-introduction, (roundtable discussion, solo technical sharing, workshop, etc., choose one or two), interaction, and photo at the end.
Check-in, self-introduction, and opening should not be a problem within half an hour.
For activities that choose one, one hour should be fine.
Interaction for half an hour should be fine, and it can be filled with program comments and new technical viewpoints.
If it's about 2 hours of interaction, it should be able to fill the time.
Feasibility of the plan#
Expectations for failure#
If the plan is organized once or twice, there should be no major problems. Whether it can be done periodically can be put aside for now. The workshops mentioned earlier are based on the premise that they can be done.
If it's only two interactions, with no additional costs, just organizing content and finding people, it should be doable.
Risk control#
Mention the disadvantages and risks.
- Can we find guests? Me, Kaiyi, and friends in Beijing like Smart should be able to meet the minimum requirements. We can also have a guest online.
- Can we find listeners to come to the venue? If the venue is suitable and it's on the weekend, we can guarantee at least 5-10 people. If not, we can fail two or three times and stop doing it.
- Does the venue cost money? Can we provide water for the attendees? See if Kaiyi can get a venue for free, and we can buy water and small biscuits on-site. With 100-200 yuan, we can at least buy water and small biscuits.
- What are the minimum requirements for the venue?
- There should be seats, relatively quiet positions. We can try offline recording and use my Bluetooth microphone for recording.
- If the network is good and there is a large screen or projection, we can have remote guests.
- The people who come should ensure that they are energetic and able to walk and talk.
- It might be awkward at the venue, and the guests might not know what to talk about. It shouldn't be a problem, as there are many alternative fillers.
- There might not be enthusiastic atmosphere and feedback at the venue. It shouldn't be a problem, as we can find an audience leader.
- If there is a lot of time available at the venue, more than half an hour? It shouldn't be a problem, as we can prepare a video in advance.
- If the time at the venue is very tight and we can't finish in two hours? We can cut some content appropriately.
Sustainability of the plan#
To be determined, we'll see the results after one or two times.