DEV Community: Aakansha Doshi

Announcing Canvas X React Workshop in January 2025

Aakansha Doshi — Tue, 26 Nov 2024 15:18:00 +0000

My Canvas Journey: From Novice to Builder

Canvas often feels like a mystery box - we use tools built on top of canvas, but few of us truly understand how it works. If you're a JavaScript developer, this might sound familiar 😊.

Back in May 2020, when I was at HackerRank and we were looking for a whiteboard to integrate, we chose Excalidraw for its simplicity after reviewing many options.

Back then, I was very familiar with React, Webpack, and other tools as I used them daily at work. So, I proposed to the excalidraw team that we could build an npm package.

Since Excalidraw was at a very early stage and supporting the npm package would introduce a huge change in the codebase, it took me some time to convince them. Meanwhile, I forked the repo, and we shipped the editor at HackerRank.

However, I was aware of the nightmare it would introduce to keep the forked codebase up to date if we don’t push the changes to the base repository so I was having back-and-forth conversations with the Excalidraw team regarding the npm package.

Finally, after ~8 months, WE DID IT! This was my AHA moment! Thus, I started maintaining the npm package.

However, I knew nothing about Canvas, but I was really curious about how these drawing tools worked inside. It seemed so cool that you could draw any shape and interact with it.

As a maintainer of the NPM package, I had the chance to dive deep into the codebase. However, the canvas was still a puzzle I was trying to solve.

Over time I learned a lot (I am still learning as learning can never end :p) and started building core canvas features, some of which were Text containers, Labeled arrows, adding points in line segments, hyperlinks, and more, and every time I realized there weren’t enough resources on the web about Canvas.

Why this workshop?

Besides my passion for open source, I love sharing what I've learned and experienced. As there aren’t enough resources on the web regarding Canvas, I want to make it more accessible so anyone can easily learn about it.

That's how I started speaking at conferences three years ago. I always aim to share my insights in my talks, and I enjoy doing it.

I’ve delivered talks and podcasts on Canvas, where I discuss building features like text containers, labeled arrows, and other whiteboard functionalities, along with how they are implemented in Excalidraw. You can check out my talks and podcasts (I will be adding the 2024 ones soon).

While giving these talks, I noticed that although not many people explore Canvas-related topics, the audience is curious and enjoys learning about the unknown and how things work behind the scenes. This inspired me to do it even more!

Since then I wanted to dive in one level deeper and do a workshop where we not only dive into the concepts but also build this stuff together - yes that’s the IDEA - A deep dive Hands-on workshop where we start from the basics and deep dive into internals turning these implementations into reality.

I have been thinking of doing this workshop for months and years. Last year I gave a workshop about “Building a whiteboard from scratch” at React Alicante and wanted to do more. But I couldn’t prioritize it but why am I finally doing it?

Recently at React India in Goa, Tejas and I were having a casual conversation, and suddenly this topic came up: "Hey Aakansha, why don’t you run a workshop on Canvas?", I replied, "Really? Do you think people will be interested? I have been thinking about this for a long time".

Tejas is an awesome community member and an amazing friend. He strongly encouraged me to go for it, and the following week, I launched the website with the workshop announcement✨.

Hence here I am doing the workshop On January 25, 2025.

What will you learn?

The workshop will start with the basics, keeping it beginner-friendly, right from how to render the Canvas and then take a deep dive into the internals.

And the best part is it’s not just theory but lots and lots of hands-on. Here is a quick overview 👇

HTML Canvas Fundamentals - Learn how to use Canvas APIs for drawing shapes and paths. This will ensure the workshop is completely beginner friendly and slowly we deep deeper into internals.
Hit Testing and Interactive Canvas - Have you wondered how user interactions work in Canvas? To understand this will be diving into techniques like Hit Testing to enable the selection, movement, and resizing of Canvas shapes.
Navigating the Infinite Canvas - Building Infinite Canvas and learning how to manage the viewport to make it interactive. This might be your favorite part as everyone loves endless Canvases, isn’t it?
Text and HTML Rendering - Rendering Text in Canvas and making it interactive with HTML elements. This might sound simple but there is a lot to explore when it comes to text rendering and making it in sync with the HTML Input element used for updating the text element.
Performance Optimizations - Learn how to improve performance with complex Canvas applications. During the workshop, we will come across cases where we need to improve the performance for rendering the Canvas shapes and this will help us understand the techniques which can be used to improve the performance of Canvas-based applications.
Build a Mini Whiteboard - This is the best part as together, we will build a mini Canvas-based whiteboard editor using all the concepts learned above.

