A Manual for Your First IT Study Group: Registration, What to Bring, Etiquette, and the Flow of the Day (2026)

What is missing at a first event is not technical knowledge

Before attending an IT study group for the first time, small worries come to mind before the content does.

• Whether your level is good enough
• Whether you will stand out attending alone
• What you should bring
• Whether you can leave partway through
• What to do if nobody speaks to you

What a first visit requires is not detailed technical knowledge. It is knowing the flow of the day and the range of things you get to choose. How much you talk, how long you stay, and whether you ask a question are all chosen by the person attending.

This article explains everything from searching for an event to after you leave, in order. It covers the first-visit conventions common to IT study groups generally. Three things are handled by other pages.

• Find a session you can attend now: event listing
• Registration steps, venue guidance, and day-of contact details specific to Miyako de IT: first-time guide
• Three routes for finding events in Kyoto and the differences between formats: Looking for a study group in Kyoto? How to choose an event for IT engineers

---

1. Choose the event you will attend

There are five items to check on the event page: who it is for, the format, the cost, the venue, and the code of conduct.

Who it is for

Look for statements such as beginners welcome, for experienced participants, or for students. Even when a page says anyone may attend, some sessions are advanced. Talk titles and reports from past sessions show the actual level.

Format

The main formats are as follows. The order does not indicate ranking.

• Co-working session: each person advances their own work
• Lightning-talk event: several people give short talks of 3–5 minutes. Many sessions allow attending only to listen
• Lecture or seminar: you listen to a speaker
• Hands-on workshop: you learn while doing
• Networking event: conversation is central
• Reading group: participants work through a technical book
• Hackathon: participants build something in a short period

If you want to talk less at a first visit, a co-working session or a listening-centred format suits. Registration steps and the flow of a co-working session are covered in What is a mokumoku-kai? Registration and the flow of the day; moving to the presenting side is covered in Your first lightning talk: a complete guide.

Cost

Check the participation fee, food and drink costs, and cancellation terms. Some sessions are free; others collect actual costs for the venue or refreshments.

Venue

Check the route from the station, the entrance, the floor, whether shoes come off, Wi-Fi, power, whether food and drink are allowed, and step-free access. At sessions held in temples or machiya townhouses, removing shoes and the heating and cooling differ from an ordinary meeting room.

Code of conduct

Look for statements on sales solicitation, harassment, photography, and handling of personal information. If a reporting contact is also given, you know where to turn if something goes wrong.

---

2. Register

Most IT study groups take registrations through an event page such as connpass.

If there is a questionnaire, answer as far as you can. There is no need to describe your employer or technical level in more detail than necessary.

After registering, keep the following to hand.

• Date and time
• Venue address
• Day-of contact details
• Your registration confirmation
• What to bring
• How to cancel

If you can no longer attend, cancel as soon as you know. At events with a capacity, that lets someone on the waiting list attend. Not showing up without notice also affects seating and catering arrangements.

For Miyako de IT sessions, the registration steps and day-of contact details are held on the first-time guide. This article does not repeat them.

---

3. Prepare what to bring

There are five basics.

• A smartphone
• Your registration confirmation or reception details
• A charger
• A laptop, if needed
• Something to drink

Some formats require additional items.

Business cards are not required. You can attend without them.

At a hands-on workshop, time spent setting up an environment on the day reduces learning time. If the event page specifies preparation, complete it the day before.

---

4. Arrive at the venue

Aim to arrive about ten minutes before the start. Arriving much earlier may catch the setup; arriving late can make the entrance harder to find.

At reception, this much is enough.

This is my first time here. My name is [name]. Thank you for having me.

Even if you are asked for a fuller introduction, your name, your work or what you are studying, and one thing you want to learn today is sufficient.

Almost no events specify a dress code. Everyday clothes are fine.

---

5. A short self-introduction is fine

A self-introduction takes about 30 seconds. There is no need to force in a technical topic.

An example for someone working:

I am [name]. I usually work in web development. I came today because I wanted to see examples of AI-agent implementations. Thank you.

An example for a student or someone without experience:

I am [name]. I have just started learning programming. This is my first study group, so I came to see what it is like.

There is no need to pretend to know a technology you do not. Saying that you are still learning tends to bring back the explanation you actually need.

---

6. Conversation is not compulsory

Even at a networking event, you do not have to speak with everyone. How much you talk is yours to decide.

