Is it worth posting small articles on technical issues on Habr?

Question

Habr

Actually, at work, sometimes you come across all sorts of interesting features of the language / compiler / libraries and there is a desire to share. But you probably won’t write a fundamental article from this, especially looking at the solid works of some authors, it’s even somehow embarrassing to post this. Although personally it would be more interesting for me to read such things than news, smartphone reviews and discussions about which of the corporations is the most innovative.

Therefore, I ask - is it worth posting such articles or is it better to start a personal blog for this on one of the thematic platforms?

Answer 1

If it’s not enough for a full-fledged article, maybe it’s worth saving up material and then posting a large article?

Answer 2

If you feel that some issue under consideration is a “killer feature”, firstly little known, and secondly, allowing you to save someone a lot of time and effort, then yes, it might be worth posting. By the way, the best criterion for substantiating the sufficiency of the article material is your personal experience. “How I saved a week using the xxxx feature” or “How I reduced the load on the server by a factor of three by using yyyyy.”
If most of these features do not give such an “immediate super effect”, then it is better, as IllariPosselt said above, to post the article right away. But at the same time, I would add that it’s much more interesting not just a “hodgepodge article”, but something like a “thematic collection” or a “book of short recipes”.
Agree, it would be much more pleasant and practical for you to read the article “Practical use of gcc extensions for code refactoring”, rather than just a bunch of disparate pieces “Little-known features of gcc” which, firstly, who had the time, already smoked it in the manuals, and secondly, even those who smoked hardly come to mind where to stick it.
That is, the reader needs information not about the fact that you subtracted a chip in the docks that no one subtracted, but a valuable story about your even small but successful / failed experience of using something. It's really interesting to read (information passed through your personal experience).

Answer 3

Be very careful. They can be extinguished immediately. Very good articles here. Anything a little lower can lead to disaster, even if you do it with good intentions, and even if it can help a lot of people. I've stumbled on this a couple of times already, I don't post anymore.

Answer 4

In fact, in a bunch of what is fasting right now - such as copyright wars, corporate blogs with advertising and other IT-related topics (we are sliding into cnews, God forbid), any article about something really technical, IMHO, will be good.
The only thing is that there are a lot of people who only comment, and they may not like it. But you try - they won’t remove much, but you will do good for the rest.

Answer 5

IMHO, that would be really cool. But the notes must be of good quality.
It would be cool to even highlight a separate type, not articles, but notes.
For example, every day I solve some useful tasks for myself.
To solve it, I kill from half an hour to several hours of time googling the problem.
If you make an article out of this, then it turns out little. Sometimes it works out enough.
I would be happy with such small articles and would be happy to upvote them.
Having such an article will help someone save a day of work.
As mentioned above, they love fundamentality in tasks.
On the other hand, someone spends one evening on an article, and someone a couple of months, and the effect is not much different.
I decided this for myself: if I am going to post a small fact, then I try to reveal it well, with links, abstracts, etc. Having described everything, you will get a good, solid article of not large size.
I tried it - it really worked.
If the fact has not grown to an article, then I will publish it on my blog, it is also useful. Someone will find and read.

Answer 6

IMHO - no. Small things are just notes for yourself. On Habré, I want to read something sensible and extensive, and not just another report - I know what nslookup is or how to get a stack trace using twidle.sh. Amateurish advice is never needed :)
If this is a related topic, then as an option, you can try to make it all one big advice.