DEV Community: Adhiraj Dutta

ESLinter - for all JavaScript projects

Adhiraj Dutta — Tue, 23 May 2023 19:25:42 +0000

What I built

I built a Github workflow that lints every pull request and checks for errors using the rules set up in the project's .eslintrc.json file. This is very useful for maintainer's as contributor's may not follow the rules setup by the project which can lead to a messy codebase that can become difficult to maintain as it scales.

Category Submission: Maintainer Must-Haves

App Link

Github repository

Description

name: eslinter

on:
  pull_request:
    branches:
      - "**"
    types: [opened]

jobs:
  linter:
    name: eslint runner
    runs-on: ubuntu-latest
    permissions:
      contents: read
      pull-requests: write
    steps:
      - uses: actions/checkout@v2
      - uses: reviewdog/action-eslint@v1
        with:
          github_token: ${{ secrets.GITHUB_TOKEN }}
          reporter: github-pr-review
          eslint_flags: "src/"

This is the simple workflow. The eslint_flags: can be changed to the specific directory required.

Link to Source Code

Github Repo

Permissive License

MIT

Background (What made you decide to build this particular app? What inspired you?)

Working on team projects where eslint is not used by someone can make the whole project messy. Implementing this action will make the lives of maintainers easier as they can rest assured that no unlinted code will be pushed to the codebase.

How I built it (How did you utilize GitHub Actions or GitHub Codespaces? Did you learn something new along the way? Pick up a new skill?)

I finally made a CI tool that will be helpful for people. This is certainly a first for me. I took help of the official docs for Github Actions and reviewdog and cooked it up in a few hours, as I only got to know about the hackathon on it's last day. A huge thank you to the awesome actions by reviewdog!
Testing it was a bit of a problem with new PRs everytime something broke. I hope there will be a way of testing actions offline in the future.

Additional Resources/Info

reviewdog

The Curious Case of 257

Adhiraj Dutta — Mon, 09 Jan 2023 15:02:29 +0000

Python has an interesting caching feature, which I discovered recently -

This is called small integer caching.

What Python does is pre-allocate a global list of integers as singletons in the range [-5, 256] during initialisation. So every time that an integer is created in this range, instead of creating a new object, a reference to the existing object is returned. Therefore it saves a lot of space and computation for commonly used integers.

This can also be seen during computations.

Another interesting byte. When initialised in the same line, the interpreter creates a new object for the first variable, and then reference the second variable with the same object. This is because the compiler can see both the variables and can optimise the referencing.

Hey wait! I am not done yet.

Another new confusing thing?

The compiler also optimises identical literals, when the code is compiled in the same code object. So, 1. If the Python compiler can see the whole code, more optimisations may apply to the code. When typing into the Python shell each line is a completely different statement, parsed, and compiled separately.

This works for floats as well, which is not cached.

Literals inside tuples and other data structures are shared as well.

Java uses a similar approach and caches the integers between -128 to 127. However this works only on autoboxing. They’re not cached if built with the constructor.

References -

Why Python is Slow: Looking Under the Hood

Python internals: Arbitrary-precision integer implementation

What's with the integer cache maintained by the interpreter?

PS: This is my first technical blog post, so any corrections and constructive criticisms are welcome!

the new next is here

Adhiraj Dutta — Fri, 28 Oct 2022 13:03:28 +0000

Hello there!

Hope everyone is doing fantastic! Duh! Why are you even so enthusiastic about anything, I hear you say. Well, I am excited because one of web's most beloved frameworks, Next.js just got its new version - 13.0.0. Announced at the Next.js conference, it lays the foundations to be dynamic without limits.

It has created a lot of noise in the developer community as the version comes packing with an alpha version of a faster bundler, called Turbopack, as well as a redesigned approach to server rendering, routing, layouts, and data fetching.

