Live data from Hacker News

The ideal tech stack for a personal developer blog in 2020

vriad.com

11–20 of 275 posts

Re: The ideal tech stack for a personal developer blog in 2020

#11
I’m sorry, but this is ridiculous for a static site. React and Typescript with embedded markdown?

This problem has been solved a thousand times over with much simpler tooling.

> I literally have zero memory of how we used to build forms in the pre-React times.

:(

Re: The ideal tech stack for a personal developer blog in 2020

#13
Surely this is meant as satire, the title is clearly tongue-in-cheek.

I’d worry that some less experienced folks might take it at face value, rather than as a salient warning about the dangers of grossly over-engineering for no discernible benefit.

Re: The ideal tech stack for a personal developer blog in 2020

#16
post #12
post #4

Why reinvent the wheel? Use Wordpress/Ghost etc

Because writing your own blog engine is a good way to learn various web technologies that you haven't had a chance to use.

I agree, but then really you're not interested in creating blog content per-se, but in exercising your engineering skills. I think it's important to be honest about that intention both with your audience and yourself when writing articles like this.

Re: The ideal tech stack for a personal developer blog in 2020

#18
post #11

I’m sorry, but this is ridiculous for a static site. React and Typescript with embedded markdown? This problem has been solved a thousand times over with much simpler tooling. > I literally have zero memory of how we used to build forms in the pre-React times. :(

I cane here to say this. In fact, I’m wondering now if the site is actually satire!

Re: The ideal tech stack for a personal developer blog in 2020

#20
post #5

Personally I work in tech all day, I want my blog to be as simple as possible and to focus just on my writing. Still using Jekyll.

I use Jekyll too. It just works and I'd happily use it on future projects.

Even with ~300 posts and ~100 drafts it only takes 2 seconds to see auto-reloaded updates when I'm actively writing. That's within WSL 1 too (room for speed improvements are there with WSL 2).

It also has nice plugins to process SCSS and bundle your CSS / JS, along with md5 tagging all static files for cache busting without having to use Webpack or do anything complicated. You just reference them using a specific plugin's template tag. But at the same time you can choose to use Webpack if you'd like.

I'm not sure why the author mentioned Jekyll is too restrictive. You can write plugins to do some pretty custom things. Like, I wrote a few lines of Ruby to parse out time stamps from a list to make them clickable links so that I can jump to that position in a custom audio player, very similar to how clickable time stamps work on Youtube. You can pretty much do anything.

Post reply on HN