Every single mechanical engineer has to study a subject called mechanics. Some call it MOM, some call it SOM, some call it EM. But whatever you may call it, it's always there and it's always the same. This subject tells us how to decide whether our design will fail or not. And it is a very complex subject. And the bad news is, we only study this until we get familiar with the concept of Simulation. Once you start doing simulations, there is no going back. I had a glimpse of simulation very early in my college life, way before it would have according to my syllabus. And then I got myself involved in another project that made me understand simulation to a very great extend. This was the design and manufacturing of HAWT. Basically, we were trying to make a hybrid wind turbine that can produce electricity safely inside a crowded city. And the very first step included the Fluent based simulations. Actually, the first step was a literature review, but yeah you got the point. So, my s...
Let's go way back this time. This was 2014, I had just started my 11th class. There were new subjects, one of which was Computer Science. We had to study C++, and this was the first time I was introduced to a coding language other than HTML. You see, I was always very interested in computers. Before starting my college life, I had made an android app, a webpage, tried developing an AI and made a custom ROM for my Samsung Galaxy Y. And my interest in computers increased many times once I learned to code.
In 12th Boards, I was the highest scorer in Computer Science. I was so expert in coding that I taught all of my classmates and over ten students from my own class got 90+ in Computer Science. Maybe this was the reason everyone thought I will take Computer Science as my branch. But I didn't. There were two reasons for this: First, I didn't get a good enough rank. Second, I was interested in machines too. So, here I was in Mechanical Engineering, with a great amount of coding knowledge.
And this was also the reason that many of my college-mates assumed me to be a CSE/IT guy. The motive of me telling all this is that I never understood the importance of coding. I always knew how to code and so I never thought that coding was a necessary skill. I was wrong. When you think about Mechanical, I think the first image that comes up in your mind is a car. And even if you think more openly, there is rarely a thing that will require coding. That's exactly what I always thought. But believe me, coding is a necessity for every single human being. My whole class realized this in our second semester when we had to study MATLAB. And the sadder part was learning to code from a teacher from the Department of Mechanical Engineering is a bad idea.
So, although we all knew we had to learn how to code, none of us was able to understand anything. Even me who had experience with coding was facing difficulty with this new language. It was not until I reached my third year that I understood MATLAB, and also that I can use python as an alternative. The point of this post is to make one thing very clear: If you want to be a Mechanical Engineer or any engineer for that sake, Coding will only help you and make life easier. So learn to code, not for the sake of coding but for the sake of easing your life. I have done a number of projects and internships, and I have always found an opportunity to use my coding skills to optimize my work, which you will be able to see in my future posts.
Comments
Post a Comment