UHD Alum · UH Ph.D. · Lecturer
The application portal makes a Ph.D. look like a lottery. It isn't. Admission mostly comes down to one professor deciding they want you in their lab.
2014-2016: Houston Community College
2016-2018: UHD. Graduated Summa Cum Laude (3.77 GPA).
2018-2019: Researched smart gloves & RC drones for bridge integrity under UHD's Dr. Ting Zhang.
2019-2025: Ph.D. at UH. Completed core courses with 3.593 GPA.
Do you like working on problems that have no answer key? Not homework-hard, but genuinely unsolved. If that sounds fun rather than terrifying, a Ph.D. gives you years of time, funding, and an advisor to chase exactly those problems. If it sounds terrifying, that's useful to know too.
Jumping straight from a BS into a Ph.D. program is rough. Many students take a Master's first to bridge the gap. That's a valid path, not a detour.
Graduate courses assume you'll fill your own gaps. Nobody re-teaches the prerequisites. You catch up on your own time or fall behind.
Your first submission will probably bounce. Mine did. The next section is about why that's normal, not fatal.
Paper rejections are standard. Reviewer feedback is how the work gets better. You revise, you adapt, and you resubmit. A rejection is not a failure of your ability.
If a project stalls completely, you just shelve it. That work still goes into your thesis. No reasonable advisor will force you to stay an extra year just because of tough reviewers.
Listen to your advisor! Expand your connections at conferences. Once you publish, make a working demo (HuggingFace, Colab) to get citations!
Six years of work, in four projects:
Curve Segment Neighborhood-based Vector Field Exploration via Graph-based representations.
Physics-Constrained Vector Field Synthesis using Diffusion Models.
Human-in-the-loop LLM systems.
Flexible Cross-Platform Web Visualization (FCLWebVis).
The heavy math lives in a separate talk. Ask me about it after if you're curious.
Everything ships with AI in it now, whether you asked for it or not, and half the headlines say your job is next. Before you believe them, look at who profits from that story.
An AI company's valuation rides on what investors believe AI will do, not what it does. So the demo shows the best case, and the press release sells it as the everyday case.
"AI can do it better" reads like progress. "Our revenue is down" reads like a sell signal. Some layoffs blamed on AI are the second sentence wearing the first.
In 1999 the internet was going to replace everything. Then the bubble popped, and the internet stayed useful anyway. It changed jobs; it didn't end them. Expect the same shape here.
AI is a tool, not a boogeyman, and you can't judge whether a task is right for a tool you don't understand. If you like AI, learn how it works so you know when to trust it. If you hate it, learn how it works anyway: know your enemy. Keeping your head in the sand is the one option that gets you nothing.
When using AI as an assistant, especially for writing or research, you must remain the expert.
You can ask AI to find relevant sources for a paper, but you have to check if those sources actually exist. Hallucinations are real. Use reliable, established sources to confirm anything an AI reports before you put your name on it.
I taught three full-time courses. Concepts like ray-to-object intersection are incredibly dry on a PowerPoint slide. I wanted interactive, intuitive demos, but I didn't have the time to hand-code everything from scratch.
I used AI as an assistant to help build these web-based visualizations. It didn't get it right the first time: it almost never does. I had to iteratively refine the formulas and the output. But it turned abstract math into something students could interact with.
For COSC 2306 and 4370 I built dedicated lecture sites with live, interactive demos so abstract methods become something students can touch. Everything stays publicly accessible, anytime.
COSC 2306 · Data Programming: lectures and interactive data-structure demos.
COSC 4370 · Computer Graphics: lectures and interactive rendering demos.
I designed an assignment where students control a live 3D scene through natural language. The real lesson is prompt engineering: students rewrite the system prompt to make the LLM manipulate the world more reliably. Interact with it during the talk!
In my intro course I adopted CodeHelp, an AI assistant that scaffolds students toward their own solution rather than spitting out code. Students use it freely on exercises and practice exams; it lowers the anxiety of a first programming course without short-circuiting the learning.
Built by Somaia Alhazmi, a UH Ph.D. student researching AI in education. It's a live example of where a Ph.D. project can end up: in real classrooms.
Not long ago I was sitting where you are now. Last semester I taught three full courses at once and still built the demos you saw tonight, because I wanted my students to actually get it, not just survive the exam.
If you take one thing home: learn how AI works before you decide what it can't do, or what it will do to you. And if research pulls at you, email a professor whose work you find interesting. One email is how all of this started.