What Workshops Taught Me About Learning, Mentorship, and Community

When I started getting involved in workshops and community events, I thought my responsibility was mainly to teach technology.

Explain the concept. Show an example. Let people write some code. Answer questions. Move to the next topic.

But after spending more time mentoring and working with different groups of developers, I realized that teaching technology is only a small part of the job.

People learn differently

One of the first things you notice when leading a workshop is that everyone arrives with a different background.

Someone might already understand the fundamentals but struggle with a particular framework. Someone else might be completely new but surprisingly comfortable experimenting. Another person may understand the technical concept but hesitate to ask questions because they are worried that their question is too simple.

That makes teaching a very different challenge from simply preparing slides.

You are not only explaining a concept. You are trying to create an environment where people can understand it in their own way.

The best workshops are not lectures

I have gradually become more convinced that people learn technology best when they actually build something.

A slide explaining an API can be useful. A diagram showing how authentication works can be useful. But there is a different kind of understanding that happens when someone writes the request themselves, gets an error, searches for the reason, fixes it, and finally sees the expected response.

That moment of “Oh, now I understand” is difficult to create through theory alone.

Questions are part of learning

One of the biggest things I learned from mentoring is that a question is not necessarily a sign that someone is behind.

Sometimes it means they are thinking deeply about the problem.

A healthy learning environment should make people comfortable saying:

• “I don't understand this.”
• “Why are we doing it this way?”
• “What happens if we change this?”
• “I tried this, but it didn't work.”

Those questions often lead to better discussions than simply following the prepared material.

Mentoring is also about confidence

Technical skills matter, but confidence matters too.

I have seen developers understand a concept but hesitate to write the code because they are afraid of making a mistake. That is something a good mentor should actively work against.

Making mistakes is not an interruption to learning. Making mistakes is part of learning.

Instead of immediately fixing someone's code, sometimes it is more useful to ask another question and let them discover the answer themselves. The goal is not just to solve today's problem. The goal is to help someone become better at solving the next problem without you.

Community makes learning sustainable

Workshops might only last a few hours or a few days, but the relationships created around them can last much longer.

When developers share what they know, help each other debug problems, talk about their experiences, and celebrate small wins, learning becomes a community activity instead of an individual struggle.

That is one of the things I value most about being involved in the developer community.

What I take away from every workshop

Every workshop has taught me something different. Sometimes it is a better way to explain a technical concept. Sometimes it is a reminder to slow down. Sometimes it is simply learning that the problem I thought would take five minutes actually needs thirty.

But the biggest lesson has been simple:

Teaching is not about proving how much you know. It is about helping someone else discover what they are capable of learning.

That mindset has changed the way I approach mentoring, workshops, and even everyday collaboration with other developers.

And honestly, some of the best lessons I have learned while teaching were lessons I did not expect to learn at all.