In this time machine series I want to recall some of my older experiences that I didn’t write blog posts about. It’s basically me going back in time and recalling some of the cool things that my team did Migration of components In this blog post I’m gonna tell about one of the stories from my work from around 2019 end / 2020 start if I remember correctly Me and my team had this task of migrating a lot of components - Postgres databases and Redis databases / caches from one Kubernetes cluster to multiple clusters

This is a very simple post about the kind of features that users would expect in general when it comes to the ability to share URLs of websites Let’s start with an example. I’m sure many of us would have shared a lot of URLs. A popular example that comes to my mind is - sharing YouTube videos. YouTube allows users to share videos by having a button called “Share”, which shows the video’s short URL link and also the ability to share the URL on different mediums with ease.

This is a short post about how one can try to avoid rookie mistakes. This is just me jotting down lessons for myself :) Note: Rookie mistakes are common and can happen anytime. It’s good to learn from them and create processes and tools that help you succeed :) Recently I made a rookie mistake where I created a temporary git branch in a git repository, but I couldn’t delete it and this lead to problematic things that I won’t get into

This post is to see some of the cool things in the modern software development and the kind of experience that developers can get. This post especially focuses on a kind of experience that I expect to get as a developer when I develop for backend (servers, services, microservices etc) or frontend (web app). I’m not going to be focusing on other kind of software in this blog post Focus If you think about it, as a developer, I want to focus on building software.

TLDR; shellcheck is a open source linter for your shell (sh/bash/dash/ksh) scripts! The official website calls it as - “a static analysis tool for shell scripts”. A small example usage - $ cat list-special-files.sh #!/bin/bash dir=$1 for file in "$dir/special-*"; do echo $file done $ shellcheck list-special-files.sh In list-special-files.sh line 5: for file in "$dir/special-*"; do ^--------------^ SC2066: Since you double quoted this, it will not word split, and the loop will only run once.

TLDR; $ man envsubst Online man page - https://www.man7.org/linux/man-pages/man1/envsubst.1.html $ cat sample.template.yaml shell: ${SHELL} # notice how we can use ${} format too histsize: $HISTSIZE home: ${HOME} user: ${USER} $ cat sample.template.yaml | envsubst '$SHELL ${HISTSIZE}' > sample.yaml $ cat sample.yaml shell: /bin/bash # notice how we can use ${} format too histsize: 50000 home: ${HOME} user: ${USER} Longer version Me and my team mate are working on writing some automation scripts to automatically run some commands which can bootstrap a kubernetes cluster.

⚠️ This is kind of a rant post too. You have been warned! 😅 Also, it’s a lot of scattered thoughts too. I’m sorry if you feel lost somewhere 🙈 Given that a lot of modern and tech based companies have moved from an office setup to a remote working setup - working out of homes or multiple scattered very small offices etc, the mindset of the companies doesn’t seem to have changed much.

I have been working with software since 2011 when I started learning the ABCs of C/C++ in my 11th grade, and I was a user of software way before that. I have been professionally working with software since 2017 when I started freelancing and then joined my first company for a full time job If I look back at all those years of writing code, I can clearly remember some experiences where I banged my head to solve some problem and figured out a good way to debug or analyze the problem at the end of it.

I was recently working on a front end project where the code was written in TypeScript. It was a React project, and it was bootstrapped with Create React App (CRA) tool. And the testing framework that we used was Jest. The team quickly realized that the test code we wrote was not being type checked and we could see TypeScript type errors in our text editors and Integrated Development Environments (IDEs) but there were no such type errors when running the tests using react-scripts tool to run the tests which in turn used Jest

This post is a part 1 as I have lots of small scattered thoughts around this and I have been postponing this post because I wanted to put it all but then I decided to do it iteratively like software development ;) This post is to provoke some thoughts in people Trusting on Open Source We all use a lot of Open Source. A lot of us trust Open Source, as the source code is open and anyone can read it