What Kind of Event Will Engawa AI x XR Be?
In the previous entry, I wrote an overview of "Engawa AI x XR," which will start in Motoyawata, and information about the first session.
This time I will write about what I am vaguely thinking regarding the event structure.
Since this is a newly starting study group and may feel a little mysterious, I will write about what kind of structure I imagine for the events.
That said, if the direction is made too clear before it really starts, I think it may run out of steam and not work well. Still, I will write what I personally think could make a good event.
A Space Where It Is Easy to Listen and Easy to Present
In the past, I hosted a closed JavaScript study group called "Okachi.js" almost once a month in Okachimachi. Because it was closed, it had a direction different from ordinary study groups, such as the following.
- Even without slides, it was okay to talk on the spot about a topic, rather than "presenting" in a formal sense
- Creating an atmosphere where people could ask questions even if they seemed like things everyone should know
- If someone was interested, they could try things hands-on right there
In any case, I personally found it comfortable to have a place where people could ask silly questions without creating an atmosphere of "how do you not even know that?" Since the end of the COVID period, however, I have not held it much, which brings us to now. I have wanted to use the style I discovered through Okachi.js somewhere, so this time I have arranged it a little and decided to hold the first session with the following three parts.
- A "Talk Session" where people bring something they recommend and talk about it
- A "Hack Session" where people actually try things that came up in the talks
- A "Sharing Session" where people share what they did today or what they have been doing recently
The time allocation is not strictly fixed. For example, if there is nothing left to introduce, the "Talk Session" ends. This is not a large-scale conference, so there will not be an announcement like "That concludes the Talk Session." lol
For convenience, when introducing what kind of study group this is, I divide it into three sections to show that these sections exist.
The middle "Hack Session" is something like a hackathon, but I think the attractive part is that you can try things while asking questions of the person who introduced them in the "Talk Session."
For example, this time the theme is Codex + visionOS, and I will talk about Seiro MCP, a development tool for Codex. If someone wants to try it, I, the developer, will be there, so I can help with setup and troubleshooting. That makes it a good deal. If someone else introduces something, they should have used it to some extent, so they can probably help when someone gets stuck during introduction.
I think the final "Sharing Session" is quite important. I used to attend development camps, and I liked having time at the end for outcome presentations. During that time, everyone would stop working for a moment and present what they had done during the camp. It was not mandatory, so some people did not present. If the results were not good, they might talk about that, and some people presented what they were making themselves. Some people spoke briefly for one minute, while others gave a careful demo, so the time varied by person.
Communities like this are fluid, or rather, they are easily influenced by the people who participate, so it is very possible that things will change in the future. If you are thinking of taking a look, please access the event page. Sharing it on social media is also very welcome.