Background Security issues happen, and one of them happened at Skytable last week. It began with my friend Martin writing a C# driver for Skytable. We were deep into discussing the implementation when he said that he wanted to include TLS as a part of the driver, which would obviously be an amazing thing to have. So, we issued self-signed certificates and he started working on the TLS component for the driver (since I’m not a C# person in any way, I continued my work on the core codebase).…

It all started back in 2020 when I was working on a project in stealth when I really lost my head on a database schema. (Let’s not say which database, but it started with the letter M). It really annoyed me. It bugged me every time I’d work on the project and finally, I was so fed up — I started writing a database. In the beginning it was really a REPL: you’d type in SET x y and the REPL would say Okay while doing a SET behind the scenes.…

GitHub Actions was GitHub’s take at CI/CD providers and also a very rational response to competitor GitLab’s CI/CD. The fact that your CI/CD lives right next to your SCM is absolutely amazing and is one of the selling points for GitHub Actions for many. The good part(s) There are several things that make GitHub Actions very appealing; a few of these are: It’s right next to your code; like literally an ‘Actions’ tab lying close to your ‘Code’ tab It is free for open-source (with some limits); this is a big selling point for me as I write open-source code almost all the time It is open source, itself.…