I get where you are coming from but this seems like gatekeeping to me? Who here determines whether or not the author is depressed? Do they need to delve into their past traumas to satisfy the critics?
They don't need to do anything, but using depression as a marketing gimmick is bad taste and will be judged poorly.
If that is gatekeeping, well ok.
I don't see it as a marketing gimmick. I see it as "I'm depressed and this helped me so this might help other people who are depressed.
By this metric, any good software or development practice is an antidepressant. And...they aren't not in a sense, but it's just such a strange and, I guess, selfish? self-centered? solipsistic? way to frame and label the idea of doing things correctly and comfortably in a professional setting. Like, the common factor of good or bad software characteristics isn't that they're going to send every user into a depression or bring them out of one. A bad feature might annoy users, and if it annoys them enough it might contribute to depression, but putting the entire burden of depression on a single software tool is like a carpenter claiming that a single bad hammer gave them depression.