6 Neovim Plugins I Use To Troll Code Reviewers


6 Neovim Plugins I Use To Troll Code Reviewers

This issue is brought to you by:

Ready to Take Your Testing to the Next Level?


Don’t let complex testing slow you down! With Squish, you can automate your entire UI testing process across multiple platforms, ensuring both speed and accuracy. 

Ever felt like your coding experience lacks a certain… je ne sais quoi?

Most developers solve the problem of mental fatigue or coding block by taking a coffee break or scrolling through social media.

While these methods can provide a temporary distraction, they often pull you completely out of your focus.

My solution? Stay right where you are, but add a touch of the unexpected to your familiar Neovim setup.

See what i did there? I just made a justification for taking away your precious productive minutes

Perhaps what you’re missing is a duck 🦆 waddling across your screen or your code raining down like Matrix-style 🈯 digital precipitation.

Fear not, fellow developers, for the Neovim community has got your back with a plethora of utterly useless yet oddly entertaining plugins.

These plugins serve no practical purpose. From making your code “rain” to typewriter sound effects that transport you back to the 1920s, you’re going to want to try these. So with out further ado, let’s start:

  1. Cellular Automation Because who needs readable code when you can have a digital rainstorm in your editor?
    This one is a great way to troll any code reviewer. It’s like The Matrix, but with less Keanu and more semicolons.
  2. Duck.nvim For when rubber duck debugging isn’t enough. Now you can watch an actual duck waddle through your spaghetti code. Don’t stop there though, you can hatch() any emoji with no limit until your screen is crawling with creatures running around.
  3. Discotheque.vim Turn your boring old syntax highlighting into a groovy disco party. Warning: unmaintained and just as well unnecessary.
  4. Typewriter Embrace your inner Hemingway with authentic typewriter sounds. Perfect for when you want to feel like you’re writing a novel instead of debugging a bash script gone rogue.
  5. Vim Syntax Christmas Tree Feeling festive? Working on Christmas? Because nothing says “I’m a professional developer” like a twinkling Christmas tree next to your production code.
  6. Deal With It For when your code reviewer leaves one too many nitpicky comments. Respond with style and sass, all without leaving your beloved Neovim.

Wanna hear how a junior dev managed to lock themselves (and the rest of the company) our of their main server?

Here’s a thread I wrote this morning.

Thank you for reading, have a great weekend.

ESPRESSO FRIDAYS

Every once in a while I send hand picked things I've learned. Kind of like your filter to the tech internet. No spam, I promise!

Read more from ESPRESSO FRIDAYS

Kubernetes - Does It Live Up to the Hype? Twelve years ago, I landed my first DevOps role. I was a junior engineer, responsible for infrastructure and security at a startup (yeah, not the best call on their behalf), that would later become a unicorn. One evening, our CEO landed the first huge client, and we had 24 hours to prepare. I panicked. I spun up extra servers, scaled out load balancers, and froze every scale-down rule I could find to make sure we overkill this and that I'm not the...

Neovim from Scratch to BEAST Mode It took me 12 months to make Neovim look like a worthy code editor. This was 9 years ago. Today, with one small installation you get fuzzy pickers, LSPs, text objects, debuggers and MORE. Honestly, if you have the Vim basics and would like a quickstart Neovim pre-baked with everything you need, there's almost no need to make an effort, thanks to distributions like LazyVim. The traditional approach to Neovim setup has always been a rite of passage - slowly...

7 Amazing API Tools You Need To Try Before becoming a systems architect working with unicorns, I made a mistake that cost my team three days of debugging. I hardly left the office for 48 hours, and that experience taught me a valuable lesson. I thought I knew everything about HTTP requests. Having used curl for years, writing APIs, and building integrations, I felt confident. Then came the incident Our back-office application was failing, and we couldn’t help with burning customer requests. I...