"Blue-Green deployment" is an application release model, software deployment strategy and deployment technique, which offers:

• Near zero-downtime 🤯

• Simple roll-back capabilities

• Very low chances of failure 📉

• No maintenance windows

• Improved testing

Blue/green deployments can mitigate common risks associated with deploying software, such as downtime and rollback capability

- Amazon in the AWS White paper on blue/green deployments

How does "Blue-Green Deployments" work?

In Blue-Green Deployments, we have 2 servers, named green and blue. Both of them have identical environments but different versions. In the blue server, you have your production application which handles almost all of your traffic. Whereas in the green server, you have, a semi-production or staging version.

Now we test the green server if it works and is ready. We start slowly channelling away traffic to the green server. In other words, we follow a rolling release to publish the green server version.

So for instance, we have blue running on v1.0.0 (prod), and green on v1.0.0-beta (staging). We test the green server's version internally, then roll out the new version in chunks to our users. In this example, we give 25% of the people access to use it.

And this is repeated till eternity ✨ Here is the graph of the same scenario:

What happens if my beta app breaks?

Let's take a second scenario, in this scenario, somehow the application passes the internal testing phase, but when users use it, it breaks apart 🥲. We can do an instant roll-back by redirecting all the traffic to the blue server!

Rolling releases with Blue-Green Deployments

Since we have 2 servers where we are diving the traffic, we get to offer a certain feature to a set of users. This provides different benefits:

• You minimise risks since your release does not affect your entire user base

• A/B Testing allows you to analyse user groups' performance (both system & conversion).

• Feedback Loops: You can constantly collect feedback from users and iterate to improve your application.

You can send out the version to your users by directing traffic based on various factors such as:

• Randomly: You can send it out randomly to your users

• Geographically: Want a feature to only be available in the USA while you test it? You can!

• Beta-testers: Enrol users in a beta program or a select group of users like your friends and team 👀

So basically it is like feature-flags but for versions!

More benefits

• Production testing! Since the app is on a replica of the production environment you can say we're testing on production 💥

• Since you are switching servers and resources, you do not have to worry about upgrading the application without breaking everything else!

• Since with the cloud, we can tear apart and provision new services instantly, it is also more lucrative/cost-efficient for us.

Challenges

It does not make sense to have 2 databases and to sync between them for the environments, instead, we do the obvious and use the same database. The problem occurs when you make a breaking change to your schema because then your production version falls apart as it no longer can query for the same data schemas.

Other challenges include the inability to use the components of this method due to project, regulation or infrastructure-based restrictions.

Further resources

• Blue/Green Deployments on AWS (a Whitepaper by AWS)

• Continuous Blue-Green Deployments With Kubernetes (an Article by semaphoreci.com)

To understand DevOps, we first must understand what the past was.

World Before DevOps

DevOps stands for Development and Operations, and you might have guessed already. The name comes from the origins of DevOps.

Before DevOps, There used to be two teams: Development and Operations.

The development team worked on planning out and coding, whereas the operations team operated the entire codebase.

There are various challenges with this model:

• Miscommunication/Lack of Communication: Developers can't deploy and don't know the production environment. The operations team doesn't understand how the application works.

• Conflict of Interest: Operations and Development as teams have different goals. The developers want to push changes faster, but the operations team wants stability.

• Security and Testing: Security and Testing teams work on this. The code has to go through several approvals from these teams before being pushed to production.

This caused the release of the project to be delayed. It is not in the best interests of any company to not follow schedules.

Where DevOps comes in

The development and operations teams have a link, the DevOps team. DevOps teams clear out these blockers on the release cycle. This allows for faster release.

DevOps is the practice that allows for the release cycle to be faster. Earlier, DevOps was just a company philosophy and was different across companies. With the growth of DevOps, several standards were set.

DevOps has become a separate role, and the technologies used in DevOps are termed DevOps Tools.

Why DevOps?

Speed

Removing the roadblockers is the responsibility of the DevOps team. With DevOps, Developers no longer need to await review idly for long times. The automation carried out by DevOps engineers is also a heavy lifter.

Collaboration

DevOps is entirely based on the principles of collaboration. Thriving collaboration allows for better end products for the customers.

Assurance

In DevOps, the applications are rigorously tested and monitored. This gives the assurance that the application will not cause failure frequently.

