I have a personal site and it is the closest thing I could see to me doing a blog. Basically it's a dumping ground for projects I want to do, I plan on doing a

I have a personal site and it is the closest thing I could see to me doing a blog. Basically it's a dumping ground for projects I want to do, I plan on doing a little write up for each one. Right now there's only one project in there but I'm working on another much bigger one. When it is done I'll do one high quality write up of how it works. The ratio of blog:code imo should be low. If you want to do a project really well, focus on writing the code. If you're proud of it and did a good job, do a little write up. Go for quality over quantity, anybody can make "how to get started with React and Typescript" or "How to add TailwindCSS to a Vue project" because it's been done 100 times. Unless you're working on TailwindCSS, this isn't going to impress anyone. Twitter feels fake. It's like it's a bunch of used-car-salesman-like software developers trying to sell you on web3, or crypto, or their course to teach you how to code like they supposedly do. The only places I think it makes sense to have any sort of presence might be GitHub, or StackOverflow. On GitHub you might have a project you've done that others find useful, something pretty niche. This happened to me for a project I had barely even started, and a recruiter wound up reaching out over it. This project was on npm and GitHub, it had like zero downloads but because of the niche that it was in, I was one of the only people with a project like this. I could imagine if you get 50 stars on a project any employer will look at that and be impressed. Tl;dr, do what you like to do. If you're really proud of it and want to show it off, do a write up. Don't churn out easy crap just to do a blog post every week about it.