My name is Aravind Govindhasamy.
I am a software developer, an introvert, someone who enjoys solving difficult technical problems, and a person preparing to begin a new chapter through research.
But this journey did not begin with a perfect academic record, a clear career plan, or a straight path.
It began with confusion, setbacks, curiosity, and the decision to continue even when things did not go as expected.
An Engineering Dropout Who Did Not Stop Learning
Before computer science became my main direction, I started with B.E. Electronics and Communication Engineering.
At that time, I did not complete the course. Becoming an engineering dropout was not something I was proud to speak about for a long time. It felt like I had fallen behind while others were moving forward with a clear degree, job, and future plan.
But looking back, that phase did not end my journey.
It forced me to rethink what I actually wanted to learn and build.
Instead of letting that setback define me, I moved toward Computer Science. I continued my education, completed my undergraduate studies in Computer Science, and later completed my MCA. More importantly, I did not stop learning outside the classroom.
That became one of the biggest lessons in my life:
A setback can change your path, but it does not have to decide your destination.
College Days: More Than Just Marks
My college life was not only about attending classes or passing exams.
During my undergraduate years, I served as a student representative. It gave me exposure to responsibility, communication, coordination, and handling people with different opinions. It may sound like a small role, but it taught me that leadership is not always about being the loudest person in the room.
Sometimes leadership means listening, taking responsibility, solving small problems before they become bigger ones, and being available when people need help.
I was never the kind of person who wanted to be at the centre of every group.
I was usually quieter, more observant, and more comfortable working independently. Some people may call that being a "lone wolf." For me, it simply means I learned how to depend on my own discipline, curiosity, and consistency.
At the same time, college helped me understand that independent work and teamwork are both important. You may build skills alone, but real progress often comes when you learn to communicate your ideas and work with others.
From Curiosity to Software Development
Technology slowly became the place where I felt most comfortable.
I liked the feeling of taking an idea, breaking it into smaller problems, writing code, testing it, fixing failures, and finally seeing something work. Whether it was a web application, backend API, database workflow, IoT device integration, RFID system, or automation tool, I enjoyed the process of turning a problem into a working solution.
Over time, I started building across different areas:
- Full-stack web applications
- Backend APIs and database systems
- IoT dashboards and MQTT integrations
- RFID-based workflows
- ERPNext and enterprise software customisation
- Cloud deployments and self-hosted systems
- Automation and AI-assisted developer tools
I do not see myself as only a frontend developer, backend developer, or IoT developer.
I enjoy working at the point where these systems connect.
A device sends data. An API processes it. A database stores it. A dashboard makes it understandable. An ERP workflow turns it into a business action. That complete chain is what interests me.
Learning Outside the Syllabus
One thing I learned early is that formal education alone is not enough in technology.
The industry changes fast. Frameworks change. Tools change. Problems change.
So a large part of my learning came from building projects, reading documentation, debugging errors, testing hardware, deploying servers, contributing ideas, and repeatedly trying things that did not work the first time.
I have spent time learning from failures:
- APIs that did not behave as expected
- Deployments that broke after configuration changes
- Device connections that worked sometimes and failed at other times
- Databases that needed better structure
- Projects that looked simple but became complex in real usage
- Ideas that needed to be dropped, redesigned, or rebuilt
Every one of these experiences made me more practical.
I do not believe in pretending that every project is successful from day one. The real learning usually happens when something fails and you are forced to understand why.
Why I Am Thinking About a PhD
After working on real software and IoT systems, I started feeling that I wanted to go deeper.
I do not want to pursue a PhD only to add a title before my name.
I want to understand problems properly, study existing work, identify genuine gaps, build practical solutions, validate them, and contribute something useful beyond a single implementation.
My interests are centred around applied technology:
- RFID and inventory systems
- IoT and connected devices
- Open-source ERP platforms
- Automation and intelligent workflows
- AI-assisted systems
- Digital transformation for small and medium businesses
My background has taught me that a good technical idea is not enough. It must also be affordable, reliable, usable, maintainable, and suitable for real people and organisations.
That is the kind of research I want to pursue.
I Am Still Becoming
I am not writing this as someone who has figured everything out.
I am still learning. I am still improving my skills. I am still working on my career, my projects, and my future plans. There are moments of uncertainty, self-doubt, and pressure - as there are for most people trying to build something meaningful.
But I have learned not to treat uncertainty as a reason to stop.
From being an engineering dropout to finding my place in computer science, from being a quiet student representative to building real software systems, from learning alone to preparing for a research journey - every stage has shaped me.
This blog is not about proving that I am perfect.
It is about documenting that I kept moving.
And before the PhD journey officially begins, I wanted to share the person behind the projects, code, and technical titles.
This is my beginning.