As developers most of the actual work is done behind the scenes (or screens). This is not just for backend development, but goes for frontend development just as well. Consider all the time, effort and planning that goes into executing a technical solution or building an interface. Aligning between multiple stakeholders or comparing technical solutions and routes before implementing, goes largely unnoticed.

In most cases, what the end user sees, is just the tip of an iceberg! With "going public" I mean proudly exposing the underside of that iceberg. Not for the sake of the end user, but for your self. You should always consider contributing to your personal brand!

Ever since I started the process of writing a book I have had to work on streamlining the content creation part a bit! For articles on my personal website, I usually write and post when I have something the share. Usually these are simply articles conveying my thoughts or small tutorials focussing on a very specific topic. For the book Building Real-world Web Applications with Vue.js however, I have had discover a new process.

It started with determining the outline of the book with all the topics we wanted to cover and address. That structure really helped in getting the scope for each chapter right as I've discovered. Scope creep is a real thing, when you want to teach and deliver well rounded projects!

I finished the draft of the third chapter today. After some proof reading of my own, it will be off to the editor for the first review. After writing a couple of chapters, it's a good time to do a bit of reflecting on the go.

I really enjoy writing this sort of content. Having the structure of the entire book laid out beforehand also really helps in making sure that I focus on a specific topic at a time. Without, I think I would be tempted to start drifting off topic by elaborating on more niche or advanced techniques.

I've been working on another starter document, the Product Information piece. This is not necessarily part of the book itself, but is key to the success, since it holds the marketing texts and information.

This is a bit of a different mindset, because this is about trying to condense the contents of the book (which doesn't exist yet) into enticing commercial texts of varied lengths!

This morning I've met with my support team from the publisher. They will help me guide through the process of writing and publishing a book. (Well in all honesty, they are going to do the publishing part. I just have to provide the content).

This means we passed a couple of steps already. I've signed the agreement to get the whole process in motion. I've even been assigned an ISBN number (life goals 🙌).

As the great fictional professor Hubert J. Farnsworth said: "Good news everyone!". I'm going to be an author! After a short process of creating an outline and some back and forth between a publisher, I've been given the green light on writing a book on VueJS projects.

This is something I've never done before. The most writing experience I have so far is writing on my personal website, posting articles on Medium and Dev.to and one publication, which was my sole experience working with an editor.