Remember when maintaining a blog was THE way to build your developer brand?
When thoughtful technical writing could lead to speaking gigs, job offers, and meaningful connections?
But in 2025, the landscape has shifted dramatically:
- LinkedIn's algorithmic feed heavily favors short-form "broetry" over substantive technical content
- Twitter/X has become a battleground of AI-generated hot takes
- Medium is drowning in SEO-optimized tutorials that all say the same thing
Unless you're already established or willing to play the AI-SEO game, it feels impossible to build genuine readership for a technical blog in 2025.
Yet part of me wonders if I'm just being cynical. Maybe there's still value in writing for its own sake? Or perhaps there are distribution channels I haven't considered?
For those still maintaining personal blogs: How do you find readers? Where do you share your content? And most importantly - why do you keep writing?
Plain HTML only with a single page and hyperlinks into a specific article. Very basic styling and no JS, don't even necessarily want to have a css file, just inline in the header. Very likely just setting font family to sans and be done with it.
I sometimes play with esoteric stuff that might be fun to blog about.
Stuff I've recently played with and deployed on internal tools was a SPA built using just js. No react etc. Basic router which makes use of the history API and use the observer pattern with MVC for "components" but generally those are just entire pages.
And a "component" or "page" is just a function that takes a router (could extend it to include props I guess ala react) and returns a Promise<HTMLElement>.
All the router does is looks up the function in a map and calls it replacing the top level div on the page with the returned HTMLElement.
All external loading happens at the page level and not at component level and it's simple enough.
There's a point where you need a bigger framework like react but I find it a pain to include react and npm etc when all I need is some very simple pages with some dynamic content.
A writeup on the pros and cons etc might be fun.
The next thing I'm playing with is possibly something like a job system(well promises in JS would work fine) and using that for state updates. Think goroutines and channels. There are some existing articles on that but they reference very old libraries and I feel there might be no reason to use a library or even channels on the web for that concept.
reply