HeraHealth Postpartum Hemorrhage Tracker

I am currently working with HeraHealth, a women's health technology startup to develop an AI-powered Postpartum Hemorrhage Tracking App.

My main role on the team is to train, optimize, and implement a computer vision model capable of tracking blood loss in new mothers via pictures of their pads. However, as with many startups, I am wearing many hats.

This has given me the unique and exciting opportunity to see all sides of a application's development, including frontend and backend development, community outreach and user testing, and the legal hurdles of developing a health application.

For new mothers, the leading cause of death is postpartum hemorrhaging, which is a risk that can last up to 12 weeks after birth. With the HeraHealth app, these mothers would be able to automatically track and detect this hemorrhaging before it becomes life threatening.

Being able to use AI to tackle a dangerous problem that affects some of our most vulnerable people was a very inspiring oppurtunity for me.

Training the computer vision model was a powerful learning experience for me. I was lucky to have a team with absolute pros who were kind enough to guide me through the process, explain the logic behind the training, and point me to great resources for self study

Due to the medical nature of the project, finding data for our training was difficult. We had a single dataset that showed pads labelled with the amount of blood on them, but it could only do so much to improve model accuracy. We ended up using data augmentation methods to extend the dataset and make the model more robust with different image qualities, angles, and lighting.

Our model was tested, showed extremely high accuracy, even with image conditions it had not been previusly exposed to, and is now ready to be implemented into the application.

With the AI model done, I have shifted my attention to 3 other aspects of the project: the app, the users, and the law.

We are currently creating a React-powered app to allow for easy cross-platform publishing. While our main goal is to develop mobile applications, we are also keeping the app easily modifiable and scalable to allow for future work such as a website.

I am also spending time reaching out to mothers and healthcare professionals to interview them. Through these interviews, I can help inform design decisions, better understand my target demographic, and foster a connection with our potential userbase.

Working on an app designed for medical use has also required me and my team to be very conscientious about HIPPA compliance and general user privacy. Adhering closely to cybersecurity principles and methodologies had been a direct way of addressing these concerns. However, we have also reached out to health law experts throughout our development cycle to ensure compliance and make our application properly secure.

Our timeline is to finish the app by the end of December, then perform user testing and quality assurance in the Spring as we prepare for a full release at the summer's start.

This entire development process has been an amazing learning experience for me, and I am grateful to be able to work on such an impactful issue with such a talented team.

My experience with working on a production-level project is teaching me a web of skills that I will carry with me into my future projects

PECO: Peer Support Coach

Under the mentorship of Dr. Sang Won Bae and Dr. Rahul Islam, I helped design PECO, an AI-powered mental health support coaching system.

This coaching system helped to address the shortage of professional mental health support in the United States.

I presented this work at the Stevens Next-Gen Healthcare Innovators Symposium 2025.

PECO (AI-Powered PEer COaching System) is a novel training platform designed to strengthen the skills of peer supporters. PECO enables users to engage in simulated conversations with an AI-generated support seeker and receive live feedback from FIDO (Feedback for Improving DialOgue). FIDO provides indirect, descriptive feedback that highlights opportunities for improvement while encouraging users to revise their own responses. This reflective feedback style is intended to preserve the user's voice and foster active learning.

PECO integrates two AI models: the simulated seeker and the feedback engine, FIDO. The simulated seeker is built upon Patient-Ψ, a large language model (LLM) framework that employs Cognitive Conceptualization Profiles to generate realistic mental health patients in varied scenarios. FIDO is a custom model fine-tuned on Meta's LLaMA 4 Scout model.

Fine tuning was performed using annotated datasets from studies on mental health conversations, including labels for support strategies and seeker emotions and tendencies. FIDO provides feedback by generating a response to messages from the simulated seeker, comparing to the user's proposed message, and instructing on where improvements can be made. Additionally, PECO allows users to select specific traits in seekers they want to practice with, such as “hostile” or “verbose”.

This work was presented at the Stevens Next-Gen Healthcare Innovators Symposium 2025, a research symposium dedicated to technology-driven healthcare solutions.

