Every new repo used to cost me two or three days of reading before I dared touch anything. This is my fix for that. You hand it a GitHub repo and ask questions in plain English. It'll also write docs for you and run a security pass. The bit I'm happiest with: answers come back with the file they came from, so you can go and check for yourself.
I work a help desk, so I wrote all fifteen tickets the way they really land in the
queue. You get the user's words, never the diagnosis. "It says connected but nothing
loads." Then you poke around a fake Windows console with ipconfig,
ping and nslookup until you're ready to commit. It grades
the route you took, not only where you ended up. The DNS one gets almost everybody.
Paste in a job description, drop in your resume, and see where you actually line up. I wrote the matching engine myself: TF-IDF, cosine similarity, a taxonomy of about 190 skills. Every other tool I'd tried just handed me a number and expected me to believe it, so this one lets you open the scoring panel and drag the weights around. Nothing gets uploaded either. It all happens in your tab.
This began as a SQL Server database I designed for a class. Tables, relationships, stored procedures. I liked the schema enough that I built a real front end on it, then moved the data layer over to IndexedDB so the whole thing runs in a browser with no server behind it.
Class projects and things I built to figure something out. Games, algorithm practice, coursework in Java, Python and C++. Rough around the edges, but it's all public if you want to see how I write when nobody's watching.
Professional
Jan 2025 to now
Hardware, software, networking, locked accounts. Faculty, staff and students, in person and over remote sessions. I own tickets in Ivanti from the first report right through to the close. I also image and maintain the Mac and Windows lab machines using Jamf and Azure. When the same problem keeps resurfacing I'll write up what actually caused it so we can stop reopening it every semester.
Jan 2024 to Jan 2025
Hit the unload deadlines and trained the new hires on how it's done.
Oct 2020 to Apr 2023
Sorted high volumes of mail against dispatch deadlines.
Education
Expected Sep 2026
GPA 3.83
2022
GPA 3.82
2020
I'm Darel. I got into this the way a lot of people do. Something on my computer broke, I wanted to know why, and I never really stopped. These days I work the help desk at Central Connecticut State University, which is mostly hardware, networking and locked accounts, plus the occasional thing nobody can reproduce. It's taught me more about debugging than any class has, mainly because you can't skip the boring part when somebody is standing there waiting on you. Alongside it I've got a BS in Computer Science from Southern New Hampshire University and I'm about a semester off finishing my MS there, and I've held a 3.8 through both while working.
Python and TypeScript are where I'm most at home, and I can work most of the way across a stack, from the schema and the stored procedures up to the React front end sitting on top of them. FastAPI, Next.js, Postgres, Redis, Celery and Docker are all things I've actually shipped with. What I actually care about doesn't demo well. Writing code the next person can read. Tests that catch real problems. Not being the only one who can touch a project. Every project on this page started as something that annoyed me until I built the fix.
