1. Choose a subject

I think with can distinguish subjects in 3 categories based on the “evolution a developer come through time”:

Discover → Master →️ Build and share your vision

— — —

A subject you love, sharing a discovery

You don’t have to master a subject to present it, you just have to love it first!

This definition is particularly important when starting writing/presenting and essentially helps breaking the impostor syndrome.

You don’t have to be a master or have super presentation skills to present a subject.

What matters is to share something that matters to you.

Sharing some issues that you encountered, projects you worked on, things that you learned is always interesting.

Keep in mind that, all — constructive — feedback are valuable.

Example of subjects:

“How to build a website with Gatsby”

“How I learned programming in 2 months”

— — —

A subject you want to master, teaching or provide feedback

You only master something when you can explain it in simple words

Making a presentation on a subject you want to master is the best way to achieve one’s ends.

Simply because mastering a subject is achieved when you can explain it in simple words — which is hard.

Teaching, mentoring is the best way to master a subject

I really enjoy doing “vulgarization” presentation and challenge myself in making something simple to learn.

This is a wonderful exercise.

Example of subjects:

“Set-up a data pipeline with Google Cloud”

“Learning TypeScript: the basics”

— — —

A subject you master, sharing an idea or a vision

Get people to understand and join your vision

You are building a library, framework, tool or community?

Then you may want to share a vision.

This is also the case if you want to advocate for a technology you love 💙

Get people to understand and join your vision is a hard BUT funny exercise

This is definitely a “frightening” exercise but a wonderful journey to express its view and accepting feedback.

Example of subjects: