started off as a react.js page with email.js integration, but then i realized i wasn’t important enough for that to have any real effect.
found out about Hugo, a Golang-based static site generator. i’m typing this out on it, hence the “meta”-aspect. definitely feels a lot smoother for something like a portfolio page, without all of the extra overhead (apart from installing themes…)
our (collegiate) magnum opus. designed this with three friends as a part of our senior design project, but it turned into something much bigger.
when i moved into my apartment, i was lucky enough to have core furniture already installed by the guy who lived here before me (i just paid him for it). but when i wanted to buy something new, like a lamp or a new couch for the living room, etc., i faced an issue which is pretty common among home decorators:
a fastapi-powered backend that automates the entire cold-emailing process for job applications. it handles scraping job info to generating and sending emails. i connected it to a google sheets app script and it runs locally with an ngrok tunnel to interact with from the browser for the apps script.
you start by pasting a linkedin job link into the sheet and the system kicks off a playwright script that scrapes the company name, job title, and job description. after this a separate playwright worker searches bing for recruiter or hiring manager profiles at the company (e.g. “recruiters at {company_name} site:linkedin.com”), finds the most relevant result, and adds that link to the sheet.
got into lifting over winter break and i always thought something like this existed but didn’t see anything so i just got to building. solves the (somewhat nonexistent) problem of using too many plates to lift the same weight.
for example, if you wanted to lift 135 lbs using a 45lb barbell, would you use two 25lb plates and four 10lb plates, or would you simply use two 45lb plates (one on each end)?
when i worked with state street corporation as a part of Boston University’s cloud computing class (ENG EC 528), i built a system to automate resource deployments (orchestrating database migrations) from snowflake over the course 4 months.
this project exposed me to the inner workings of ci/cd pipelines and cloud-native deployment, in addition to how database migrations truly work.
this figure shows the overall architecture of our project, detailing the specific functions of liquibase and harness.