Let's talk about the new Turbopack bundler, written in Rust. It is positioned as a successor to Webpack. Offering improved speed and a better architecture, Turbopack is a build system for JavaScript and TypeScript that is designed for incremental builds. Turbopack is 700 times faster than Webpack when working with large applications, the parent company of Next, Vercel said.

We also have an enhanced version of the framework's filesystem-based routing system. It sets out to make it easy to lay out complex interfaces and maintain state across navigations, all while avoiding expensive re-renders. So now we get to save 8 seconds of build time each time we hit save xD!

The gods on the side of Next listened to our prayers and have improved on the existing Image component, making it easier to display images with less layout shift and better optimisation of files. On a similar front, there's also a new font system that automatically optimises fonts and automatically uses the CSS size-adjust property.

All's sweet as honey as we go on about the new changes. Let's have a look at what's going to break when we finally run that npm i next@latest react@latest react-dom@latest eslint-config-next@latest command -

The minimum Node.js version has been bumped from 12.22.0 to 14.0.0, since 12.x has reached end-of-life.
The minimum React version has been bumped from 17.0.2 to 18.2.0.
The swcMinify configuration property was changed from false to true.
The next/image import was renamed to next/legacy/image. The next/future/image import was renamed to next/image.
The next/link child can no longer be <a>.

Huff! That was a LOT of fanboying over a single update. See you later folks, happy deving!

How to start your coding journey

Adhiraj Dutta — Fri, 21 Oct 2022 21:06:27 +0000

This is more of a how-I-did-it post than a how-you-should-do-it post.

I first dabbled in coding in class 11 when my curriculum added in C++. I was familiar with python before but C++ was where my real coding journey began. And it has really been a roller coaster ride ever since. From pitfalls of depression to riding the waves of confidence, coding has it all. I am now a mediocre noob after much procrastination and practice.

In this post I want to share the platforms and resources that helped me a lot on this journey!

HackerRank

I joined HackerRank in class 12, during the covid period and it was my first foray in competitive programming. It is very beginner friendly and it is a very good place for beginners to start with.

CodeChef

I next jumped to CodeChef when it was still free and really good for people to start off with. I started giving contests from here. The Long Challenges are really good for noobs as the longer duration allows people to learn the topics well and apply them to solve the questions. However with the pro plans arriving and the blatant cheating during contests made me move away from this site.

Codeforces

Codeforces is very well known in the competitive programming world as "the" place for contests. It might seem a bit overwhelming for newcomers at first, but after solving a few problems you will be able to get the hang of it. Contests are held regularly every week. The level here is harder than codechef, so directly jumping here will be a bit difficult for you. Better take it slow, or else you will fall into spiral of despair which is hard to get out of.

LeetCode

LeetCode needs NO introduction. It is THE interview preparation platform. The problems here focus on algorithms more with rigorous practice for data structures like linked list, stack, queue etc which is not generally seen in other programming websites. The problem classification, study plans and weekly short contests make it a really good place to hone up your coding skills.

Neetcode is a great companion website for Leetcode. It has curated problems and their solutions from Leetcode.

One other website that focuses more on algorithms is Codewars. It will really help you in improving your coding style and help you write clean and efficient programs.

LightOJ is something I came across fairly recently and it has really good categorisation of problems. This is good for practicing certain topics and getting a better grasp at them.

Like every skill, only regular practice makes you improve. CLIST is a great place to keep track of upcoming contests. You can directly add them to your calendar from the site.

GeeksForGeeks and CP-Algorithms are really resources. Make sure to use them! However, some topics are out of scope in these websites, so make sure to use your own discretion.

The following are famous annual contests conducted by large organizations.

Google Codejam
Facebook Hackercup
Google Hashcode [This one's an optimization contest.]

Some good youtube resources are:

This is an exhaustive resource dump. Do not get overwhelmed. Just refer these when you need help. Everyone's way of learning and understanding is different. Explore and try to find the suitable way that will help you the most. I will keep updating the blog post as I get older and wiser.

Happy learning!