Start with the real problem
I define who the page is for, what they need to do, and what would make the experience confusing.
About
I care about whether a digital product actually works.
Good presentation matters, but reliable behavior matters more. I pay attention to broken flows, unclear requirements, inconsistent content, and the details that make a product difficult to trust.
I am currently studying Computer Information Systems while building independent web products and working on multimodal AI evaluation and timestamped video-captioning contracts.
I started building my own sites to turn ideas into usable products. That work expanded into responsive interfaces, content systems, discovery tools, product prototypes, deployment, and repeated QA passes.
My long-term direction is technical: front-end development, software quality, and digital product work where I can build, investigate, test, and improve systems over time.
How I work
I build in small, testable steps.
Build the useful version
I use AI and other tools to move faster, but I decide the structure, content, behavior, and priorities.
Review what actually happens
I test mobile layouts, links, forms, empty states, and edge cases, then revise the parts that do not hold up.
Background
How I got here.
Independent web and product work
Right now I design, build, test, deploy, and revise projects like LobbyPick, EarnVerity, KpopPick, and my Roblox game concepts.
Timestamped video captioning
I review 5–10 minute clips and edit separate caption tracks for visual events, nonverbal audio, speech transcription, and speech characteristics. The work requires precise timing and close consistency across every track.
AI evaluation contracts
Across projects through Handshake, Mercer, and Outlier, I have reviewed text, image, audio, video, and simulated workflow output against detailed quality standards.
Computer Information Systems
I am completing my Computer Information Systems degree at Community College of Philadelphia, where I have worked through systems analysis, databases, programming foundations, and business technology.
Working rules
I test behavior, not just appearance.
I check whether links, forms, layouts, states, and user paths work under realistic conditions.
I document problems clearly.
I describe what happened, how to reproduce it, what was expected, and how I verified the fix.
I do not invent evidence.
I do not use fake metrics, customers, testimonials, traffic, or expertise. I show work I have actually completed.