I personally learned a lot from this research. It was my first experience working with AI to solve a real problem, and that was both exciting and challenging.

The biggest lesson I learned is that asking for help is the best way to learn. The biggest leaps of progress I made were always after I asked others for advice, either from my advisors or from experts I approached myself. They always had great insight and introduced me to many powerful tricks and tools that helped me on my journey.

This research also helped kickstart my fascination with AI and the public good it can bring. Applications of Artificial Intelligence in fields such as healthcare can provide massive amounts of good to society, and it has been very inspiring to work on projects that can contribute to this common good.

Barbusoft 9000

In a project for my Computer Architecture and Organization course at Stevens Institute of Technology, I was assigned with creating a custom CPU from scratch.

Using Logism Pro, I was able to make a CPU with 4 registers, an accessible RAM for data, and a display to show values.

I also created an Assembly language that could be compiled into binary code and be executed by the CPU.

It was a fun challenge creating as much functionality as possible with basic instructions. I assigned only 16 bits to each instruction, yet still had an addition, subtraction, loading, storing, displaying, and setting function for a user to implement in their programs. The CPU allowed for both the use of 2 registers or a register and a 4-bit immediate number for its instructions, and the user could even display register values or immediate numbers.

The CPU also had a RAM that was accessible by the program. Register values could be stored at specified addresses in the RAM, and data could also be retrieved from the RAM and stored in registers. The instructions for a program were stored in a separate RAM, and a program counter would automatically iterate through the stored instructions until it reach an empty instruction. At that point, the CPU would automatically stay at that empty instruction to end the program.

The user would be able to write an assembly program, then compile it using a compiler that I wrote in Python. The compiler converted a custom .barb assembly file into a hexadecimal image readable by the CPU, and the compiler allowed for comments, whitespace, and empty lines.

I also made a manual for the CPU to help others understand and write programs for it. It gets into the grittier details of how the CPU works and how one can write, compile, and run code for it. Feel free to give it a read by downloading the manual.

I was able to make the CPU, assembly language, and compiler in a day, and I am very proud of the result.

I've spent a fair bit of time just writing custom programs for the CPU and watching it do its thing. Assembly becomes a lot more fun when you're the one who designed it!

Climate Reality Gateway

I was an involved environmental activist at my high school, and so I was invited to join the Climate Reality NJ Youth Chapter.

After talking about my coding hobby, they quickly arranged for me to build a website for their chapter.

Effectively, the website was meant to be a database full of articles for teachers and students. Teachers would be given learning plans and student would be given educational reading on environmental issues. The most difficult part was this: every member had to be able to go onto the website, write an article, and post it onto the website to be accessed. I had to find a secure yet user-friendly way for my teammates to write these articles with, and this took me some time to figure out.

I eventually settled on TinyMCE, a rich text editor than can easily be implemented into a website. A teammate could go onto an article creation page, use TinyMCE to write the article (including content such as images and videos), add a title, tags, etc., then send it to the server as an html file. The server would then take this html file and store it in the porper folder (There was a folder tree of teachers and students, and each tree was separated into grade levels). Now, a user could go onto the site and search for an article using keywords and filters for user-type and grade level. The website would automatically find every relevant article and list them out for the user to enter. When clicked, the user would be brought to the corresponding article.

The website was eventually fully finished and hosted, and my team immediately began using to create and post their resources. Altough the website is no longer online, I am still proud of the contribution that I made to the Climate Reality project.

Calendar for a Friend

The first website I ever made was for a friend. He offered to pay me some cash to make him a calendar website, so I immediately got to work learning how to even make a website.

He effectively wanted to be able to add events to an online calendar (like Google Calendar), except everybody who went on the website accessed and modified the same calendar. Although the website was simple, sending user input to the server, storing it, then later retrieving it was a big challenge for me to learn. I eventually came up with a solution using Node.js involving using a manifest text file to store the events, then the server would read this text file and send the events to the user.

The user was able to add an event, specifying its name, date, time, location, and description, and this would be sent and stored in the server. The user could then view a month or a day. The month would show a list of days with events in them, and this would have a brief look at the events. The user could also look at a specific day, and here they would find more details on each event. Lastly, the user could delete any event, making the calendar fully modifiable.