You can find more details about my workshop here.

Register with an Early bird discount

If any of this sounds interesting and exciting to you, sign up for my workshop with a special early bird discount of 40%. I would love to see you there!.

If you know someone who might be interested, please do share it with them :).

Since it's a live workshop, seats are limited, so the sooner you register, the better :). The recordings will also be provided after the workshop.

I am still working on the exact time of the workshop, based on the registrants across the world and I will soon share more details on the same.

If you have any questions or suggestions, please comment or contact me on LinkedIn, Twitter, or Bluesky. I'd love to hear from you!

If anything is stopping you from joining the workshop, my DMs are open. Let me know, and I'll do my best to help :)

Closing thoughts

I am very excited about the workshop. I'm learning a lot during this process, though I must admit some things are quite challenging! I will document all my learnings and experiences from this workshop.

Until then, goodbye and have a great day and see you soon!

My First Talk

Aakansha Doshi — Sun, 11 Sep 2022 13:56:44 +0000

Hello everyone 👋🏻. The "First" in everything we do has its own importance, isn't it? Throughout my career, I have mentored a lot of people and I have seen this hesitation in a lot of them too to get started with public speaking. I believe it's very natural and all of us faced this at some stage. So why exactly am I writing this blog? Well, I am one of you who always had hesitation, stage fear, and self-doubt about getting started with public speaking! How does one exactly start to give talks? Should I actually give a talk? Should I submit CFP? What if it doesn't get selected? And a lot more of these kinda questions crossed my mind and I always resisted to start speaking. I have given a few talks till now but The First Four Talks I gave have been very special for me and each with different learning. In this blog, I will share my experience of my First talk and I am sure a lot of you will be able to relate to it as well 😊

Convincing myself

I wanted to start giving talks but I was too worried and self-doubting about how and where to start. This is very natural and must be happening to most of us. I was working at HackerRank and as part of the quarterly review, this was one of the feedback I had gotten multiple times as well that I should start giving talks!

In 2019 I finally decided to put it as one of my goals on my personal road map. Till now I had no idea what topic, or where to give but yeah I wanted to start to finally be able to break this ice.

Deciding the topic

There were a couple of topics like Testing, Code review, React related topics in my mind but I wasn't sure which to pick as I was totally confused. I had been reading "You don't know JS" By Kyle Sympson and I just the book.

So I thought let me try giving a talk about Scope as I was very inspired with the way Kyle approaches a topic and conveys it to the audience.

After a number of iterations, I finally decided on the talk title Do you understand Scope in Javascript ?.

Where should I give the talk?

The option to give a talk at the office was always there. We used to have Tech talks every Friday but here is one theory that I believe in since I was so anxious about giving the talk and also worried about what will happen if something goes wrong. I was worried about how will I face my colleagues so I decided to give my first talk outside where less / no one will know me and it might be easier for me to give the talk then as I would have less pressure.

Submitting the CFP

Since I decided to give my talk outside the office, I started to look for places that I could explore. Bangalore is a very active place with meetups and you will pretty much find meetups for all categories. So I came across ReactJS Bangalore Meetup and decided to submit my CFP in this one. It took me a lot of courage to submit my first CFP and finally submitted the topic for September 2019 meetup. It's weird that though I was aware I am not going to lose anything if the CFP gets rejected but still I don't know why I had this fear of rejection 😞. Well Within an hour I get a reply from Kiran (the organizer of the meetup)

And reading this I was shocked, happy, excited..... all mixed emotions! But of course, I wasn't ready to give it in just a few days. So I had to come up with an excuse that I might not be available on the coming Saturday and hence submitted it for the next month's meetup. Sorry Kiran if you are reading this, I am sure you will understand 😃.

And now I was the first speaker for the September meetup. So this was First Talk + First speaker!

Preparing the talk

I started looking into how to prepare talk slides, the format, and template everything during the weekends. I had almost a month so I thought I have a lot of time so I went on a slow pace until I had just one week to go.

Probably that's how most of us "Devs" function 😂 ? So finally I had the draft ready (well I thought it was ready :p)

Reviewing the slides

Since this was my first talk I wanted to get it reviewed and fortunately I had mentors at HackerRank whom I could always reach out to for any assistance. So I started getting it reviewed from Sudhanshu, Akshay, and Hari.

A couple of important points I received as feedback

