I write this blog partly so employers, collaborators, and researchers can see how I think. Writing is one of the cheapest ways a developer can make their skills visible.
Why it works
- Proof of skill that anyone can check
- Proof of communication, which matters even more for remote roles
- Search traffic that compounds over years
- Conversation starters for interviews and outreach
- Clarity for you: writing forces understanding
What to write
- Problems you've solved, especially the ones you searched for and couldn't find good answers to
- Explanations of concepts in your niche (example: What Are Embeddings?)
- Decisions and trade-offs from real projects
- Case studies (template)
- Lessons and mistakes (HairOver mistakes)
A simple post structure
- Title with the search query, e.g. "How to Fix INP in React Apps", not "Thoughts on Performance"
- The answer early, in the first paragraph
- Steps or sections with clear headings
- Code or examples
- Related links to your other posts
Check length with a Word Counter, but write as long as the topic needs, not to a number.
Own your domain
Platforms rise and fall. Your own domain keeps the value. A good setup:
- Publish on your site (this one runs Next.js + MDX)
- Cross-post to platforms with a canonical URL back to your site
- Share on LinkedIn and X with a short summary
SEO basics that matter
- One clear primary keyword per post, in the title and first paragraph
- A descriptive URL slug
- Internal links between related posts
- Honest, specific content that actually answers the question
- Fast pages (Next.js performance)
Consistency
Pick a cadence you can keep, like two posts a month. Keep a list of ideas in a note. When something annoys you at work, that's a post.