I started teaching what I’m learning

I made my first post.

Not a portfolio update.
Not another project.
Not another piece of code sitting quietly on GitHub.

This time, I made something to teach.

And with that, I think I’ve officially started my journey as an education content creator.

---

Why content?

I've always liked learning things and then trying to understand why they work.

But learning something and explaining it are two very different things.

When you have to explain a concept to someone else, you quickly find the gaps in your own understanding. You can't hide behind "I kind of get it."

You either understand it well enough to explain it—or you go back and learn it properly.

That is what I want this journey to be about.

Learn → Build → Explain → Repeat.

Not pretending to know everything.

Just learning in public.

---

Starting with Swift

For my first piece of content, I decided to start with something I'm currently learning myself:

Swift.

And instead of making a typical introduction to the language, I wanted to make something simple enough that someone scrolling through Instagram might actually stop for it.

So I played with the word itself.

A car.

A bird.

Something fast.

And finally—

Swift, the programming language.

That became my first carousel.

It felt like a small thing, but it was also the first time I looked at something I was learning and thought:

"How can I explain this in a way that someone would actually enjoy consuming?"

That question is probably going to shape a lot of what I make from here.

---

I'm not an expert

This part matters.

I'm not starting this account because I think I've figured everything out.

Quite the opposite.

I'm starting it because I'm still figuring things out.

I'll be learning Swift.
I'll be learning iOS development.
I'll be building projects.
I'll make mistakes.
I'll probably rewrite things I thought I understood.

And I'll share the process.

If something takes me three hours to understand, maybe I can explain it in three minutes.

If I find a resource that genuinely helps, I'll share it.

If I build something interesting, I'll show it.

And if I get something wrong, I'll correct it.

---

What I want to create

I don't want the account to become another collection of generic:

"10 programming languages you MUST learn in 2026"

posts.

I'd rather make things that I would have wanted to see when I was starting.

Things like:

• Simple explanations of programming concepts
• Swift and iOS development
• Useful resources for beginners
• Projects and things I'm building
• Lessons from learning
• Mistakes I've made
• Tools that actually help
• And occasionally, the chaotic reality of being a CSE student

Basically, education without making it feel like a lecture.

---

Learning in public

There's something interesting about putting your learning process online.

Once you publish something, you can't just say "I'll learn it someday."

There's now a small commitment attached to it.

Someone might be watching.

Someone might learn from it.

Someone might even point out something you got wrong.

And that's okay.

I'd rather be someone who is actively learning and sharing than someone waiting until they feel qualified enough to start.

---

This is only the beginning

The first post is out.

The account exists.

The journey has officially started.

Now comes the harder part:

showing up consistently.

I don't know exactly where this will lead.

Maybe I'll end up building iOS apps I never thought I could build.

Maybe I'll discover that teaching is something I genuinely enjoy.

Maybe I'll completely change direction six months from now.

That's part of the point.

I want to document the process rather than pretend I already know the ending.

So if you're interested in Swift, iOS development, programming, projects, or simply watching a CSE student figure things out in public, stick around.

I'm just getting started.

Learn. Build. Share. Repeat. 🚀

---

I'm sharing the journey on Instagram:
@miserymightflourish

If you're starting your own learning journey too, maybe we can figure it out together.