This post could be summarised as "Stop talking, start delivering" but it would be a little too simplistic. It's a small "what do you feel?" post to see whether my feeling is shared among devs or not.
My feeling is this. We are overwhelmed with information, sometimes of great quality. And some good people spend hours writing very good starter tutorials, and I read them a lot here at dev.to but also in many other places (thanks to all). In some rarer cases, I find some really helpful articles that go well beyond "hello world" and is relevant to some of my current dev difficulties. Usually, I always find an answer to my problem.
Moreover, I often feel I should also participate to this sharing: provide insightful readings to fellow devs, in blog posts where I expose the various problems I had in the past in my dev life. Or maybe give speeches in conferences. But what should I write/talk about? I tend to avoid having very specific problems, and if I stumble upon one, I look for working around it. (Okay sometimes, I have to [re-]write some third-party libs to fix stuff).
I have one specific/personal problem though. I have giganormous personal projects. I am having monster fun at making them. But I can't afford having too difficult problems. I must be very efficient to actually deliver something. I've developed a kind of "code-as-as-unix-daemon" spirit, where I can start (and stop!) coding in no time, while still handling kids and family time...
And this point of efficiency is so intense that this blog post is the first (and maybe the last?) of a long list of unfinished unpublished drafts about unclear subjects that will actually... be pushed "in production"! Because I have only one thing that matters, and that I really love: pushing my stuff in production.
And you? What's your feeling? Do you share some bits of what is described here?