First Week at Texas A&M Research Lab

I have been in the university town for exactly eight days. Everything is different. The air, the food, the sheer scale of the campus, the way people greet strangers on the sidewalk. I keep catching myself staring at things that locals would consider completely ordinary.

But I am not here to write a travel blog. I am here because I got into an MS Computer Science program, and I am starting my research assistantship this week.

Arriving

The flight was brutal. Multiple layovers, sleep deprivation, and the slow realization somewhere over the Atlantic that I was genuinely doing this. Leaving behind everything familiar to study at a university I had only seen in photographs and ranking tables.

The town is not what I expected. I had imagined something like the cities I saw in American movies. Instead, it is a quiet college town where the university is the town. Everything revolves around it. The traditions here run deep. People say "Howdy" to each other with a sincerity that took me by surprise.

My apartment is a small one-bedroom about a mile from campus. I share a ride with another graduate student who arrived a few days before me and already knows which grocery store carries the right spices. Small mercies.

The Research Lab

My advisor runs a lab focused on cloud computing and distributed systems. Walking into the lab for the first time was humbling. There are whiteboards covered in diagrams I do not fully understand yet. Papers stacked on desks. Monitors showing dashboards and terminal windows. It looks exactly like what I imagined a real research lab would look like, except now I have to actually contribute to it.

The other research assistants are welcoming but clearly busy. Everyone has their own project, their own set of problems they are working through. The culture is very different from undergraduate education. Nobody is going to hold my hand. Nobody is going to assign me homework with neat deadlines. I am expected to read papers, identify problems worth solving, and make progress. The freedom is exhilarating and terrifying in equal measure.

My advisor spent about an hour with me during our first meeting. He outlined the broad research areas the lab focuses on, talked about some ongoing projects, and then said something that stuck with me: "Graduate school is not about learning answers. It is about learning to ask better questions."

I wrote that down in my notebook. I suspect I will come back to it many times over the next two years.

The Academic System

The American graduate school system works differently from what I was used to. There is a strong emphasis on independent research from the very beginning. Coursework exists, and I am taking classes this semester, but the courses are designed to support and deepen your research rather than being the main focus.

I am enrolled in three courses: Advanced Operating Systems, Distributed Computing, and a seminar on cloud architectures. The syllabi alone are intimidating. The reading lists reference papers that I have only ever seen cited in other papers. Now I have to actually read and understand them.

The class sizes are small. My Advanced Operating Systems class has about twenty students. The professor knows everyone's name. Discussions are expected, not optional. Coming from large undergraduate lecture halls where you could remain anonymous for an entire semester, this level of engagement is an adjustment.

Research Assistant Life

Being a research assistant means I get my tuition covered and a monthly stipend. This is crucial because international student tuition in the United States is not a number you want to look at on an empty stomach. The stipend is modest, but for a graduate student in a small college town, it is enough. Rent is reasonable, food is manageable if you cook, and entertainment mostly consists of working late in the lab and occasionally watching football with the other grad students.

In return, I work in the lab. My responsibilities are still being defined, but they will involve a mix of supporting ongoing research projects and eventually developing my own thesis topic. Right now, I am in the reading phase. My advisor gave me a list of about thirty papers to work through in the first few weeks. Topics range from virtual machine management to resource allocation in cloud environments to service-oriented architectures.

Thirty papers. In a few weeks. Each one dense with mathematical models, system architectures, and evaluation methodologies. I have read four so far and I am beginning to understand how much I do not know.

Culture Shock, the Quiet Kind

The culture shock is not dramatic. Nobody has been rude to me. Nobody has made me feel unwelcome. If anything, people have been overwhelmingly friendly. The culture shock is in the small things.

The grocery store is enormous. The aisles stretch on forever. There are seventeen varieties of bread. I stood in front of the bread aisle for five minutes trying to understand the difference between wheat, whole wheat, whole grain, multigrain, and something called "honey oat." Back home, bread was bread.

Driving is essential here. There is no public transportation to speak of. I do not have a car yet, so I walk or catch rides. The distances are vast by my standards. What people here call "nearby" would be considered a separate neighborhood where I come from.

The weather is strange. January here is mild by local standards, but after arriving from a tropical climate, I find it cold. Not brutally cold like the northern states, but cold enough that I had to buy a proper jacket for the first time in my life.

What I Am Feeling

Honest answer: overwhelmed, excited, and determined, roughly in that order.

Overwhelmed because the gap between what I know and what I need to know feels enormous. Every paper I read references three more papers I should have already read. Every conversation in the lab involves concepts I am still wrapping my head around.

Excited because this is exactly what I wanted. A real research environment. Access to cutting-edge work. The opportunity to learn from people who are pushing the boundaries of what distributed systems can do. I wanted to be challenged, and I am getting that in abundance.

Determined because I worked incredibly hard to get here. The GRE preparation, the application process, the visa interviews, the financial planning. All of that effort was in service of this moment. I am not going to waste it.

Looking Ahead

My immediate goals are straightforward. Finish the reading list. Get comfortable with the lab's existing codebases and tooling. Start identifying potential research directions. Survive my first round of coursework assignments.

Longer term, I want to find a research problem that sits at the intersection of cloud computing and something practically useful. I am drawn to problems that have both theoretical depth and real-world applicability. I do not want to write papers that only other researchers read. I want to work on things that eventually matter to practitioners building real systems.

That might be naive. My advisor would probably say I need to worry about understanding the existing literature before I start thinking about impact. He would be right. But the ambition is there, and I think that matters.

More updates to come as I settle in and start making sense of this new world.