Kyvernetes Icon Kyvernetes.

Welcome Devs!

misc.

6 min read

Published on Mar 5, 2024

Jump to ...

Welcome!

Hey there 👋 ! I’m Kyvernetes, and I’m stoked to kick off this blog journey with y’all.

ANOTHER Blog??

In a world teeming with blogs, most are tailored for absolute beginners. I don’t need another lengthy intro into the basics of for loops and if-else statements. I am a junior dev myself, and I am sick of those kinda blogs. Also, I don’t like lengthy docs, and admit it, neither do you. I echo Linus Torvalds’ sentiment:

Talk is Cheap. Show me the code.

So, my approach aligns with this philosophy –- minimal words, maximum code. I’ll provide concise explanations where needed, steering clear of unnecessary verbosity. While reading the manual is golden, it doesn’t always suffice, especially when dealing with arcane or cutting-edge technologies with scant documentation. I had to spend some considerable time through those cryptic codebases, obscure tech, and outdated websites to gather insights. I’m here to share my findings, sparing you the search, wherever possible. And I will let you know all the tricks and tips and hacks I used.

Expect discussions on performance, functionality, and other critical considerations to make informed choices. Will I make mistakes? Absolutely. But I won’t delete anything from my blog. Corrections and updates will be front and center, admitting where I faltered and how I rectified it.

No adherence to programmatic dogmas, no hypes or sermonizing, and certainly no tech shilling –- I’m not an influencer. No rage tweets, no baits –- just code that works. Performance and binary size take the spotlight, areas often overlooked by many devs today. Get ready for experiments, tales of my foibles, and the lessons learned. If my unconventional approach doesn’t resonate with everyone, that’s okay. My focus remains on delivering functional code and sharing the intricacies of my coding journey.

OS and Distribution Preferences

Personally, I opt for Linux-based OSes for their superior customizability and a richer library ecosystem compared to Windows. My Windows misadventures at the age of 15 pushed me toward Linux, specifically Ubuntu, and I’ve been hooked ever since. While I occasionally dabble with Windows, the Linux terminal feels like home.

After facing some problems with Ubuntu, Manjaro and others, I now use Arch Linux, thanks to EFLinux’s awesome tutorials. Contrary to popular belief, Arch Linux isn’t as daunting as it sounds –- a proper tutorial makes all the difference. I chose Arch for its cutting-edge nature, satisfying my need for the latest package versions. I love Debian, but couldn’t love Ubuntu. PPAs, flatpaks, and snaps became more of a hassle. There are notable cases where these two shine, the most prominent ones being support for the most recent version of LLVM, or if you ever want to use Xilinx Vivado.

I am considering a potential switch to NixOS, I plan to run some tests in a VM and let you guys know. Macs have always been out of my budget, and Linux proves to be a reliable choice without breaking the bank. If you are interested in NixOS, and made it work with dynamic libraries and all, I would love to hear from you.

A note to other readers: Please don’t do random distro hopping, it’s a waste of time. Know why you are switching.

My IDEs, Editors, and Tools Preferences

  • IDEs and Editors: NeoVim user here, but it’s prone to breaking. To mitigate, I avoid updates for 6 months, then rewrite the whole config and update everything. Didn’t use Vim as Vimscript isn’t my thing; I prefer Lua. No Emacs yet, maybe later. I use VSCode too, for frontend stuff, and for Java, Kotlin, and Android I use JetBrains and Android Studio. I just enable Vim mode everywhere. Point is: Use the right tool for the right job, I need to code, not get into editor wars.

NOTE: Scratch that. I almost use VSCode exclusively now, with vscode-nvim. It saves time.

  • fzf and rg: I use fzf for lightning-fast codebase and file searches. Highly recommend it for efficiency. Combine it with greppers like ripgrep for text searches.

  • LSPs: Configure Language Server Protocol (LSP) whenever available. Game-changer for jumping to definitions, and going through codebases.

  • Themes: Opt for themes with proper syntax highlighting and contrast. Crucial for error spotting and eye comfort. In well-lit spaces, consider a light theme for optimal visibility, especially for those with astigmatism. Always prioritize good contrast themes.

  • WMs and DEs: I like tiling WMs, but if you don’t, look into GNOME or XFCE. However, if you happen to use Wayland, and are gonna use a tiling WM, I recommend HyprLand.

Coding paradigm and preferences

Clinging to a single dogma or programming paradigm is dumb. While pure functions in, say, OCaml may excel, TypeScript operates differently due to its lack of an optimized compilation pass (in a typical repo). ”Clean Code’s” short function emphasis may sound admirable, but it can lead to a convoluted code maze. The microservices hype, once fervently embraced, saw a quiet retreat to monorepos as developers overlooked crucial performance considerations. The lesson: resist succumbing to Twitter trends and hypes, explore various programming paradigms, and prioritize performance nuances. Crafting effective software involves a judicious mix of approaches, and there’s no one-size-fits-all solution.

I don’t pledge allegiance to a specific programming language or paradigm. While I am partial to languages like C++, C, Rust, and Zig for performance, I also find value in Python, TypeScript, Go, OCaml, and others. My debugging involves strategic print statements and flags to locate memory leaks in memory-unsafe languages. Learning, for me, is a blend of experimentation, blog reading, and YouTube videos. I seek sources that cut to the chase, offering pragmatic insights and a touch of unconventionality.

Also, please consider performance implications early on. They say hotspot engineering is good, but I beg to differ. If you first build a bus, you cannot just turn it into an F1 car by changing the engine

So again, who are you?

Check out the About section for all the deets. Cheers to a thrilling coding journey! 🍻

Also, what is the meaning of the word Kyvernetes?

My first name is Aritra. The Greek work κυβερνήτες has the same meaning as my name, which, when anglicized, is ”Kyvernítes” or ”Kyvernetes”

Editor: ChatGPT