Should I write an article about developing your own pro audio software solution?

Question

Habr

I really want to publish an article in which I could talk about the development of a software package for mixing, mixing, playout and automation in the field of audio. The only alarming thing is that the final release is still very far away and in fact now there is no way to give the reader either the source or the "exe". There are only ideas, plans and a working draft. The most I can give is a few screenshots to better capture the main idea. Yes, and it's scary, as always, to reveal your own "product" in the sense that it may immediately seem like an advertisement.

Of course, the question looks a little strange - there is nothing, but I want to tell you. But since the project in terms of its audience is no longer drawn to something homely and is focused, incl. for professionals in their field, it is very important for me to get feedback. Suddenly, some features are far-fetched, others have received too little attention, and I generally unforgivably forgot about some critical functions.

So that the article does not seem like some kind of note in the microblog, of course, you need to write more technical text. In this regard, I can reveal the problem of real-time audio processing, talk about my way of solving it, what and how the specific components of the project are implemented.

Does it make sense to publish an article like this? Does the Habr audience need such an article? Which hub to choose? What's the best way to avoid falling into empty advertising?

Answer 1

What are the problems, write in a draft, at the end of the project or bringing it to some intermediate result, you will launch a series of publications 'how I spent the summer', wondering whether it is worth writing or not - it's stupid if you want to write!
If the goal of the project is not just to collect likes, but to get feedback, then it’s definitely worth writing. And if you get a negative response - it will also be a useful result, it is worth considering it in this vein.

Answer 2

Write. The emphasis can be placed not on the software being developed, but on the problems in this area, the approaches and algorithms you used to solve them, how and why, possibly with examples from real code. It will be interesting to read.

Answer 3

Ideas are worth nothing. And plans too.
This is an axiom, the adequacy of which is easy to verify with the help of Google.
On Habré, you need to write something that may be interesting to at least some part of the audience of IT people. You choose this audience yourself (tags, title). But ideas are of no interest to anyone, by definition, except for those who are going to put them into practice. Don't you think that once you write an idea, how everyone will rush to do it? Of course not. Which means she won't be interested.
However, many IT people in the relevant field are interested in how complex things work from the inside. So if you, after spending a lot of time, understand the topic, and then you can explain complex things in simple language , then this will be valuable. The article does not have to containa lot of technical text or source code . But if it is necessary in order to convey the essence of the article, then it will not be superfluous.
The key point here is to spend a lot of time , ie. become at least more or less an expert . After all, you need to write about what you already understand, and not about what you want to understand. If you are a one-of-a-kind expert with a unique experience, then it will most likely be very interesting to read you.