DEV Community: Abhay Katheria

Shogun Coders Dojo

Abhay Katheria — Tue, 22 Feb 2022 05:43:18 +0000

Last year a buzzword that later turned into an art revolution came into the picture. NFT's or Non Fungible Tokens are now becoming a household name.
So my friend and I decided to launch an NFT project just for programmers. We present to you shogun coders dojo. A collection of 30 unique NFT's which represent a particular language or framework.
You can own one to show off your skills.

Shogun Coders Dojo

@codersdojo

Buy Now on -
opensea.io/collection/sho…

#NFTartist #nftart #art #digitalart #nfts #nftartist #crypto #cryptoart #nftcommunity #nftcollector #ethereum #bitcoin #blockchain #cryptocurrency #opensea #artist #eth #nftcollectors #cryptoartist #nftdrop #nftcollectibles #openseanft

08:40 AM - 20 Feb 2022

We also intend to provide custom NFTs on-demand with a nominal fee in the future.

You can buy the collection at opensea.

LFX mentorship @ Vitess

Abhay Katheria — Thu, 18 Nov 2021 12:10:43 +0000

This summer I was fortunate enough to be selected as linux foundation mentee for Vitess which is a CNCF graduated project.
According to vitess.io

Vitess is a database clustering system for horizontal scaling of MySQL through generalized sharding.

Sharding is the concept of breaking up data into smaller chunks distributed across separate database nodes.

My aim for the summer was to develop an exhaustive test suite for Vitess's compatibility with Django's model layer.

During this period, I was mentored by a team of engineers from Planetscale who are currently maintaining Vitess. I was part of daily stand-up meetings and was in constant touch with my mentors, who guided me through the whole project. Also I got a chance to be part of community-day for Vitess in which contributors and maintainers from all around the world interacted.

Sadly, due to an unfortunate event I was unable to work for weeks. But my mentors and the admins at CNCF were kind enough to understand my situation and granted me an extension for the program. And with the help of my mentors i was able to complete the project within the extended deadline.

I learnt a lot during this mentorship program and will continue to contribute more to the project in future.

A noobs guide to Google Summer of Code.

Abhay Katheria — Mon, 28 Sep 2020 05:20:03 +0000

Heya fellas,
In this blog post, I will try to put down my learnings of getting selected in google summer of code 2020, to give you some idea about how to move forward in the right direction.

So if you don't know about GSoC let me summarize it for you.

Google selects about 200 open-source organizations every year to be part of GSoC.

The aim is to promote open-source among students.

Students are encouraged to contribute and give a proposal to make these projects of these orgs better. Ideas can be their own or pre-selected by the org.

On successful selection, students work during the summer on their proposed ideas. And receive a stipend of 3000 USD (stipend varies year to year and from country to country)

Now to the main part. How to get selected, Sir ..?

The logic behind selection in GSoC is straight pretty straight forward -
the more you contribute the org the better are your chances of getting selected in that org.

So before you start contributing to an org.

You need to know how to contribute and in which org to contribute.

Apart from being comfortable in the language/framework of your choice, you need to be a master of git.

And learning git is the easiest part of the journey. The best way to learn git is by getting your hands dirty. There are very good resources on the internet to learn hands-on. I will give a link to a repository http://github.com/nishakm/puns. You can find the guide to use git and best practices here.
Try to add new puns file open Pull requests get your hands dirty.

Now searching for an org is a different game itself.

Choosing an org mostly depends on what tech stack you currently know and how much you are willing to learn. So from my experience, I classify orgs on 2 basis.

Orgs that uses existing Frameworks like react Django etc. to build and maintain existing applications like AOSSIE, FOSSASIA, SUGAR-LABS, SCORE-LABS etc.

Hardcore Orgs like which have existing large codebases like Mozilla, Django, TensorFlow, Flutter etc.

Contributing to the former is beginner-friendly as there is a plethora of learning material available online about these frameworks and you can understand their codebase more easily. But the competition is also fierce here and some nepotism is also seen here like students of X college are preferred by the mentors who were/are students of X college. Its something to watch out for. Selection in any org depends on how much you have contributed before gsoc to that org. Students mostly start around november. Also, maintainers are somewhat less active as most of these apps never see the production. But again it's far easier to read the codebase once you learn the used tech stack. And if you have enough merged PR's you will be selected.

The second type of orgs have codebases of 10s of thousands of lines and are written in languages you are most familiar with like C++, JAVA, Kotlin, python. But far too advanced to understand without maintainers help. On the bright side, their maintainers are really active and are very supportive and even solve your silliest doubts but you have to work really hard to map the working of the codebase and solve bugs.
And believe me, even making a local build for development is also challenging 😛.
Do read the documentation......

So the key to getting selected is communicating with the maintainers just select any org and join their gitter, slack or Irc channel or mailing list and just ask them where you get stuck if they don't reply and move on to the next org.

work smart and fast

TERN - Inspect thy docker image

Abhay Katheria — Fri, 03 Apr 2020 03:06:35 +0000

Docker is a commonly heard buzzword these days. Almost every major project on GitHub is now using docker. opensource.com summarizes docker as -

Docker is a tool designed to make it easier to
create, deploy, and run applications by using containers.

What are containers then?

According to wikipedia

Containers offer operating-system-level virtualization through a virtual environment that has its own process and network space, instead of creating a full-fledged virtual machine.

All container images have some sort of dependency chain associated with them. Suppose you are creating a container based on the mongo-DB base image. You might be familiar with the packages that you installed on top of the mongo-DB base image, but likely won’t know anything about the dependencies that the mongo-DB base image brings with it. Creating a software bill of materials (SBoM) can help you make better decisions about your container-based infrastructure, integration, and deployment strategies.
Or, maybe you are just curious about the contents of the image you are using such as what packages are installed in it and which licenses govern those packages.

Well then tern comes to the rescue.

Tern is an open-source container inspection tool for containers. Tern is currently available as a pip package but can also be cloned from its GitHub repository. The installation is straight-forward but it does require Docker to be installed on the host machine.

Linux users can find installation instructions here
Windows and mac users can find installation instructions here

Once you've set up tern you can start inspecting docker images and dockerfiles.

To inspect locally pulled docker images or images available on DockerHub.

tern report -i debian:jessie

To inspect local Dockerfiles.

tern report -d path/to/Dockerfile

Tern creates SBoM reports suitable to read over or to provide another tool for consumption. Currently, supported report formats are :

summary (default)
json
yaml
SPDX tag-value

You can read more about them here.

Another thing that makes Tern special, is the beginner-friendly documentation, code readability, and community support. The maintainers are super active and respond to the issues raised very frequently. Also, you can raise your issue on the slack channel or get help if you feel stuck anywhere. The team is super friendly and responsive. I am a contributor at Tern now and I can say all this from personal experience.

This is my very first article hope you guys like it. I didn't want to make it too long if you guys want a more detailed article comment below. I would like to thank rose from Tern team for helping me out with this article

Do checkout tern's github repo.