Go along!

Go along!

Hello Guys! πŸ‘‹πŸ½

Earlier this year, I resolved to prevent consequential drift in my personal development that plagued me last year, regardless of errors, bugs, tasks, and associated deadlines.

So, I'm embarking on a quest to up-scale my personal development road map firstly by conquering the ancient & contemporary art of Go πŸ₯‹ via conquests against sneaky bugs, data structure & algorithm problem sets, tricky system designs, large systems architecture, and implementation of high availability systems but generally usurp and bask in the triumphant victories.

But guess what! I've unequivocally decided to drag you along for the ride!
Lucky you :)

Get ready for a regular or irregular dose of my epic adventures in Go Mastery 😩.

Last year at a glance:
I got clouded with additional responsibilities & leading exciting projects, although I was able to bag my Azure DevOps Certification along the way, got the all-builders welcome grant, and an invitation to the Valorant Champions game in LA, etc.

What to expect?

A series of series structure, such that I discuss various related subjects, topics, and learning paths in threads. It's going to be like a Netflix series, but with more strategy and fewer snacks **(**unless you count the occasional victory cookie ):

So, buckle up and watch this become a blockbuster πŸ™ƒ.

So, why Go Lang?

Picking a native (default) programming language can be compared to choosing a soulmate **(**calm down. I'm getting somewhere :)

Ensuring it's up to your specs or what you're looking for or want in a language you know **(**communication, performance, speed, simplicity, and a beautiful syntax that makes you admire your code :) because most likely it would be your default go-to in times of trouble and triumph hopefully till your programming career successfully winds down.

A quick guide of how, why, and what to look out for in a lang-mate

  1. Gather adequate insight about the language you want to learn to further spur you towards learning it. (if no inspiration is found, you should probably reconsider). Cause you need to be strategic while picking up any technology stack. You can start here.

  2. Having a mentor is great, but try as much as possible to craft your pathway and not imbibe their entire journey (believe it or not, your personality would influence your career).

  3. Simplifying your journey towards mastering a language and then a framework.

  4. Ask a lot of questions. You can barely go wrong with asking questions, doing rigorous research to validate the answers, and pursuing further knowledge about the domain because a fluent speaker doesn't translate to a knowledgeable one.

  5. Having a detailed understanding of the principle of how technologies work would serve you much better than watching every tutorial that comes your way. Always emphasized understanding & comprehension way before execution.

  6. Make use of tutorials with less ambiguous words. Look up, understand, and write down new terminologies.

  7. How extensible the language applications and their community is towards your other interests?

  8. Fewer years of experience can be amplified with an extensive understanding and command of a well-chosen language. It also comes in handy for problem-solving skills.

  9. Passing down knowledge after a good grasp helps further improve your fluency in expressing your knowledge of such domain which would help hold meaningful conversations with experts and in interviews.

  10. Keep precise notes (digital or analog).

Not just Go

My pursuit in designing, architecting, building, scaling, and maintaining sustainable & effective solutions would continually evolve around closely coupled technologies, thus making me quite a Jack with a handful to master.

I've whipped up a fabulous adventure schedule to dive into the world of Go Lang!

Picture this: A thrilling journey through expert-crafted courses, starting from the basics of Go, weaving through the enchanting realms of data structures and algorithms in Go, soaring into the clouds (AWS, Azure, GCP, Civo, Dream Ocean, etc.) with Go-based DevOps magic, navigating the intricate landscapes of Microservice Architecture and Backend Development Design patterns with a sprinkle of Artificial Intelligence and machine learning.

Addressing the Elephant in the room:

Why were you dragged along :(

For one, an accountability partner to help prevent any drift, chill! I'm not trying to use you 🌚. You know this would be a healthy symbiosis relationship regardless of whether you are a beginner or an expert. Just go along!!!.

You stand a chance to learn a lot, and of course, I'm open to structured criticism, discussions, and questions during the series. Fingers crossed, I will strive not to bore you or misplace you. Also, from the perspective of a future movie producer & writer, I would endeavor to paint a vivid image during this series of series alongside cute illustrations.

Thanks for now 🫢🏾,

see you 🫡🏾 soon :]

Β