Every time I picked up a new repo I lost two or three days just reading before I could safely change anything. So I built this. Point it at a GitHub repo, ask questions in plain English, generate docs, run a security pass. Every answer comes back with the file it pulled from, so you are not just taking its word for it.
I work a help desk, so I wrote the fifteen tickets the way they actually come in:
what the user said, not what is wrong. "It says connected but nothing loads." You
dig around with a fake Windows console (ipconfig, ping,
nslookup) and then commit to a diagnosis. It grades how you got there,
not just the answer. The DNS one catches almost everybody.
Paste in a job description, drop in your resume, see where you actually line up. I wrote the matching engine myself (TF-IDF, cosine similarity, a 190-skill taxonomy) because every other tool I tried hands you a number and expects you to believe it. Open the scoring panel and drag the weights around. Nothing gets uploaded, it all runs in the tab.
This started life as a SQL Server database I designed for a class. Tables, relationships, stored procedures, the whole thing. I liked the schema enough that I built a real front end on top of it, then swapped the data layer for IndexedDB so it runs in a browser instead of needing a server.
Class projects and small experiments. Games, algorithm practice, coursework in Java, Python and C++. None of it is polished, but it is all public if you want to see how I write when nobody is looking.
Professional
Jan 2025 — Present
Hardware, software, networking, account lockouts. Faculty, staff and students, in person and over remote sessions. I take tickets in Ivanti from the first report through to closing them out. I also image and maintain the Mac and Windows lab machines with Jamf and Azure. When something keeps coming back I write up what actually caused it, so we stop reopening the same ticket every semester.
Jan 2024 — Jan 2025
Met tight unload deadlines and trained new hires on the process.
Oct 2020 — Apr 2023
Processed 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 got curious about why, and I never really stopped.
These days I work the help desk at Central Connecticut State University. Hardware, networking, account lockouts, and every so often something nobody can reproduce. I take tickets from the first report all the way through to closing them out, and I keep the Mac and Windows lab machines imaged and up to date. Honestly it has taught me more about debugging than any class did, mostly because you cannot skip the boring part when somebody is standing in front of you waiting.
On paper: BS in Computer Science from Southern New Hampshire University, and I am about a semester out from finishing my MS there, focused on software engineering. Before all that I picked up a networking certificate at Tunxis. I have kept a 3.8 through both degrees while working, which I am reasonably proud of.
Code-wise I am most at home in Python and TypeScript. I am comfortable most of the way across a stack, from designing a schema and writing the stored procedures at one end to putting a React front end on it at the other. FastAPI, Next.js, PostgreSQL, Redis, Celery and Docker are all things I have shipped with rather than just read about.
The part I actually care about does not demo well: code someone else can read, tests that catch real problems, and leaving a project where I am not the only person who can touch it. Every project on this page started as something that annoyed me until I built the fix.
