Do you know how email tracking works? In this blog post we will look at some of the basics of email tracking. A few years ago, I was working on this open source software called Mail for Good by Freecodecamp. https://github.com/freeCodeCamp/mail-for-good It was a software used by Freecodecamp and many NGOs for their email campaign management. It was built on top of Amazon Web Services (AWS) Simple Email Service (SES) which costed around $1 for 10,000 emails at that time.

Let me start with the beginning of the story of the team when I wasn’t present. I know only some details about this which I was told by the team members. I know better about what happened after I joined, but given my bad memory, I can only recall some of the important moments. Also, it was around a 2 year journey. I’ll try to recall as much as possible 😅

I have always been curious about internals of some systems, if not all. One of them is the CI/CD system and how it works with source code hosting services. Apparently it’s not too complicated. So, let’s dive and see what are the different ways CI/CD systems work with source code hosting services So, what’s actually the thing that I was curious about? I was to curious to understand how a CI/CD pipeline runs for exactly a given commit especially when there are pushes to the source code immediately in a matter of a few moments / seconds, but pipeline for both runs only after a few moments but at the same time but with correct commit in each.