Portfolio  |  Email  |  LinkedIn

using System;
using System.Collections.Generic;

public class Vincent
{
   const string Author = "Vincent";
   const string School = "Brandeis University — Computer Science & Economics";
   const string Email  = "vincentjared18@gmail.com";

   static readonly Dictionary<string, string[]> Stacks = new()
   {
       ["Languages"]      = new[] { "C#", "Python", "Java", "JavaScript", "TypeScript", "Rust", "Swift" },
       ["Frontend"]       = new[] { "React", "Next.js", "React Native", "Flutter", "Tailwind CSS", "Three.js" },
       ["Backend"]        = new[] { ".NET", "Node.js", "Express", "NestJS", "Django", "FastAPI", "GraphQL" },
       ["Data & ML"]      = new[] { "NumPy", "Pandas", "scikit-learn", "PyTorch", "TensorFlow" },
       ["Cloud & DevOps"] = new[] { "AWS", "Azure", "Vercel", "Render", "Cloudflare" },
       ["Databases"]      = new[] { "PostgreSQL", "Firebase", "Supabase" },
   };

   public static void Main()
   {
       Console.WriteLine($"👨{Author} | {School}");
       Console.WriteLine($"Reach me at: {Email}");
       Console.WriteLine("Passionate about software engineering, machine learning, and impactful tech.");
       Console.WriteLine("Building across web, mobile, and backend — always exploring new tools.");
       Console.WriteLine("Always learning, always building.");
   }
}

A mobile-first, peer-to-peer campus marketplace where students buy and sell within their community, with real-time in-app messaging tied directly to individual listings. Full-stack solo build — from database schema to mobile UI.

Technologies Used: React Native (Expo SDK 54) · TypeScript · Node.js · Express · MongoDB (Mongoose) · Socket.IO · GridFS

Key Design Decisions:

• Real-time messaging with Socket.IO — room-based architecture (user:<email> for inboxes, conversation:<id> for live threads)
• Conversations scoped to (listingId, buyerEmail, sellerEmail) to guarantee no duplicate threads
• Media upload pipeline storing images/video in MongoDB GridFS (up to 40 MB per file) via multipart form-data
• Listing lifecycle state machine (available → pending → sold) with soft-delete and API-layer self-purchase prevention
• File-based routing with Expo Router and a centralized theming + context state architecture

A Dominion-style deck-building card game built as a 4-person team project — featuring a full game engine, a console harness, multiple AI player strategies, and a networked player server deployed to the cloud.

Technologies Used: Java · Maven · JUnit · Docker · Azure Container Apps · GitHub Actions

Key Design Decisions:

• Pluggable AI strategies behind a common Player interface (Big Money, Adaptive, and benchmark bots) for head-to-head comparison
• Card effects modeled as individual ActionCardHandler implementations (one class per card) for clean, testable game logic
• Player rating + benchmark harness runs automated match-ups to score strategy performance at scale
• NetworkPlayer lets remote agents compete against a publicly deployed player server on Azure Container Apps
• CI via GitHub Actions running the JUnit suite on every push

⭐️ From jaredvincent414