Two months Intern to an Amazonian !

RITIKA SINGH — Fri, 28 Oct 2022 07:07:20 +0000

Amazon has always been my dream company. From fighting to pass all the test cases in the online Assessment to becoming an intern and then finally an amazonian , my journey has been stupendous.

I did a 2 months Software Developer Engineer Intern in Amazon ADS , Bengaluru India.

So here are some myths and some procedures that one can follow to improve exponentially in your work while interning at Amazon.

Lets start with some interesting myths that I came across.

You can't get a Pre-Placement Offer from a 2 months intern. (like dude why?)
People selected from Amazon WOW [a diversity hiring programme at Amazon] get less stipend.
You can't prove in 2 months internship.

Reality:

Hard work and determination are self-sufficient to clear the haze created by the above myths.

Now coming to the most important part , The points to remember while interning :

Prepare Git and AWS in advance (or just get a glimpse of them)
Try to have command in Java ( or any other language but make sure you are clear with all the core concepts. )
Develop a habit to read and learn (in industries it's the blogs of your teammates that are actually a saviour when you have crashed the production 😅)
In any big tech I feel that documenting should be a knack for you .( keep documenting what all you learned each day or per 3 days )
Documenting will help you in analysing your progress , and of course any other person (say the bar raiser) will get a clear idea of your hard work.
Be attentive while attending meetings ( as in ask doubts make notes , be aware that on what other teammates are working , etc).
If you are facing any problems try contacting your mentor or any teammate and get the blocker solved ASAP!
Actively take feedback from other team-mates [write down the things you have to improve and set an achievable deadline for the same]
In the first two weeks of your internship , setup a 1:1 connect with all your teammates . (doing this will help you connect and understand the work of your team , including tech-stacks , objective of the products , flow of information , etc)
Develop a habit to convert the flow of your code into graphs or flow charts that can be presented to anyone in the future which will help others understand what your code actually does , what services you have used , the flow of information between the services , etc.

Just be active and do hard work you will get to your goal.. 😊

You can also reach out to me on LinkedIn , Twitter , GitHub.

GitHub Actions : Zero to Hero

RITIKA SINGH — Sat, 08 Oct 2022 05:51:16 +0000

What Are Github Actions?

GitHub Actions are packaged scripts to automate tasks in a software development workflow in GitHub.

That is all the processes (or GitHub Events) like the creation of a pull request, committing your code, pushing into the production/ any branch, etc can be monitored by GitHub actions, and hence when an event occurs the workflow is triggered.

Github Actions Workflow

A GitHub Actions Workflow is a process that you set up in your repository to automate software development life cycle tasks. It is a configurable automated process made up of one or more jobs.

Each repository has this actions tab in which the defined actions run :

One must create a YAML file to define the workflow configuration. If you’re new to YAML and want to learn more, see Learn YAML in Y minutes.

GitHub actions are categorized as Container actions and JavaScript actions.

Container actions
As the name suggests in container actions, the environment is part of the action’s code. These actions can only be executed in Linux-based runners that GitHub hosts. Or if one wants to create a Self -hosted runner (read about runners) make sure it uses Linux OS and has Docker installed. Container actions support many different languages for execution.

JavaScript actions
They do not include the environment in the code. This means that one has to specify the environment to execute these actions. They can run in a VM in the cloud or on-premises. They not only support Linux but macOS and Windows environments also.

Let’s Start by Creating A Simple Workflow:

Create a new repository and then create a workflow (say action.yml) in the workflows folder so the final path of your workflow will be like .github/workflows/action.yml
Now, our first job is to add the on and name attribute to our workflow.

name: defines the name of your workflow.
on: defines the event on which the workflow has to be triggered.

There are plenty of Github events that trigger any workflow (read about GitHub events that trigger workflows)

Next essential requirement of a workflow is the job that it has to do (a workflow has to have a minimum of one job!)
One can define multiple jobs for a workflow. Each job has sundry attributes the major are name, runs-on, steps.

name: defines the name of that particular job in a workflow.
runs-on: defines the runner of that job. (runner can be a Github Hosted Runner or a self-hosted Runner)
steps: defines the steps to be taken in that job.

5 . Commit the code, open the Actions tab in your repository and see your actions running!

So here you can see that all your jobs in the action.yml file ran successfully. And our job named custom3 (line 38) ran and gave us a DateTime output!

And Done! Aren’t GitHub Actions cool 😎!

Let me know in the comments if you have any doubts or face issues, hope it helps you. 😀

Do check out my session on Git & GitHub actions : (Jump to 17:17 for the real fun 😉)

You can also reach out to me on LinkedIn , Twitter , GitHub.

Forem: RITIKA SINGH

Two months Intern to an Amazonian !

GitHub Actions : Zero to Hero

What Are Github Actions?

Github Actions Workflow