When talking about a broad topic - better to have an Agenda so the audience knows what I am going to cover
Slide for Takeaways from the talk towards the end
Font size big enough to be visible
Not too much content on a slide and better to have bullet points
Don't write on the slide what you are going to speak to avoid repetition
Avoid grammatical errors

So I started working on the feedback and the slides were mostly ready by now. I had 2 days to go before my talk.

One day to go

It was Friday late evening and my talk was the next day but I hadn't practiced in front of anyone so I tried practicing in front of a few of my colleagues at HackerRank so I could gain some confidence.

A few important things I got to know when practicing was

As the topic name was "Do you understand Scope in Javascript" - give a brief outline of "Scope" being one of the trickiest yet important concepts to understand
I was speaking at a fast pace so take a pause in between
Ask the audience if they have any questions

One good thing I liked about my talk is I tried to make it interactive by asking questions so that I can engage people. Practicing with my colleagues really helped me in gaining confidence. I know I should have rehearsed a few days earlier but I am glad that I managed to practice before giving the talk.

The night before the talk was just crazy, I was still making changes in my slides, tweaking design, and whatnot! This I think is normal when it comes to giving talks 😂. I still don't remember If I slept that night, it was too much anxiety 😨

The talk day

I got ready and left for the venue. It was 21st September 2019 and my talk was the first one at 2 pm IST. I left with my partner and reached the venue and we waited for some time for people to join in. Harshith, one of my close friends, and Hari also came to attend my talk and this boosted my confidence to a great extent. And then yes the moment came and I started my talk. As I started speaking for the first couple of seconds I was very conscious but then I just went with the flow and it actually went well 😍 The audience was very interactive, after my talk as well I got a couple of questions and during break time as well I interacted with a lot of folks, got a lot of valuable feedback, and had a great great time.

The AHA moment 😍

I was so so relieved, it was no less than winning a war 😂. I had decided that if my talk went well, I will party so in the evening I was ordering some dessert to celebrate and suddenly I get a notification 🔔

https://twitter.com/kiran_abburi/status/1175420141196021761

This made my entire day and I was so so exhilarated that I can't put that into words! Kiran is such an incredible person and this coming from him was really a huge thing and motivated me so much.

Thank you 🙏

I am fortunate to have a few people in my life who always support me and push me to go beyond my limits. Throughout my career, there is one person Hari who has always pushed me to do better. My family has always been very supportive and always been there whenever I needed it.

You can find the list of my talks here and more coming soon 😊.

So yes this was my first talk experience, and as I said "First" talk is always special. Would like to know your experience so share them below If you haven't yet written then write it, it's never late 🙂.

Hacking Javascript Objects - I

Aakansha Doshi — Mon, 18 Jul 2022 17:07:04 +0000

Most of us deal with Objects pretty much every day and it's one of the most commonly used data structures. But few of us might know that it's also possible to control the behaviour of the properties in an object or you can say "Hack" the properties of Objects 😂.

In this post, we will be diving into some of the internals of the Objects that can help in achieving the same and we will also have a fun Quiz towards the end of the post 😉.

Before we dive into the internals of object, let's start with some basics.

What are objects?

Objects are a collection of properties where each property has a key and a value.

Objects can be created in three forms👇🏻

The literal notation with curly braces {}. This is the most commonly used syntax.
Using the Object constructor. Object class represents one of the data structures in Javascript. There would be hardly any need to use this form when creating objects but still good to know 🙂
We will not be going into details about the third form but will share it later in this post 🙂

Customising the behaviour of properties in an object

So it's fairly easy to get started with objects, but here comes the interesting fact, it's also possible to customise the behaviour of the properties in an object.

Let's see what all customisations are possible 👀.

Object class has a static method defineProperty which allows to add a new property or update an existing property of an object and also control the behaviour of the property. The static properties are directly accessed using the class, instances need not be created to access the static properties.

Object.defineProperty

Usage

Object.defineProperty(obj, property, descriptor)

obj: The object whose properties need to be updated.
property: Name or Symbol of the property which needs to be added/updated. Since Symbol is not covered in this post so we will be using Name.
descriptor: An object denoting the attributes for the property. This is going to help us in controlling the behaviour of a property in an object 😉. Going further we will be referring to these attributes as descriptors.

There are two types of descriptors

Data Descriptors - The property descriptor has a value and may or may not be modifiable.
Accessor Descriptors - The property descriptor has get and set methods with which the value of the property can be retrieved and updated respectively.

