I really think the negativity in the comments here is overblown, and misdirected. The author has a totally reasonable set of requirements: React + TypeScript, writing posts in Markdown, small amounts of interactability, and static site generation. It may be an indictment of the JavaScript ecosystem and the current state of the web that nothing exists that can help the user accomplish this out of the box, but that doe…
The ideal tech stack for a personal developer blog in 2020
191–200 of 275 posts
Re: The ideal tech stack for a personal developer blog in 2020
#192Re: The ideal tech stack for a personal developer blog in 2020
#193Surely 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
#194Jesus Christ, the crap we're spending time on. https://www.theolognion.com/programmer-starts-a-blog-doesnt-...
Haven't been banned from GitHub yet but the "shunned by community" is coming together nicely. Also, to be fair, it's my second post.
Precisely. If it was your first post, I wouldn't have posted that. Also, please don't take it the wrong way, this is just humor. I appreciate you sharing knowledge with the world, it's something I haven't done in a long while so I respect that.
Re: The ideal tech stack for a personal developer blog in 2020
#195I'm quite surprised by the negativity here. If I was commissioned to make a custom blog site for someone, I would probably go down this route, and use a headless CMS to make it easier for others to generate content. But using plain markdown is not a bad choice if you can't be bothered with, or can't afford a server. With the stack described as I understand it, the front-end flexibility is preferable to what the likes…
Re: The ideal tech stack for a personal developer blog in 2020
#196Another aspect is that your blog should make you want to blog. The tech stack therefore mirrors your interests. It feels great to use tools built by _yourself_ for _yourself_. Doubly so if the stack is janky (rust / org-mode for me). The feeling that you've made something makes you want to invest more into it. To make sure the tools were worth making in the first place.
My stack for the blog is Org Mode compiled by Emacs into HTML, which then gets parsed by my Common Lisp static site generator. It's a weird setup, but it came to be because:
- The rest of the site, and the overall template, is generated straight from Common Lisp (using a much saner syntax for markup and styling than HTML/CSS),
- writing a parser for Org Mode for anything but the most basic features is a rather complicated endeavor, so it's better to let Emacs deal with it and then clean up the exported markup,
- I also imported posts from my old Wordpress blog, as HTML dumped from a database, so I had the tools to slice and dice DOM in my CL generator anyway.
I really hate how bad this design is. It needs rewriting from scratch into something designed closer to a build system, but that would take a lot of time, so I procrastinate on that endlessly. On the other hand, writing blog articles in Org Mode is super fun, so the frustrations cancel out with the benefits.
Re: The ideal tech stack for a personal developer blog in 2020
#197For a techy person, GitHub pages + markdown is all you need: https://quanticdev.com/articles/website-with-github-pages When you already know Git & GitHub, you get an all-in-one experience with your code & website side by side.
Glad someone already said this. And if you want something a bit more fancy, use a static site generator like Jekyll or Hugo.
I've heard good things about Hugo though (generally people seem to like it better than Jekyll), but I set up my site before it existed and I think Pages still only supports Jekyll.
Re: The ideal tech stack for a personal developer blog in 2020
#198Earlier quoted context omitted.
This meme is tedious. Typescript is here to stay. No question. React has been a thing now for what, six years? And it feels like 80% of FE job opening require React. And no major shift on the horizon.
Six years, roughly the time it took Angular to rise until version 2. Sorry for the sarcasm, I've been trying to learn web development for some months, starting with the basics (HTML, CSS, plain JS) and slowly adding more modern frameworks (Bootstrap, NodeJS, ...). The course is a few years old already and it feels like 80% of what I learn is now completely irrelevant. I just wonder how frontend developers keep up wit…
Leapfrog.
You learn the newest hotness right now (and hope you're right), evangelize it like a Southern Baptist at a tent revival, ride the wave for a few years until it's obvious the wheels are coming off in one of the three or four predictable ways, then pick up the new, new thing and pretend the past never happened.
It helps to change jobs every nine months or so; otherwise, someone will ask you to do something to that ancient archaic legacy stuff. Nobody wants that.
Re: The ideal tech stack for a personal developer blog in 2020
#199"Even something simple (like the email newsletter signup form at the bottom of this page) would have been hard to implement without React" the fuck ?
Re: The ideal tech stack for a personal developer blog in 2020
#200I'm perfectly happy using Hugo + git hooks. It's easy as
1. Write a post in markdown
2. Commit and push
3. A post-commit hook runs hugo. Refresh your page and the post is live.
The friction to create a new post needs to be as low as possible. I can't get it any lower than this.
It's dead simple to set up too - https://blog.nindalf.com/posts/setting-up-this-blog/