I write about infrastructure and AI (subscribe to get emails once a few months https://sdan.io/subscribe).
In particular I write posts about setting up your own servers (one about hosting your website from your Raspberry Pi at home and WireGuard is coming up) and about handling massive loads as well as interesting AI topics such as how Transformers work or new and exciting AI papers.
As to why you should read it? I have always tried to show warts and all when it comes to anything technical I post. This includes where I screw up, make mistakes or work with false information. Mostly because I keep a record as I do things and don’t want to sanitise what I did and also because most posts paint a perfect picture which is usually far from reality.
Great thread! I sometimes wish there was a variant of Hacker News that only had blog posts written by individuals. Mine is https://tkainrad.dev I think you should read my blog because I invest a lot of effort into my posts. Not sure why I do that, as there is no reward except growing Google Analytics numbers. My three most successful articles have been - Managing my personal knowledge base: https://tkainrad.dev/posts…
> I sometimes wish there was a variant of Hacker News that only had blog posts written by individuals
Basically I'm taking all the links published into HN and I'm filtering the domains which are news domains or appear too frequently, but that is still a lot of links, so I'm not calling it a success yet
I mainly write about frontend, Node.js, modern javascript ecosystem tooling, productivity and occasional book reviews that I found interesting (not necessarily software related).
No particular reason, but I started building websites in the late 90s and am now heading up the engineering department in our scale-up (60+ people w/ 25+ engineers).
https://mrkaran.dev/ This is my personal blog where I pen down my thoughts on Containers, DNS, bits of Devops etc. I've been a self learner since the time I started programming and I feel penning down thoughts and reaching to a wider audience makes me learn those concepts even better. If you enjoy understanding concepts using an ELI5 approach, consider checking out my blog :)
https://fromtoschool.com - It's a little rough around the edges, but I'm in the process of testing out a new, faster way of teaching programming. Instead of assuming no similar knowledge when teaching a new language or framework, we try to leverage the knowledge of similar languages and frameworks that you already have to build the new knowledge structure.
My goal is to talk about original topics in which it is difficult to find information whatever the topic: startups, dating, nutrition , diy, travelling as a dev