A personal brand for a developer is one specific thing you are known for, backed by public work, repeated consistently in one place until people associate the topic with your name. It is not a logo, a colour scheme or a content calendar. It is "the person who explains Postgres indexes clearly" or "the person shipping a Rust CLI in public".
1. Choose one thing
Pick a topic narrow enough that you can be a top voice in it and broad enough to sustain a year of posts: "testing Next.js apps", "Flutter performance", "building CLIs in Go", "learning ML from a web background". Specific beats broad; you can widen later. The test: could someone describe you in six words?
2. One home base, consistent everywhere
Use the same name, handle, photo and one-line bio on every platform so people who see you in two places connect the dots. Pick a home base where your work lives — a DEVAE profile, a personal site, GitHub — and point everything else at it. Your bio should say the topic and what you want (a job, collaborators, clients).
3. One artifact a week
Brands are built from artifacts, not opinions. Each week publish something people can use: a snippet with an explanation, a small tool, a benchmark, a "here is what broke and how I fixed it" post. Include the code. A year of that is 52 pieces of evidence that you know your topic.
4. Make a few things reusable
Among your weekly posts, some will resonate. Turn those into things people bookmark and share: a checklist, a starter template, a free tool, a cheat sheet. Reusable artifacts keep working while you sleep and become the links other people cite when they mention you.
5. Show up in person, sometimes
Text builds recognition; voice builds trust. Host a live room on your topic once a month, give a short talk at a meetup, record a five-minute demo. You do not need production quality; you need to be recognisably the same person as the posts.
What not to do
- Post takes without work behind them. Hot takes get attention and lose trust.
- Chase every platform. One home base plus one distribution channel is plenty.
- Fake numbers or borrowed credibility. Developers check.
Measuring it
Ignore follower counts. Track three things: are people asking you about your topic, are people sharing your artifacts, and are opportunities (jobs, collaborators, clients) arriving that mention your work. Those move after six to twelve months of the weekly habit, rarely sooner.
A worked example
A backend developer decides to be "the person who explains Postgres performance to application developers". She sets her bio to that sentence everywhere. Week one: a post on why a query got slow after adding a column, with EXPLAIN output. Week three: a small script that finds unused indexes. Week eight: a checklist, "ten things to check before adding an index", which people start linking to. Month four: a monthly room where she looks at one attendee's slow query live. Month nine: a company invites her to give an internal talk and, later, to interview. The brand was a topic, a habit and a checklist.
Questions people ask
**Do I need a blog?** No. A profile where your posts and artifacts live is enough. A blog helps with search traffic once you have twenty or more pieces; before that, distribution matters more than a domain.
**What if my topic changes?** That is normal. Narrow topics are stepping stones; the audience follows a person who explains things well, not a keyword. Announce the shift and keep the habit.
**How do I avoid sounding like a marketer?** Only publish things with work behind them, and write the way you would explain it to a colleague. Developers can tell the difference within a sentence.
