After embarking on the Brainless journey of learning MLOps, I’ve decided to take my coding prowess to new heights by immersing myself in the world of Vim. Because, you know, what’s life without a little brain overload?

Now, let me confess something. I’m a die-hard user of Jetbrains products. Their IDEs have won my heart, even if it means sacrificing performance resources and dealing with an abundance of [potentially superfluous] tools. It’s a necessary evil, or so I convince myself.

But deep down, I yearn for the smooth experience of Github Copilot. Sadly, it doesn’t play as nicely with Pycharm as it does with VSCode. And to add insult to injury, Github Copilot Chat is nowhere to be found. Oh, the disappointment!

In my relentless pursuit of coding efficiency, I’ve ventured into the mystical realm of Vim. But here’s the kicker: I use a customized layout (a modified AdNW) and an Iris keyboard, making the Default Keymap Vim a bit nonsensical for me. So, like a true pioneer, I’ve decided to craft my very own custom keymap in Vim.

To spare my precious ‘production’ system from potential chaos, I’ve set up a VM running Ubuntu. Ah, the brilliance of my plan! Or so I thought. Little did I know that I would encounter terminal troubles and an admin rights conundrum. But fear not, my problem-solving skills came to the rescue, and I triumphed by rebuilding the VM. Pure genius, I tell you!

And now, my next steps beckon. I must find a way to install Vim and embark on the thrilling adventure of changing the keymap. Oh, the countless hours I’ll spend optimizing my keymap, sacrificing time that could be better spent on… well, anything else.

But hey, it’s all part of the journey, right? Vim, here I come!