Data descriptors

`Name`	`Type`	`Default`	`Description`
`value`	Any valid javascript type	`undefined`	This denotes the value of the `property`. Defaults to `undefined`.
`writeable`	`boolean`	`true`	Implies whether the `value` of the `property` can be updated with an `assignment operator(=)`.

value

This denotes the value of the property. Defaults to undefined.

var myObj = Object.defineProperty({}, 'id', { value: 1 }); // value is passed
console.log(myObj); // { id: 1 }
myObj = Object.defineProperty({}, 'id', {}); // value not passed
console.log(myObj); // {id: undefined}

writeable

Implies whether the value of the property can be updated with an assignment operator(=). Defaults to true.

// writeable will be set to true since not passed
var myObj = Object.defineProperty({}, 'id', { value: 1 }); 
myObj.id = 10;
myObj.id; // 10

// writeable is false
myObj = Object.defineProperty({}, 'id', { value: 1, writeable: false }); 
myObj.id = 10;
myObj.id; // 1, as the value couldn't be updated

Accessor descriptors

`Name`	`Type`	`Default`	`Description`
`get`	`function`	`undefined`	A `function` which returns the `value` of the property. This `function` gets called when the property is accessed.
`set`	`function`	`undefined`	A `function` which sets the `value` of the `property`. This function gets called when the property value is set using `assignment operator(=)`.

get

A function returns the value of the property. This function gets called when the property is accessed using dot(.) or square brackets([]).

var myObj = Object.defineProperty({}, 'id', {get: () => 10 });
myObj.id // 10

set

A function that sets the value of the property. This function gets called when the property value is set using assignment operator(=).

var myObj = Object.defineProperty({}, "id", { set: (val) => (id = val) });
myObj.id = 20;
myObj.id = 20;

myObj = Object.defineProperty({}, "id", {
  set: (val) => (id = val),
  get: () => id,
});
myObj.id = 20;
myObj.id; // 20

Note: An object can have either Data Descriptors or Accessor Descriptors but not both.

myObj = Object.defineProperty({}, 'id', { value: 10, set:() => id = 10 });
// Throws error as we are using both Data and Accessor descriptors
// value is a Data descriptor whereas set is an accessor descriptor

Additional attributes for descriptors

Apart from data descriptors and accessor descriptors, there are additional attributes common to both the descriptors👇🏻 that can be used to control the behavior as well.

Name	Type	Default	Description
`configurable`	`boolean`	`false`	Implies whether the property can be deleted from the object.
`enumerable`	`boolean`	`false`	Implies whether the property will show during `enumeration` of the keys of the object.

configurable

Implies whether the property can be deleted from the object. Defaults to false.

var myObj = Object.defineProperty({}, 'id', { value: 10 });
delete myObj.id
myObj // { id: 10 } as its not configurable

myObj = Object.defineProperty({}, 'id', { value: 10, configurable: true });
delete myObj.id
myObj // {} as its configurable

enumerable

Implies whether the property will show during enumeration of the keys of the object eg when using Object.keys or for...in. Defaults to false.

var myObj = Object.defineProperty({}, 'id', { value: 10 });
Object.keys(myObj) // [] as the key "id" is not enumerable

myObj = Object.defineProperty({}, 'id', { value: 10, enumerable: true });
Object.keys(myObj) // ["id"] as the key "id" is enumerable

For updating multiple properties, we can use Object.defineProperties.

Object.defineProperties(obj, {
  property1: descriptor,
  property2: descriptor
});

As mentioned earlier, there is a third way to create an object as well and that is Object.create which helps to create an object with the specified prototype object and descriptors.

Now since you know about the descriptors with the help of which the behavior of the properties can be controlled, can you guess why 👇🏻 is possible?

var myObj = { id : 10 };
myObj.id; // 10
myObj.id = 100;
myObj.id; // 100
Object.keys(id); // ["id"];
delete myObj.id
myObj; // {}

This means when the objects are created using literal notation / Object() constructor or even a new property is added via assignment operator(.), the descriptors are set to 👇🏻

Name	Value
`value`	The value which is set when creating / updating the object.
`writeable`	`true`, hence update is possible
`enumerable`	`true`, hence the keys are enumerable
`configurable`	`true`, hence `delete` works

Retrieve descriptors of an existing Object?

Using descriptors we have a lot more control, but there should be some way to retrieve the descriptors of properties in an existing object as well. Well yes, there is a static method getOwnPropertyDescriptor in the Object class which helps in achieving the same 😍.

