Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The ideal tech stack for a personal developer blog in 2020

vriad.com

Post reply on HN
Print view View original

21–30 of 275 posts

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

#21

Post by nallerooth »

DJHenk wrote: post #10

A personal blog should be whatever the author wants it to be of course, and a developer should play with whatever technology he/she wants. But as a backend developer, I don't want any Javascript on my site, because I hate writing it and I don't like browsing it. These statements indicate to me that this "ideal tech stack" is rather personal to the author: > I want to build the site in React and TypeScript > I don't w…

Hugo is awesome! (Apart from the Go templates, before you get the hang of them..)

A year or two back, shouting REACT at everything and everyone could actually land you a new job, but now... I'd just stick to Hugo and focus on my content if I wanted to impress any recruiters.

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

#22

Post by reacharavindh »

Hugo (static site generator) + a theme (Ananke - based on Tachyons CSS) + Markdown for content. Hosted on a CentOS 8 VPS on GCP.

https://aravindh.net

No JS tinkering. Just simple HTML and CSS to customise the theme for my taste. Not as simple as editing raw HTML with vi, but I'm good with it.

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

#23

Post by duxup »

encom wrote: post #6

Here's my stack: I write .html files in GNU Nano, and serve them with Apache. I've done that for about 20 years (with varying editors and servers), and I don't see why it needs to be any more complicated putting words on the internet. Yes yes, old man yells at cloud etc, but I'm a strong believer in "less is more".

Everyone's "less" is different I think.

Someone has a workflow that they know like the back of their hand and has low friction... that's less. Good for them.

Folks get worked up on developer choices so much, if it's a blog and it's not doing something seriously bad ... it's their site and their call IMO.

When I was into photography one of the biggest lessons I learned was you use the tool... you're going to use a lot. It doesn't matter what it is as much as the tool should allow you to do the thing and not get in the way because you think you "should" be using something else.

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

#24

Post by MoOmer »

9nGQluzmnq3M wrote: post #9

Creating your own stack for your personal blog seems to be the modern-day equivalent to creating your own programming language: it's a huge time sink with virtually no sane justification, yet developers are drawn to it like moths to a flame.

Sometimes following rabbit holes is fun for personal projects - not every project is measured strictly by utility.

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

#25

Post by jasode »

clarry wrote: post #3

> I worry that many developers (maybe even you, dear reader) are settling for suboptimal, restrictive static-site generators that place limits on the interactivity and flexibility of your website. I wonder what sort of interactivity you want on your text? > This degrades page load speeds and user experience, which accordingly degrades your rankings on Google. Instead I want every page of my site to be pre-rendered to…

>I wonder what sort of interactivity you want on your text?

In case you glossed over it, I think he said it in his post:

"But down the road, I may want to build a page that contains an interactive visualization, a filterable table, or a demo of a React component I'm open-sourcing."

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

#26

Post by nick_meister »

nallerooth wrote: post #21
DJHenk wrote: post #10

A personal blog should be whatever the author wants it to be of course, and a developer should play with whatever technology he/she wants. But as a backend developer, I don't want any Javascript on my site, because I hate writing it and I don't like browsing it. These statements indicate to me that this "ideal tech stack" is rather personal to the author: > I want to build the site in React and TypeScript > I don't w…

Hugo is awesome! (Apart from the Go templates, before you get the hang of them..) A year or two back, shouting REACT at everything and everyone could actually land you a new job, but now... I'd just stick to Hugo and focus on my content if I wanted to impress any recruiters.

Hugo is great but check out Zola, it is basically like Hugo but with better templates IMO.

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

#27

Post by Cthulhu_ »

encom wrote: post #6

Here's my stack: I write .html files in GNU Nano, and serve them with Apache. I've done that for about 20 years (with varying editors and servers), and I don't see why it needs to be any more complicated putting words on the internet. Yes yes, old man yells at cloud etc, but I'm a strong believer in "less is more".

There's nothing wrong with that approach tbh; when you think about it, the only reason to make a dynamic website is to prevent duplication, things like headers, menus, styles, etc. But there's ways around that, like frames.

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

#28

Post by Amorymeltzer »

DJHenk wrote: post #10

A personal blog should be whatever the author wants it to be of course, and a developer should play with whatever technology he/she wants. But as a backend developer, I don't want any Javascript on my site, because I hate writing it and I don't like browsing it. These statements indicate to me that this "ideal tech stack" is rather personal to the author: > I want to build the site in React and TypeScript > I don't w…

The ideal tech stack for a personal blog is whatever the person wants to maintain, update, and, most importantly, use.

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

#30

Post by jamesu »

My main problem with blogging is not really the tech stack itself, but rather getting into the flow to consistently write and complete stuff. Every slip-up which happens on the way from brain to page drastically reduces the chance something will get published.

e.g. troubleshooting a broken deployment script because something broke after an update? -> no post. needing to manually manipulate images? -> no post. page rebuilding taking too long? -> no post.

Post reply on HN