A Senior Developer working mostly with PHP and JavaScript, with a bit of Python thrown in for good measure, all on Linux. My tooling is simple, it's GitLab and JetBrains where possible.
I write by assuming I have no audience - or that future me is my audience, so usually for fixing issues I've had. I've got other stuff thrown into the mix so if someone reads my blog, they can see there's more to me than just code.
My most popular posts are always ones where I've solved issues. Usually where documentation doesn't cover the subject matter too well.
Essentially, my good content is point 3 on your (excellent, I must say) blog post.
The stuff I have which would go under point 2, is the content I am trying to put together for a book. I'm just blocked on that by another project at the moment before I can continue.
I've bookmarked your post for those 4 ways to generate new ideas. I think it's going to be my go-to muse when I run low on ideas. I just hope the ideas I come up with don't turn into projects for me.
Thank you so much for taking the time to respond. I'll add your book to my to-read list. And the book publishing one. I really hope I need that in the not too distant future.
🇩🇴 I'm a Technical Program Manager and Content Strategist with an MSc in UXD. I help developers become better content creators and DevRel teams build robust content programs.
Thank you for sharing your process, workflow! And completely understand re: audience—if it helps, I wrote a blog post about different audiences if and when you're ready to define them.
Looking forward to seeing more of your writing!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I write by assuming I have no audience - or that future me is my audience, so usually for fixing issues I've had. I've got other stuff thrown into the mix so if someone reads my blog, they can see there's more to me than just code.
My most popular posts are always ones where I've solved issues. Usually where documentation doesn't cover the subject matter too well.
Essentially, my good content is point 3 on your (excellent, I must say) blog post.
The stuff I have which would go under point 2, is the content I am trying to put together for a book. I'm just blocked on that by another project at the moment before I can continue.
I've bookmarked your post for those 4 ways to generate new ideas. I think it's going to be my go-to muse when I run low on ideas. I just hope the ideas I come up with don't turn into projects for me.
Thank you so much for taking the time to respond. I'll add your book to my to-read list. And the book publishing one. I really hope I need that in the not too distant future.
Thank you for sharing your process, workflow! And completely understand re: audience—if it helps, I wrote a blog post about different audiences if and when you're ready to define them.
Looking forward to seeing more of your writing!