Object.getOwnPropertyDescriptor

Usage

Object.getOwnPropertyDescriptor(obj, property)

obj: The object whose property descriptors need to be retrieved.
property: Name or Symbol of the property whose descriptors needs to be retrieved. Since Symbol is not covered in this post so we will be using Name.

var myObj = { id: 10 };
Object.getOwnPropertyDescriptor(myObj, 'id')// {value: 10, writable: true, enumerable: true, configurable: true}

To retrieve descriptors of all properties of an object we can use Object.getOwnPropertyDescriptors

Object.getOwnPropertyDescriptors(obj)

Quiz time

It's time to have some fun quiz now 😉. Take the quiz here . Good luck!

Closing Thoughts

If you have used some of the methods like Object.freeze, Object.sealed, now you know what it does behind the scenes 🙂, it modifies the descriptors for the properties of the object.

Most of the time these utilities do help but there might be cases where you want more control over the properties and that's where you will need to use it. Hope you enjoyed the post 😍.

My Journey from a novice to a Front-end Engineer

Aakansha Doshi — Sun, 27 Jun 2021 15:32:33 +0000

How? How exactly does one start a damn Blog?!??? Maybe I should introduce myself. Maybe I can jump in straight away and talk about... No, the introduction sounds better! CLEARLY, I AIN'T A PRO AT WRITING BLOGS 😆, but I do write code though 😂. I have a story to share, one I believe many of you will be able to resonate with!

Here's me Aakansha Doshi, venturing yet again into something new. Blogging. This is my first blog. And why exactly am I writing this? Ummmm... At work, I have gotten the opportunity to interview and mentor people, and looking back I could relate to many of them. I could relate to what they were feeling, the anxiety, the excitement, and the curiosity of the unknown. I want to be able to share my journey today so that someone, somewhere, reading this can relate to it, and feel "It's okay, I am doing fine". It's great to be able to walk down memory lane and give myself a pat on the back. Sometimes we need to give ourselves credit. It's good to be reminded of the path, of the journey, completed, and of the long road, that still lies ahead!

Background

I was never sure of what I wanted to do. I was confused amongst various subjects like Computer, Mathematics, and Chemistry during my school days. Engineering was never in my mind but my friends pushed me to give the entrance exams. So, I went for it.

It takes years to prepare and get a decent rank to get into good engineering colleges. Since I had given only 2 months for the preparation I had no hopes. Nevertheless, I wanted to do something with Computers so I decided on BCA, but things turned out differently. As per my rank in the entrance exams, I managed to get into one of the private engineering colleges.

College Life

I hardly knew anything about web development in my college days! To be honest, I was one of those 'studious' students whose only goal was to score a good CGPA thereby securing a job at a decent software company. There were very few MNCs like TCS, Infosys, IBM which use to visit our college for campus. Fortunately, I got placed at TCS, but I always wanted to join a startup so I can get more exposure. Hence I started browsing about the prerequisites required to be able to get into a good startup. And, the first thing was A good understanding of Data Structures And Algorithms. I knew the theory as I had studied that as part of the college syllabus but wasn't sure about how to implement it. So I started browsing how to improve my DS/Algo skills and came across few platforms where I started practicing 24*7 on each DS/Algo topic during my 4th year. A few of those platforms are listed 👇🏻

Participating in contests and code sprints became an addiction for me. As a result, my college grades started deteriorating but I WAS ENJOYING CODING 😊.

How I became a challenge curator

One day after participating in HackerRank EpiCode where I ranked 638/5855, I received an email from Hari, The CTO of HackerRank and thereby my interview process began. As I had started competitive coding only a few months back, I lacked confidence! And there was a lot to learn but there was no harm in trying since I had nothing to lose😉.

Fortunately, I cleared my first round where I was asked to solve a challenge with one of the graph search algorithms. The next round with Hari didn't go very well as I didn't have any experience/projects to show as a developer but luckily, there was a requirement for a Challenge Curator and that sounded interesting to me so I decided to move ahead.

The role of a challenge Curator is to create challenges based on different DS/Algo/frameworks, etc topics that could be used in contests and hiring as well. Few interviews went well, few didn't and I was aware that I had so much to learn and improve in lots of areas.

Finally, I got the offer! Since I was not technically very strong for the role, I was put on probation for 6 months, and if everything was to go well I would be then hired as a full-time.

