I did a talk about React at my job and everyone really enjoyed the content and the way it was presented. I'm happy with the feedback and felt inspired to continue learning and teaching on this subject. That's when I had the idea to write a book.
I'm passionate about education and software development and I'm always trying to learn something new every day. Because of this, I feel that I can't keep what I learned just for me, I feel that I have to share it in the best way possible, so more people can learn and improve their skills.
Today I have about 4 years of professional experience, and it worries me if people would be interested in my book, since I do not have such a strong name in the community. I also don't know about proper writing, formatting, publishing and pricing.
I'm thinking about a big tutorial, but organized in chapters with (no so deep) clear explanations. Is this "tutorial" mindset the same for a book?
Any tip will be welcome!
All of us write code that breaks at some point. That is part of the development process. When you run into an error, you may feel that you don't know what to do. However, even the most seasoned developers introduce errors and bugs that break their code. We are humans after all.