• About WordPress
    • WordPress.org
    • Documentation
    • Support
    • Feedback
  • Log In
  • Register
  • Home
  • About Us
  • Blog
  • Courses
  • Contact Us

Have any question?

101daysofdevops@gmail.com
RegisterLogin
101DaysofDevops
  • Home
  • About Us
  • Blog
  • Courses
  • Contact Us

Blog

  • Home
  • Blog
  • Blog
  • My journey of writing a tech book

My journey of writing a tech book

  • Posted by lakhera2020
  • Date March 21, 2021
  • Comments 0 comment

This blog will share my journey of writing my first book, AWS for System Administrators.

Today I received the printed copy of my book AWS for System Administrators

This is the moment I have been waiting for the last 6–7 months. Ebook/PDF version was out a few weeks ago, but nothing compares to holding the printed copy of the book and seeing the content you have been working on by turning pages back and forth. I know it’s an old-fashioned way, but I believe printed copy will have long-term memory, which helps you remember the contents better.

Start of Journey

This whole journey started when Packt, Acquisition Editor, contacted me on Linkedin to write a book on AWS. I was hesitant at first, but on the second thought, I decided to write the book as I felt that it’s the right time to share knowledge with the rest of the world. I am using AWS for the last eight years and have already achieved 4 AWS Certifications(Overall 19th technical certifications), so I felt the experience I have in this technology would benefit other users. At the same time, it helps me to get my name out there along with recognition.

Effort and Duration

As I have already been using AWS for the last eight years, I was aware of most of the topics. But Cloud/AWS world changes almost every day, so I had to buckle up and make sure that the writing content was not outdated. I revisited AWS Documentation and the AWS re: Invent videos to ensure the book’s high-quality content. Some of the research was done alongside the writing process. So overall, I would say it took me a month to prep up before starting to write.

Challenges

I have written 200+ blogs, and in the blog, I mostly follow free flow format, but I found writing a book is an entirely different ball game as you need to share your knowledge with the user in an easily digestible way. To overcome this issue, I read books from other authors and started jotting down points that I completely overshadowed in the past.

The second major challenge was a very tight schedule along with a full-time job. But the proper planning and time management are the key to overcome this hurdle.

Continuously changing technological world

AWS/DevOps/Cloud is a continually changing environment. So you need to keep up to the pace to learn whatever new technology is coming into the market, so be prepared to upgrade yourself. Rather than focusing on one technology, try to learn the concept behind it and see how you can utilize it in other technologies.

The second key point is to get your hand dirty; if you are running a command daily, ask yourself how to automate it. Automation is the key to your long-term success.

Wrap Up

The way you understand technology is different from how other people think and understand it. So get into their shoes and try to present things in a manner that everyone can understand. Try to give as many minute details as possible even if you think it’s too basic; trust me, it will help someone reading your book.

  • Share:
author avatar
lakhera2020

Previous post

Extending Kubernetes with the plugin using Krew
March 21, 2021

Next post

My two cents on Blockchain and Cryptocurrency
May 28, 2021

You may also like

Am I reading the iostat command output correctly?
25 April, 2022

Iostat command came from the same sysstat family package # rpm -qf `which iostat` sysstat-11.7.3-6.el8.x86_64 It mainly read data from /proc/diskstats # cat /proc/diskstats 259 0 nvme1n1 147 0 6536 …

Debugging Performance Issue using SAR
21 April, 2022

What is SAR? SAR is a utility used to collect and report system activity. It collects data relating to most core system functions and writes those metrics to binary data …

4 common Kubernetes Pods Error and Debugging
20 April, 2022

Why do Kubernetes Pods fail? The two most common reasons for Kubernetes pod failure is The container inside the pod doesn’t start, which we also call a startup failure. The …

Leave A Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • Am I reading the iostat command output correctly?
  • Debugging Performance Issue using SAR
  • 4 common Kubernetes Pods Error and Debugging
  • My road to Gremlin Chaos Engineering Practitioner Certificate
  • My road to Certified Kubernetes Security Specialist (CKS)

Recent Comments

  • lakhera2020 on Debugging Performance Issue using SAR
  • Anonymous on Debugging Performance Issue using SAR
  • Pety on Day 2 – MetalLB Load Balancer for Bare Metal Kubernetes
  • akashambasta on Day 1 – AWS IAM User
  • rd on 100 Days of AWS

 

101daysofdevops@gmail.com

  • Home
  • About Us
  • Courses
  • Blog

© 101daysofdevops. All rights reserved.

Login with your site account

Lost your password?

Not a member yet? Register now

Register a new account

Are you a member? Login now