There is a specific technique to writing software. It's different from designing algorithms, or any specific language or tool. You'll know the difference when you know your language, you know the algorithm, you know the problem... And still, the code doesn't just "flow" from your fingers.
What you need, in that case, is practice in the technique of writing software.
This book can help.
It turns out that there are a few simple, specific, concrete steps to that practice. They work in any language, alone or in pairs-or-more. They're not complicated, but good practice always takes work. I'll introduce a new-to-software form of practice taken from other disciplines along with those steps. I'll also give some accompanying guidelines, with what problems you should expect if you ignore them.
If you'd like to see more about the book but you're not convinced to buy yet, I recommend checking "https://codefol.io/topics/technique" for advice, an email class and more.
When you purchase, you should also receive an invitation to the Slack community of purchasers and practitioners. You're not required to join or participate, but perhaps you'll find it helpful?
You can, of course, also get a refund if you don't like what you see. We're all adults here. You know how this sort of thing is done.
NOTE: the book is content-complete, but has yet to finish final editing. You'll receive the current version now, plus all additional updates for free, forever.
You'll get the current draft of Mastering Software Technique, along with all future updates to this book.