Episode-6

This week the episode was a bit short, I had a couple of questions to facilitate and they were quite interesting and deeper in their own senses. Sharing the highlights below:

Everything in which I work interests me the most, be it database study, be it PHP learning, software development of research. I am not sure which path to opt for?
The question is very confusing for college students and is quite common. When I was in college, I use to work on different things, and everything seemed to be most interesting in one way or the other. I found a common pattern in the interests, started with why? Why building software is so exciting? Why reading new concepts of academics and implementing them is interesting? All these questions landed me on a basic question, why I chose CSE or why did I opt for engineering. The answer was quite simple, solving people’s problems always used to amaze me and that’s where I thought to stick by the side of developing technical capabilities to achieve the same. It worked perfectly for me by taking a clear picture of what I actually want to do by working on several technologies and concepts, maybe that would help for you as well.

Sometimes I feel like I am the least skilled guy among the teammates I am working along with, what more can I do to become better?
I could totally resonate with the question and have a very beautiful story to share in context with the same. Back in the internship days, when I was working on the CII projects, we (I along with two other teammates) were assigned various tasks in the project. The tasks assigned to them were quite tech-heavy and the ones given to me were a bit relaxed ones. I felt demoralized a bit that am I too less skilled to be given things like that, or are the teammates that intelligent to get such heavy technical things. I knew I had less tech engagement as compared to my colleagues. Time passed, the features were built and they were appreciated for decent progress and I was given feedback to push myself more on the skill part. A day came when we had to split up into different projects and I was the one working on the first project alone. After several QA checks, a separate bug/issues list came out. The results were quite surprising. There were in total of 13 bugs reported in the features built by my teammates and none in the ones which I created. Though they were tech-heavy, I could understand the complexity and the reason for the bugs. All those issues were then assigned to me and I was able to rework those lines of code written by them and didn’t seem that heavy to me while working on them. That moment I realized that technicality is in my head and what matters the most is the ownership with which I am building my things. I was happy with my skillset of building this with full carefulness rather than making dozens of tech-heavy things. Hence I feel that skill is half of the thing in our head. Followed by sticking to the basics and adapting best practices, one can do anything.