Phases of DevOps and the Infinity Wheel

Image Source: https://www.atlassian.com/devops

DevOps is often represented as an infinity loop. It has eight stages. Let's go through all of them, starting with the planning stage.

Discover

Organization and prioritization of ideas are necessary.

In the initial stages, the "Discover" stage may include understanding the problem statement and the required initiatives. In later phases, it can be "incorporating the changes suggested".

This stage can largely be carried out by creating Tickets or Issues in Jira or GitHub.

Plan

As fun as it would be, barging into the problem like barbarians is not an efficient way to work on a project.

Therefore, teams tend to work through a plan. They strategize the goals and set deadlines.

This is often achieved using Kanban Boards on Trello or GitHub Project Boards.

Build

This is the coding part of the cycle. The developers start working on the code according to the plan. Most likely, They will be working asynchronously over the same codebase. This requires the need for version control.

Version control allows teams to keep track of their changes and effortlessly merge the changes two developers worked on asynchronously.

Of course, Git is used for this part of the cycle. Alternatives include Mercurial and SVN.

Test

Testing is essential for production. Users don't exactly use the applications as developers intend. Developers must prepare for the worst with test cases for such scenarios. There is a lot to talk about tests for another article.

Automation: CI (Continuous Integration) pipelines are set up to automatically run tests on the code before merging it to the master source. CI is a script that runs on a schedule or event and returns failure/success. It allows assurance that the code being published is foolproof.

Popular CI providers include Jenkins, Circle CI, GitHub Actions and GitLab CI/CD.

Your choice of testing software will depend on the tech stack.

Deploy

Now, it is time to push to production. In the deployment phase, the code is released to production. Releases are more frequent and generally automated.

Automation: CD (Continuous Delivery) is the same as CI but for deploying changes to production.

Innovation: Feature Flagging is a system where you release the new version to a smaller group before making it available to the entire user base. It allows you to observe the impact of the changes before making it live for all the users.

Operate

Operating infrastructure and configurations are also a part of DevOps. You could also think of this phase as ensuring "end-to-end delivery of IT services to customers" (source: atlassian.com)

Observe

You will not know the health of the application without observing it. The "observe" phase includes setting up log drains to notice errors, uptime and speed of the code.

Automation to inform teams about high-risk failures is also a part of this.

Tools like Grafana are used for this phase.

Continuous feedback

Providing feedback to the development team and suggesting changes will improve the project regularly. This is extremely necessary to keep a bug-free code base.

Note: There are different versions of the DevOps infinity wheel. The differences are just in naming convention or too minimal to account for.

Security and DevSecOps

Considering security an essential part of the development and any phase, DevSecOps is like a fork of DevOps where security is emphasized at every stage. It integrates security into all of DevOps to minimize vulnerabilities.

It also has a separate infinity wheel:

As you can notice, there is a great emphasis on testing the code, code review, and scanning vulnerability. We will talk more about this in my way future articles because this is irrelevant right now.

Conclusion

DevOps is a philosophical thing. It is a set of practices that a company uses to release stuff rapidly. It is a gigantic and growing field. Here are some resources for you to explore further:

• 90DaysOfDevOps 2022

• Atlassian DevOps Blogs

• Roadmap.sh

I hope you learned something new from this article. Please drop a like and share it with your network. It brings great motivation for me to continue writing such blogs. :D

I am working on this as a series to teach DevOps as I learn it. I will try my best to publish at least one article every week! :)

• "You can get a job with open source."

• "Open Source experience should be included on every developer's resume."

• "GitHub is your resume!"

Okay, I admit that the last one is just me.

So it's good to say that tech Twitter somewhat agrees with me? No. I disagree with half of the things tech Twitter says about open source. In this article, I try to map out open source with my experience and knowledge after almost a year and a half of contributing, maintaining, and advocating.

So what exactly is Open Source?

The book definition

Open source is code that is publicly available for anyone to study, improve, change, and redistribute to everyone.

Each of these may have a slightly different implementation due to the various open-source licenses available, but at their core, you should be able to do all of them.

The actual definition

Open source is a community of developers dedicated to the greater good. Many developers just open-source their projects to make development easier for everyone by solving common problems. Some other developers are against big corporations owning everything and favour creating open-source alternatives.

So it's just a VERY VERY VERY large community consisting of just 100 million people on GitHub

