3 ms·

yeah good point, I was a bit worried that this approach is frowned up by the community, but I will try it out. thank you for your suggestion.

gus_massa 8mo ago
There are not hard rules, but my recommendation is to not post your own stuff more than one a week. (I prefer once a month but as I say there is no hard rule. I like longer articles, and it's difficult to write them unless the blog is your full time job.) Usually technical articles with a few relevant photos/graphics are the best. Try to not use AI, because there will be a lot of complains in the comments. Perhaps only to fix orthography and grammar errors, or a few style problems. --- https://littlecodingthings.com/simple-ways-to-create-a-css-overlay-effect/ https://littlecodingthings.com/simple-ways-to-create-a-css-o... May be a good post for HN, but who knows, my css knowledge is very low. https://littlecodingthings.com/docker-docker-compose-commands-i-keep-forgetting-cheat-sheet/ https://littlecodingthings.com/docker-docker-compose-command... All the examples are one line. It's probably too close to a manual or tutorial. I don't expect it to get traction, but who knows, my docker knowledge is very low.
- lilcodingthings 8mo ago
  Thanks for taking the time to look at our articles! That's really helpful feedback. I'll start with the more technical and in-depth posts, as well as ones that describe personal paths and experiences, and see how it goes based on people's feedback The once-a-month approach could also be a good starting point for me. I'm trying to blog while working full time and, as you said, it is hard indeed. Hopefully, as time goes by — and fingers crossed, by making the right decisions, people will start reading, Google will start showing us in results, and we'll stop feeling as if we're writing for ourselves only. Although I don't feel bad writing just for myself, it would be nice to know that someone else may read what I'm sharing. :)

gus_massa 8mo ago

There are not hard rules, but my recommendation is to not post your own stuff more than one a week. (I prefer once a month but as I say there is no hard rule. I like longer articles, and it's difficult to write them unless the blog is your full time job.) Usually technical articles with a few relevant photos/graphics are the best. Try to not use AI, because there will be a lot of complains in the comments. Perhaps only to fix orthography and grammar errors, or a few style problems. --- https://littlecodingthings.com/simple-ways-to-create-a-css-overlay-effect/ https://littlecodingthings.com/simple-ways-to-create-a-css-o... May be a good post for HN, but who knows, my css knowledge is very low. https://littlecodingthings.com/docker-docker-compose-commands-i-keep-forgetting-cheat-sheet/ https://littlecodingthings.com/docker-docker-compose-command... All the examples are one line. It's probably too close to a manual or tutorial. I don't expect it to get traction, but who knows, my docker knowledge is very low.

lilcodingthings 8mo ago
Thanks for taking the time to look at our articles! That's really helpful feedback. I'll start with the more technical and in-depth posts, as well as ones that describe personal paths and experiences, and see how it goes based on people's feedback The once-a-month approach could also be a good starting point for me. I'm trying to blog while working full time and, as you said, it is hard indeed. Hopefully, as time goes by — and fingers crossed, by making the right decisions, people will start reading, Google will start showing us in results, and we'll stop feeling as if we're writing for ourselves only. Although I don't feel bad writing just for myself, it would be nice to know that someone else may read what I'm sharing. :)