Questions that are easy to use when you are standing alone include the following.

• What did you come to see today?
• Is this your first time at this community?
• What have you been building recently?
• Do you use this venue often?
• Was there anything in that talk that caught your attention?

When you do not want to talk, looking at the materials, going to get a drink, or returning to your work are all fine. Stepping away is not rude.

If anxiety about attending alone is the larger issue, Nervous about engineer meetups? What to know if you are attending alone sets out common worries and concrete ways to handle the day.

---

7. Questions have a shape

A question tends to land when it follows this order.

1. What you are trying to do

2. How far you have tried

3. What you do not understand

4. What range of answer you are looking for

For example:

I am building a form in Next.js. Submission works, but I am unsure how to design the display when an error occurs. Rather than an implementation example, could you tell me how to think about it?

There is no need to feel apologetic for asking. Do, however, avoid keeping one person occupied for a long time, and check whether the rest can wait until later.

---

8. Can you leave partway through?

Unless the event page restricts it, many events allow leaving early. Some formats with a set progression, such as hands-on workshops, make it difficult, so check the event page.

If you leave, say a word to reception or the organizer.

I have another commitment, so I will leave around [time].

That lets the organizer keep track of numbers, rather than someone simply disappearing.

---

9. Check the rules on photographs and social media

Check whether photography is allowed, whether faces may appear, and the rules on posting to social media. If you do not want to appear, say so at reception. Take care that name tags and laptop screens do not show personal information.

Do not post photographs of other participants, or what they said, without permission.

---

10. If sales or solicitation becomes a problem

If you have difficulty with solicitation that is hard to refuse, religious or political activity, investment, recruiting, sales, or requests for personal contact details, tell the organizer. There is no need to keep enduring it.

Organizers state the code of conduct and a reporting contact on the event page. Whether sales between participants is prohibited outright differs by event, but continued solicitation that ignores the other person's wishes is not accepted at any event.

---

11. After the event

If you exchanged business cards or social accounts, send a short message if you want to.

Thank you for today. What you said about [topic] was helpful.

There is no need to promise to attend again.

Whether the event suited you can be reviewed from the following angles.

• The content
• How much conversation there was
• The venue
• The participants
• How the organizer handled things
• Whether you want to keep attending
• Whether another format might suit you better

Sometimes one visit is not enough to judge. Changes described by people who attended the same event several times are set out in The value that starts with three visits.

---

Notes for students and people without experience

Will I be out of place?

If an event states that beginners are welcome, you can describe your experience honestly. People who have just started learning attend too.

Can I attend without a laptop?

For listening-centred events and networking events it may not be needed. For hands-on workshops and co-working sessions, check the event page.

Can minors attend?

Check guardian consent, the timing, whether a social gathering involves alcohol, and the venue's rules with the organizer in advance.

Will it lead to a job?

A study group is not a place that guarantees recruitment. Use it as a point of contact for learning about technology and people, and apply through the formal recruitment route. If you are still comparing ways to learn, see How to learn programming in Kyoto: self-study, schools, and study groups; for how to get involved from your first year at a company, see Five reasons new-graduate IT engineers should join a community.

---

If attending alone worries you

Most participants come alone.

The goal for a first visit is not to build a network. Any one of the following is enough.

• Get through the door
• Greet one person
• Ask one question
• Listen to the end
• Find out about the next event

If one of these works, the barrier to a second visit is lower.

---

If you are attending Miyako de IT

Miyako de IT is an IT engineer community based in Kyoto. Over 7 years it has run 153 events (as of 2026-08-10). The current number of events and connpass members is published on the activity statistics page. This article does not record fixed values.

The venue, day-of contact details, and upcoming dates can be checked on the following pages.

• Sessions you can attend: event listing
• Registration steps, venue, and day-of contact: first-time guide

As organizers, we do not approach first-time participants excessively. We run the sessions so that how much you talk remains your choice. If anything goes wrong, tell the organizer on the day.

---

Summary

What makes a first visit difficult is not technical knowledge but not knowing the flow of the day. These five points are enough.

1. Check who the event is for, the format, the cost, the venue, and the code of conduct on the event page

2. Register, and save the date, venue, and contact details

3. Prepare your registration confirmation and charger, plus a laptop if the format needs one

4. Arrive ten minutes before the start and say that it is your first time

5. Choose for yourself how much you talk and how long you stay

Sessions you can attend next are listed on the event listing.