You might be wondering even though not being technically very strong for the role, why was I offered probation? The interviewers noticed my persistent efforts and were quite impressed! And woopie I got the offer. I started learning, practicing extensively, and finally got converted to a full-time Challenge Curator after 6 months.

🤔 about Development

Everything was going smoothly but soon after a year, I started getting inclined towards web development. I didn't even know how to use git properly, so that was the first step as that's where the code base resides. The culture at HackerRank has always been amazing and everyone has always been amicable. I started picking up small tasks- mostly bug fixes in the back-end(Ruby on Rails) at HackerRank to get an overview of the codebase in my leisure time.

Moving to Development

I continued taking dev tasks on the side even though it sometimes affected my performance review as a curator but I wanted to move to development soon, so I had to take the risk.

Hari always gave me side projects to work on especially during weekends so I could progress faster. Things were difficult during this time but soon after a year, I got the opportunity to be interviewed for a fresher(backend) at HackerRank. To be honest the interview went 'Okayish' so I wasn't sure if I will get a chance to move to the dev team. It was a full pressure situation and I wasn't sure what would be my next step if I get rejected.

And guess what- I was not rejected and was moved to the dev team in April 2017.

Bad times

Being a part of the Dev team I thought things would get easier but it was the other way round. My first project was to rewrite one of the routes from backbone to react. I had an overall idea about react since I had to create react challenges as part of previous role. Of course, that wasn't enough to rewrite an entire route! The next step was to start learning react, redux in-depth and the courses by Stephen Grider at udemy really helped me in understanding react. This was a big rewrite (~4k lines of code) and the deadline was getting nearer, and I was not even close to completing it. I was trying hard to finish it as soon as possible and ended up getting fully burned out for months. Can you guess the number of comments on my pull request? Let me give you a hint, it broke github, and even today if I open the pull request it doesn't load 😂

Ok, I will tell you it was ~500 comments 😱

After ~9 months my code went to prod. It took ~3 quarters to finish this which was earlier estimated to within 1 quarter. Due to my poor performance, my appraisal didn't go well. This year had been very difficult for me. More so because of the doubts, I had inflicted upon my own self.

Critical Feedbacks

I had received a lot of critical feedback when working on the previous project. Trust me on this- critical feedbacks if taken in the right spirit can get the best out of you. And it really helped me in my journey.

Learn to Debug

As I tried to finish the project faster, I became further dependent on others rather than learning to do it myself. This doesn't mean you shouldn't take help but first, one needs to try on their own. This is the only way one would become independent, and let me tell you the joy of fixing it yourself is priceless😍.

Planning before Implementation

I was trying to jump into implementation even before thinking how I should be breaking it into components, what should be the flow etc. It's ok to take more time to complete the task instead of finishing it in haste. No one is going to judge you based on that, rather if you take a little buffer and finish it before time then it would be commendable. Remember to take some time in planning so you estimate better as well as, execute it well.

Have 💪 Basics

I was lacking basics and that was causing trouble in understanding the core concepts. So I started fixing my basics first and You don't know JS by Kyle Simpson, there is also an online version for the same. These are the best series of books for anyone who wants to get into the core of Javascript from basic to advanced as it assumes you are a complete beginner.

Persistence

I started working on all my weaknesses and aimed towards becoming a better developer. Soon within a year, I had shown a significant amount of improvement. I also took the responsibility to set the right coding standards and high coverage. Everything went well and I was promoted to SDE 2 by next year. I started mentoring my juniors, leading more projects and executed them well. I was applauded for being so hands-on and taking complete ownership of the projects I was working on. Soon I was promoted to Senior Software Engineer.

The most important realization for me was that I need to have the right amount of patience. Only then can I ensure my understanding of the core and thereby plan, and execute things accordingly. It's never too late to learn or start with something new. The time you start is always the right time 😊

OpenSource

Contributing to OSS is something that has always helped me grow professionally and personally. There is a lot of exposure and learning you get while working with the community. And once you start contributing, trust me you will get addicted to it . I will soon write a blog on how opensource helped me become a better developer.

Well, this is how my journey has been so far and I believe there will be so much more to it in the time that is yet to come! But I can't be ending without expressing gratitude to the ones whose guidance shaped me. Thank you Hari for being my pillar, for always pushing me beyond my limits, Sudhanshu for mentoring me, Akshay for the support and guidance without whom this wouldn't have been possible. I also have tremendous gratitude for everyone with whom I got the chance to work. It's so important to be surrounded by people who believe in you and keep inspiring you to be better.