Popular Open Source Projects

So most people joke about Open Source software not being good :/

Especially about Linux,

What most people don't realize is that almost all of the code in your browser is open source. The entirety of the internet's backend is also open source, as is the software that Hashnode is using to present this article (NextJs). It does not take a good while to realize how much of your life is open source.

Why should you care?

Does Open Source bring jobs?

Short answer: It can.

Long answer: It most probably will not. Getting a job entirely through open-source contributions is a new thing most companies are still not into. But open source can help you get a job in other ways.

Resume

Open Source is a significant addition to your resume; it demonstrates collaboration and soft skills, as well as visible proof of your knowledge.

Skills

You can learn anything from industry professionals via the medium of open source. I could right now pull up a MEVN stack project, send in a PR, get a code review, and learn from people working in that tech stack—the people who built that project itself.

I mean, developers these days post these memes on Twitter:

Ok. You got it. No one can design such a bad meme other than me, so it's me, but how did you know this? :|

Open Source Noo Noos

Open Source Only For Jobs?

Never. Open source is not a way to get a job; it is just a multiplier to increase your chances. Don't let open source take over everything, including portfolios and projects.

Yeah, imagine explaining that situation to your partner's recruiter.

Beginners can't contribute to Open Source

I contributed without any knowledge of computer science as an 8th-grade student. What in the damn world can stop you, apart from yourself being lazy?

So I can, as a beginner, contribute to open source, but you can't? ("Yeh Sab Doglapan Hai!"; Translation: This is the true contradiction.)

You can not contribute to big projects

Where do big projects get their contributors from? If you think about it, every big project began as a small project. So what's the difference between small and big projects? Bigger projects move faster, but can you attribute that to their having more files? So it's balanced most of the time.

I've contributed React's documentation (which is in the queue right now); that proves that no matter how big a project might get, there is somewhere you can add value.

You have to be a dev to contribute

There are so many ways you can contribute! Why limit yourself to code contributions? You can add value in so many more ways (you can create your ways to add value)

• Code

  • Feature Addition

  • Refactoring Code

  • Bug Fix

  • DX Improvement

• No Code

  • Documentation

  • Content/Awareness/Education

  • Community

  • Triaging (Confirming if that issue exists for you)

