Things that no one tells you properly
When you hear the term developer branding,
most people have these thoughts first.
"Should I start a blog?"
"Should I work hard on social media?"
"Should I start a YouTube channel?"
"But... do I really have to?"
It seems like something you should do,
but you don't really know why you should,
and when you actually try to start, it feels uncomfortable somewhere.
Stories about increasing followers,
formulas for increasing views,
methods to create virality overflow,
but strangely, after seeing all that, you feel more empty.
"So... what should I do?"
If you have ever stopped at this question,
this post is for you.
The reason branding is difficult,
It's not because you lack something
Many developers find branding difficult.
However, the reason is not because of lack of skills,
or inability to write.
The problem is because the question itself is wrong.
We usually ask like this.
"How can I become famous?"
This question naturally
leads us into the world of means.
- Where should I write?
- Which platform is advantageous?
- What format will spread well?
But this question
lacks the most important thing.
"Why should people remember me?"
If you have never seriously asked this question,
no matter how much you write,
no matter how hard you work on recording,
branding will always feel daunting.
This is not a marketing story
I want to say this in advance.
This series
does not teach you how to quickly increase followers,
explode views,
or how to do branding well.
Instead, it talks about these.
- Why do some developers remain memorable for a long time?
- Why do people keep coming back to some people's writing?
- What remains even as technology changes?
- And what is the essence of developer branding?
The core of this series is simple.
Developer branding
is not a process of becoming a 'skilled person,'
but a process of becoming a 'person who leaves thoughts.'
Why this story is needed now
We are living in a strange era.
The lifespan of technology is getting shorter,
frameworks keep changing,
AI shatters yesterday's standards.
The vague anxiety that
the skills we have diligently accumulated
may become ordinary in a single moment.
So more developers
ponder on having "something of their own."
However, this pondering often
flows in the wrong direction.
Trying to increase exposure,
imitating the correct answers,
copying the format of those who are already successful.
And at some point, you think this.
"This doesn't seem like me..."
This series
restarts from that point.
What this series covers,
and what it doesn't
This series
does not say, "Do developer branding like this."
Instead, it asks these questions together.
- What problems have I repeatedly faced?
- How do I perceive those problems?
- What criteria have I used for my choices?
- How can I leave traces of this thinking?
After reading this series to the end,
you may not become more famous.
But instead, this change will occur.
- You will know what matters to write about,
- You will be clear on what you don't need to write about,
- Instead of others' ways,
you will be able to record based on your own standards.
In the next post,
Let's start from the questions again
In the next post,
it talks about the most common wrong question asked in developer branding,
and how to redefine that question.
"What should I do to do developer branding?"
Is this question really the right one?
From here,
the series starts slowly,
but firmly.