I don't know where the joke is from but if there is one about how engineers set up a blog it would go like this.
Goes to Medium, Wordpress, or somewhere else, starts writing and clicks publish.
1. Set up ReactJS for the front end
2. Set up a build system for automated deployments
3. Sets up MongoDB to store the articles they'll be writing
4. Sets up the backend to serve up the various articles
5. Builds an integration for Wordpress that enables Wordpress to pull and push (make sure both ways) to the MongoDB system that's storing the newsletters
6. Sets up all the integrations required for SEO
7. Sets up the integration testing framework
8. Write an article
9. Clicks publish
Setting that up is just a different version of doing points 2 through 7 in the grandparent post's list...
(Though your direct parent post also left out the 30 years of "getting emacs set up just the way I like it"...)
Look at how much work it took you to get to 8 & 9.
Is it worth throwing away hours of work and getting 1/10 the engagement you could've gotten, in a rush to cross off 9? Of course not.
Thinking about your blog topics - what's going to engage your audience, what's going to bring it in front of more viewers - should be something you think deeply about.
Just consider elevating it beyond "what do I find interesting in this moment, at this second." Think - hard - with some Google research to back it up, and yes, maybe some tedious cross-checking of similar articles - What would people like to read, and what would get you a good return on the time you've sunk into this?
It's sad to spend 5 hours on something 4 people read, when 6 hours could've easily made it 200.
In either case, I have all the time in the world. I'm not maximizing for engagement. I'm just having fun, and I'm learning something along the way.
People make chairs with expensive tools in expensive workshops. They could just drive out and buy one, but they're not trying to disrupt the sitting industry. They just enjoy the process of making chairs.
1. Write article in notepad
2. Create blog repo in github
3. Create issue and paste article
01.2017 I simply signed up for dev.to and started writing.
Best decision ever.
We built a tool to aggregate contents from various sources (e.g. news, videos, reddit posts etc) and then put them on a simple website (something similar to HN or Reddit).
The website then has a newsletter subscription feature and then latest / popular contents will be delivered.
My inbox is a queue.. but I read news as a stack, only the latest, discard stuff I don't make it to.
Building all the tech to aggregate the data is fun. Putting the newsletter together every day, less so. Newsletter fatigue is a real thing. This was super inspiring though, thanks for sharing!
it's a sensible idea.
I think i have a lot of side projects that with some effort might become something
people would pay for (obvious thing is a auto delete flag like outlook rules in gmail)
is this not already heavily competitive? have you tried getrewardful.com?
My experience with high traffic sites is that most of the things that helped our SEO were things I’d consider basic hygiene along with generally better than average content. There’s not much wordpress can do for that, in fact it will actively hurt you with it’s slow page generation if you don’t have a good caching layer.