Hello there! 🐧🐧🐧

I have been quiet for a few months, the reason being I had an opportunity to develop new interesting things and I have been experimenting with some other technologies while trying to find the best use cases. Meanwhile, I received a comment about a package that I have been maintaining for Arch Linux and I had no available time to respond or update my AUR package. If you remember from my previous post Packaging Go for Arch Linux Tutorial, I like maintaining AUR packages but it gets time consuming when you need to track new releases and update version, SHA and commit hashes manually by hand. I had to come up with my own niche solution. ...

So I have been dying to write this blog post for a while, I feel great that I had some time to focus on this topic. Initially my primary reason to write this post is I see great negligence from very senior developers when they hear “SQL” and I came across a few very senior interviewers who said “SQL is not even programming language, we use ORMs, why bother learning something that is not even a programming language (they mean SQL)” so the main purpose of this post is to shed some light over ignorance/incompetence with the proof of “SQL indeed is a programming language” and why you must learn and practice it just like other programming languages. ...

In this post, we will go over the most unknown 8 linters that are not used by the most people. These linters overall look unimportant, however they end up winning the hearts with their humbleness. If this sounds interesting, let’s start. 8 Godox # .golangci.yaml linters-settings: godox: # Report any comments starting with keywords keywords: - TODO - BUG - FIXME - OPTIMIZE - HACK // TODO: what the hell is this // hacky logic here ❯ golangci-lint run ./... main.go:18:2: main.go:18: Line contains TODO/BUG/FIXME/OPTIMIZE/HACK: "TODO: what the hell is this" (godox) // TODO: what the hell is this Godox checks the comments and dunks a linter error if unwanted comment is written with specific keywords. I encountered this linter after an incident that caused a prod deployment blockage due to me deleting TODO and hacky code section that were passing on all tests except prod environment tests. Long story short, there was no way for me to avoid TODO section logic because my task was interferring with already written hacky solution. ...

In this post, I announce my newest tool for language learners. As long as I am learning a new language, I plan to maintain it under my voluntary github org called Lingua Sensei. What is Laverna? What does it solve? Laverna is a sleek command-line tool that transforms text into spoken audio. All it needs is a config file to read. Whether you’re practicing Thai greetings, perfecting your Japanese pronunciation, or working on English phrases, Laverna can boost your productivity when you want to store individual language audios. ...

The Problem Hello, in this short and sweet post, I will show a handy bash script to catch slow go tests based on their durations and their go cache status, but first we need to define the problem. Our current problem is when I run go test -v ./... we get simply huge output that is overwhelming with subtest outputs as well as t.Parallel pauses/continues. Plus, my inner OCD strikes when some things are always cached and some things are always not cached, I could never guess why and I never have time to look at plain log that has 1 million lines. ...