I used to not like review processes which slowed down my PRs to get merged and deployed to production. I remember my then CTO, Arzumy MD, during a catch-up, commenting about this issue and he guided me to understand the reason why we have to go the extra mile in the PRs we create. Some pointers that I remember were:
To set things in context, software engineering revolves around certain design/structural principles. Which help in managing all in general code-quality of the code base. This is super essential when working in a team. The size of the team is proportional to the need for such a principles.
We have a bunch of design patterns which each take care of “separation of concern” based on what a particular pattern is supposed to do. But we must not forget that the intention starts from a single line of code ⊆ function.
To get some things right straight away:
Lately, with the pandemic going on, we all have had to adjust in a certain way. I have had to create personal mental boundaries and try not to let any negative thoughts inside that enclosed space which is shielded from the rest of the world. For me the only way to create that shield which needs to be setup in the first place was to get into stoicism. I wanna share how I looked into the key principles of stoicism and applied it to my work as a software engineer and how it helps me get through my daily life…
When I saw this screen I was not that intrigued, as to what was happening, until I scrolled.
Once you scroll you see that the text color depends on the position of the text on the screen from the user’s end.
You’ll find so many similarly titled articles over the internet. Why should you read mine? I don’t know. Just like I don’t know what I will learn in the next 2 years. But I can share what I do know at the moment. Here are the carefully curated list of things I wanna share…
I have seen a lot of memes suggesting how some job-descriptions have bonkers expectations for job listings. But working professionally made me realise how big is the wisdom gap between me and a senior engineer, about a year ago. Unlike a lot of people’s belief, tech…
When the COVID 19 pandemic hit, we as a start-up had to come up with a solution for our users as well as out merchants. Now, most businesses don't have that much of a buffer to support themselves for the long term without any revenue. So we came up with a campaign to #saveourfave. During (what seemed like a hackathon) a 3 day time period. We came up with
We started with making a decision to start with :
Thanks to the product and the product design team for coming up with this idea and the…
During these uncertain times, things have been really demoralizing. And anyone who has an affinity to go work at an office has struggled really hard. Also, shout out to my extroverted buddies out there, we know it’s tough, you all will still have us to hang out with when all this is over, hopefully soon. One of the side effects of getting demoralized is that there is less drive for making something interesting, at least for me as an engineer, we love building things. I work and then side hustle and then sleep, repeat. …
Disclaimer: I'm an engineer at Fave, but the content of this post is not related to Fave, it is a side project that I am working on.
Having gone through setting up CI/CD for my small project, I realized that TDD is a pretty cool thing to have and it helps to automate stuff and also gives confidence not just to the coder but also to the reviewer.
The lead up to this blog can be found on the following blogs:
I had implemented Jest and Enzyme to set up the tests. Now, as a developer, I am interested in…
As there have been a lot of guides on the internet regarding testing and CI setup, I did run into a lot of issues(part of being an engineer). I will try to make this as helpful as possible.
CRA sucks for Jest-Enzyme testing!!
Don’t know if it’s just me or others have faced this issue as well. There is something wrong with CRA or rather webpack, which didn’t let me setup testing that easily
So in an overview, this is what CI setup process looked like in my head:
For every open-source maintainer trying to birth a repo/project for the first time, it is a tough task. For someone as noob as me, that’s a whole different ball game. But we all have to start somewhere right? Might as well.
It all started with the dilemma of how to setup CI/CD in my project. I looked into CirleCI. The only issue I have is I don't have any unit tests written. Dude! That comes with its own set of demons. But I guess that the process of learning comes with its fair share of problems.
The plan, for now…