On a side note, anything that adds value is a contribution. (I'd also like to clarify that you do not need to contribute to only complex issues to be a great contributor for the same reason)

Let's do this!

So let me be clear: where I can help you, and where I can't:

• ✅ Git & GitHub

• ✅ How to approach projects

• ✅ How to communicate as a contributor

• ✅ First steps on making your first pr

• ❌ Listing projects that you should contribute to (✅ I will tell you how to find them here though)

Step 1: Git & GitHub

Git and GitHub have often been overlooked topics when it comes to open source. They are an integral part of contributing to open source, yet they are just left with a list of commands. I'll do my best to give you here a concise guide to git and GitHub, including all key terminologies and functionalities.

• Git: Git is a version control system that allows teams to work on large projects with versioning and collaboration support

  • Commit: A commit would be on a version of the particular source. Commits include information about the changes and who made them.

  • Branches: When collaborating different teams need to work on different aspects of the source, branches provide a way for teams to take the source repository's current commit source to what you could call a somewhat altogether different repo that could be merged later into the main version (main branch) when the team is done.

  • Merge Conflicts: If two of the teams edit the same part of the source in 2 different branches and the first one gets merged then the second one will have to review and resolve any conflicts since the changes in the second PR do not change the main now, but branch 1's source has been merged into the main.

• GitHub: GitHub is a hosting provider for git which has now branched out to have many other services, which give it the title of the place where the world writes code.

  • Forks: Most of the time you do not have access to the official hosted repo's branches to make your edits (for obvious security reasons), in that case, you have to download that repo not locally but on your personal GitHub account so that it's still accessible to the internet.

  • Pull Requests: It's just you asking the people who do have access to the official hosted repo to pull your fork and merge its branch to the source of the official repository. (This is one way to contribute)

  • Issues: Just a tracker of the submissions for bug reports, feature requests and other things someone might suggest/report to a project.

There are many Git Cheatsheets available on the internet if you need one!

Step 2: How to approach projects?

Finding projects is very hard; Here is a list of approaches you should use to find your projects:

1. Your Network
   Many people in your network will have their projects hosted on GitHub it is a great opportunity to add value to their projects.

   People in my network have always surprised me with cool projects! I am sure your network will surprise you too!

   

2. Projects You Use
   There are hundreds of projects you already use, did you know that Chrome, Brave, Android, VS Code, GitLab and Gitpod are all open source?

There are Open Source projects like Curl which have been used on Mars 🤯

3. People you follow
   If you are seeing this post, you must be following some people who have open-source projects! Yes, everyone whom I follow has at least one!

   • YK Dojo's kaguya

   • Eddie Jaoude's book-open-source-tips

   • Francesco Ciulla's free-web3-resources

are a mere FEW!

4. GitHub Trending
   YES, YOU HEARD IT RIGHT, GitHub has a page to keep you up with all trending repositories, it can be used to find new projects to contribute to

It can be filtered by languages as well 🚀

5. GitHub Search
   You can also search GitHub for repositories and issues, beginners can try to find the label of good-first-issue

I used it to find 3+ Issues on the first day of my first Hacktoberfest, which had been merged!

6. Good-first-issue sites
   Some websites help you find issues to contribute to -

   First Contributions, EddieHub Issue Finder, goodfirstissue.dev, goodfirstissues.com, firsttimersonly.com.

7. Communities
   Communities like EddieHub have several open-source projects seeking contributions!

   

Step 3: Making your first pr

This one should be pretty straightforward, it's just a simple checklist

1. I have identified where I can add value (Go back to the graph mentioning types of contributions)

2. I have found a project to contribute to (The step before this one)

3. I know basic Git & GitHub concepts (Step 1)

4. I have made a PR to EddieHubCommunity/hacktoberfest-practice to add my name to test out step 3

5. I have read the contributing guide and the code of conduct of the project (if they do not exist please do not consider contributing to that project as a first-timer)

6. Make a PR ✅

I need your help people -- I've been writing this article since a great while now, but I think I still do not have enough perspective of different people just beginning in open source. If you've got a minute or two please share how can I improve this article and include more information. Thanks!

Finally, I'd like to thank everyone who took the time to read this blog post all the way through. If you love my content, feel free to follow me on Twitter for more such memey content

GitHub Profiles have:

• A profile picture (Your Professional Headshot maybe?) A bio, your current organisation

• Your email, Twitter, website, your projects (pinned repositories)

• Badges that tell HRs in a few images about your Open Source life

• A whole contribution graph (the green squares!!!), activity graph and access to all your collaboration, communication and code/changes in the contributions you made

• The timezone, location you live in 👀

• How can anyone forget that there is a custom readme you can write for the profile!?

I've seen a shift from tech recruiters looking on a sheet of paper (your resume) to looking at your github profile, and why wouldn't they?

• Collaboration

• Communication

• Other Soft-skills Core-Skills

• Documentation/Code/Other Hard Skills

• Consistency

All of this, just one link, your github profile

Fun facto: Cool GitHub Profile = Companies come to you

Not joking, if you have an excellent github profile, companies find you - many companies are now starting to hire people after their contributions to their projects, every day I hear people get hired to companies after contributing to the company's project.

One example is me 🙋🏻 Everything I ever achieved, ever gained, ever learnt, all are credited to Open Source!

But nothing is just as simple, GitHub cannot replace your resume yet. Many recruiters would prefer a resume to have all your experiences and skills, just like they wouldn't want a designer to share their dribble, they do not want you to share your github :(

Why? Because the idea of Open Source doesn't work everywhere, there are a lot of companies that would want a sheet of paper instead of a link.

Recruiters want a summarized bullet list of all your shit, instead of a link where they have to dive to find your shit (Some people may argue that recruiters may review if the shit is elite).

Recruiters do not have time, there are 100 more people just like you, who applied to the place and if the recruiter gonna deep dive into all of them, it would be a "Wow" if you got a response within 1 month, majorly because teams usually only hire in small scales for replacing previous employs, because expansion in tech is just too fast and big.

So GitHub cannot entirely replace your resume! (yet hopefully)

But it does provide you with some job opportunities, some proof of work, some community that will uplift you, and someplace where people can view your code.

But what's more important is the learning.

With Open Source you gain:

1. Experience: By contributing to open source you get the real-world experience you need. It can accelerate your skills! This can be a treat for you, but even if you have a good amount of experience, more never hurts.

2. Soft-skills: With open source, you can grow your soft skills like collaboration, public speaking, teamwork and a lot more.

3. Knowledge: For instance, if you learnt a new programming language, you can contribute to a project using that language. You can even learn technologies while contributing to projects.

4. Impact: By contributing to popular projects you can make a huge impact on the community. But don't run for contributing to popular and big projects, it might demotivate you on the first run.

And that is a lot achieved already, a lot that can get you your first job, something that will help you grow in your career.

So Contributing to Open Source has many benefits including Job Opportunities, therefore you should still contribute to it!

Yes Microsoft, Windows and my existence in your ecosystem have run into a problem and will never restart

And also the fact that Windows restarts every time I have a deadline :/

Because Windows is also a product of Microsoft, it has:

• No privacy at all, I think they might just be sending your passwords

• Forced Edge browser every time you search on the default search

• Productivity lags if you decide to not hand all your data to Microsoft

• And yes, can't forget the file explorer search, it's the best!!!

Linux solved all of these in an instance, just look at how I am working with directories:

Some Terminologies

Linux is a Kernel

Linux is a kernel. A kernel is a program that manages hardware resources for the user. It connects the operating system to the hardware.

GNU

GNU packages are the core of the GNU operating system. GNU stands for GNU's Not Unix. It is a Unix-like operating system. It is free software—everyone can use it and redistribute it.

GNU/Linux

GNU/Linux is when GNU and Linux hold hands! Together they form a complete operating system. In the rest of the notes, we will refer to it as simply Linux.

Distribution (distro)

A Linux distribution is a packaged version of GNU/Linux. It also has additional software like package managers, desktop environments, etc.

There are many distributions of Linux. Some of the most popular ones are Ubuntu, Debian, Fedora, Arch Linux, etc

Shell

Shell is a program that takes commands and passes them to the operating system to execute.

Desktop Environment

It is the graphical user interface (GUI) of an operating system. Some of the most popular desktop environments are GNOME, KDE, Xfce, etc.

Package Manager

Microsoft Store, but one that works 😂 It helps you manage apps and binaries!

Introduction to Linux

Distributions, Linux, and GNU are all connected to the development and usage of the Linux operating system, although they refer to various parts of the overall system.

The word Linux refers to the operating system kernel, which is the foundation of the Linux system. Linus Torvalds created the Linux kernel in 1991, and it is distributed under the GNU General Public License (GPL), which allows anyone to view, modify, and distribute its source code.

GNU (an abbreviation for "GNU's Not Unix") is a project that began in 1984 to create a free, Unix-like operating system. The GNU project contains a collection of software tools and libraries that, when combined with the Linux kernel, form a full operating system.

Distributions are pre-configured versions of the Linux operating system that include the Linux kernel, GNU tools and libraries, as well as extra applications and utilities. Different organisations and communities generate and maintain these distributions, which are customised to various objectives and user groups. Ubuntu, Fedora, and Arch are some prominent Linux distributions.

To summarise, Linux refers to the operating system kernel, GNU is a project that develops tools and libraries for the Linux system, and distributions are pre-packaged versions of the Linux operating system.

History of Linux

The history of Linux and GNU is one of collaboration, innovation, and the transformative power of open-source software.

The Free Software Foundation (FSF), a collection of programmers and activists, initiated the GNU project in the early 1980s to build a free, Unix-like operating system. The GNU project published a variety of software tools and libraries over the following several years, laying the groundwork for a comprehensive operating system.

Linus Torvalds, a young Finnish computer science student, began working on his project to design a new operating system kernel in 1991. He asked for criticism and recommendations on a Usenet forum and quickly received a torrent of answers from other programmers who were interested in his project.

Torvalds and an expanding community of contributors collaborated to create the Linux kernel, which was distributed under the GNU General Public License (GPL). This enabled anybody to see, alter, and distribute the source code, paving the way for the development of a diverse variety of Linux-based operating systems known as distributions.

Today, Linux and GNU are two of the world's most popular and significant open-source initiatives. The Linux kernel is at the heart of the Linux operating system, and the GNU tools and libraries work in tandem with it to create a complete operating system. Together, Linux and GNU have had a major influence on the world of technology, inspiring and enabling cooperation and creativity among programmers and users all over the world.

Linux Distributions and how they developed?

Distributions are pre-configured versions of the Linux operating system that include the Linux kernel, GNU tools and libraries, as well as extra applications and utilities. Different organisations and communities generate and maintain these distributions, which are customised to various objectives and user groups.

The first Linux distributions appeared in the early 1990s, shortly after the Linux kernel was released. These early distributions were created by hand, utilising a collection of accessible software tools and libraries at the time. These early distributions were gradually refined and improved as the Linux kernel and accompanying tools and libraries evolved.

Linux distributions have evolved to include more software and utilities, as well as more advanced features and user-friendly interfaces.

I am not going to be an old grandpa and talk about the distributions that died even before we took birth 😅 So let's talk about the ones that are popular and you might come across:

• Debian (Parent of Ubuntu):

  

  The name "Debian" comes from the name of Ian's girlfriend at the time Debra and their name combined, Debian introduced many things like:

  1. Dpkg - Debs are a format of packages that can be installed, this is currently the most popular way to install Linux applications and can be found on most official downloads

  2. Apt - Advanced Package Tool is Debian's version of the Microsoft store, but one that works 😂 No, but seriously apt kind of sets me and a thousand other individuals what defined a good package manager

  3. Ubuntu - Yes, Debian gave birth to Ubuntu, Ubuntu is a Debian-based distribution, and everything that you find in Ubuntu is Debian-tuned best for Laptop/Desktop use cases.

• Fedora

  

  Fedora is based on the Red Hat Enterprise Linux, I am not giving Red Hat Enterprise Linux a separate section because it's enterprise and it should probably not be your first operating system 😅

  1. Fedora comes with RPM-based packages, which are different from Debian and not so common but the community have built several binaries of those missing packages to make up.

  2. Fedora promotes Flatpaks which allows even more packages to run on Fedora

  3. This is also the choice of several people who are very popular in the Linux community and me!

  4. Fedora also has 'DNF', which is their apt, but after using both, DNF is much better, beginner friendly and feels too much like npm or yarn

• Arch

  

  Arch Linux is a very cool distribution, don't get me wrong, it is very very cool. But dare not use it as your first distribution, I won't even dare use it as my 10th distribution. Arch is very much like barebone Linux, you build everything on top, so unless you are looking for a million sleepless nights, don't.

What does Linux have over other Operating Systems?

Linux is Open Source!!! Anyone can modify and distribute the source code because it is freely available. This enables a large and active developer community to contribute to the development of Linux and create a diverse set of tools and applications.

Linux is also extremely configurable, making it an excellent alternative for developers looking to customise their operating system to their exact requirements. Furthermore, Linux is well-known for its stability and dependability, making it an excellent choice for running mission-critical applications. Linux is also very scalable, which means it can run on a variety of hardware, ranging from small IoT devices to huge servers.

My desktop looks like this:

Another advantage of Linux is that it provides a diverse set of developer tools and applications, including a robust command line interface and a diverse set of programming languages and libraries. Furthermore, Linux is compatible with a wide range of software, including both open-source and proprietary applications. This makes it an excellent alternative for developers who wish to work with a diverse set of tools and technologies.

How to choose your distro?

Don't go by looks

Any Linux distro can look any way you want, do not consider looks a point, because the looks are given by the desktop environment, like

• GNOME

• KDE

• Mint

• Cinnamon

Go by features

Use them for their software base or productivity features,

I choose Fedora over Ubuntu because:

• Speed matters more than disk space for me (Snap vs Flatpak)

• I like how table Fedora is, and especially that it doesn't break 100 times a day

• The DNF package manager is holy-smokes cool and easy to use

Popular ones have been listed above and I am not one to make an impact on your choices but I recommend Fedora to all developers

Installation

Installation is guided by what distro you use. But mostly it is going to be a GUI process, I recommend having 4 partitions:

• /boot/efi - EFI system partition (Required)

• / - Root partition (Required)

• /home - Your files partition (Recommended, use btrfs for backup guarantee)

• Linux Swap Partition - Extra RAM (Recommended, double the physical RAM is always good)

Post-Install

Can't recommend anything because nothing is general for every distro google "[distribution name] setup" and you'll find many

Thanks for reading! Follow me on Twitter for more fun and tweet out your learnings: @xkrishguptaa