It worked after 2 weeks, and I had officially finished my first coding commission!

Oregon Road 83

Oregon 83 is a project currently being developed by Professor Alex Wellerstein at Stevens Institute of Technology. The game is designed for the player to experience an alternate history America where the nuclear tensions in 1983 boiled over and the world entered a nuclear exchange.

The game combines heavy research of the time period with an homage to The Oregon Trail to make a historically accurate survival game where the player must cross the country to reach their brother's bunker in Oregon.

This project is the first large-scale video game that I have ever worked on, and it has taught me many unique lessons.

My work on the project was with the audio team. I not only contributed to the team by making music and sound effects myself, but also by helping to implement the audio in the game engine.

The game uses a custom-built Javascript engine, meaning that it was up to the audio team to organize the audio system in the code. We eventually settled on FMOD, a third party software meant to allow game developers to implement dynamic audio.

By setting up audio events and parameters to control those events, we could abstract the code behind playing the proper audio at the right time to a simple changing-of-variables for the programmers. This also allowed us to experiment with dynamic audio systems. For example, we drafted a general travel theme that would change based on which companions you had in your party.

The most important lesson that I learned from this project was the value of organization.

The audio team alone had 11 people in it, and so I thought production would be easy. However, the opposite was true.

That many people working on the same project lead to clashing ideas, redundant work, and a general lack of direction.

One of the most important contributions that I made to the project wasn't any of the music that I made or the FMOD system that I implemented, but this:

I helped to create a list of all of the music and sound effects that we absolutely needed for the project, ranging from car engine noises to the menu theme. I then made an FMOD event for each piece of audio that we needed and shared it with the team.

Now, instead of simply working on whatever they thought was worth doing, the team had a clear, managable list of individual tasks to work through.

This significantly improved the workflow of the team, as now team members were able to work on the project and feel confident that what they were doing was effective.

Although the project is still under development, I am extremely grateful to work on a video game of a larger scale. It taught me many valuable lessons about video game development that will stick with me for the rest of my career.

I learned the importance of organization, how to work within a larger team, and how to communicate with others to make sure that everyone worked towards one unified vision.

Deck Thrower

Deck Thrower was made for the first Stevens Game Development Club's Game Jam that I participated in.

I had 48 hours to build the game based on the theme they gave (Unusual Weapon).

I was able to finish the game by the deadline and got 2nd place in the entire jam!

I made all of the game's assets myself during the jam.

Some time after the jam, I decided to polish up the game into a more completed state.

I added art, sound, and music, added a main menu, and also squashed many bugs.

I'm proud of the game that it has become.

Click the image to play it in the browser. Simply use WASD to move and Left Click to shoot a card. Scroll or use numkeys to choose your card.

Fruity Catcher

Fruity Catcher was the first game that I ever fully completed.

Although it is simple, it took over a month to develop simply because I was teaching Unity to myself as I made it.

This game is a fruit catcher game, where the player must move around the ground to catch fruit falling from a tree.

However, I also added bombs and powerups to make things more exciting!

The powerups range from making the player bigger to slowing down gravity to having everything spawn in faster!

Every asset in the game, from the sprites to the music, is entirely made by me.

One of the largest challenges of the game was organization.

Even something as simple as keeping score required a lot of work to keep everything organized.

I eventually learned to use game managers to keep every aspect of the game modular and abstracted.

Rather than have my collision code also apply the powerup when the player picks up one, it simply asks the powerup manager to do so.

Rather than have my menu screen handle the transition to the main game, I simply had my menu manager do the work itself.

I eventually submitted this game to the Computer and Console Gaming Society and the Stevens Game Development Club's gaming tournament.

This event had many students on my campus come together and compete to earn in the best scores in games developed by the Stevens Game Development Club.

It was fun and very rewarding to see a whole group of people play my game and get very competitive over it!

Click the image to play it in the browser. Simply use A and D or left arrow and right arrow to move and catch the fruit!