Two Linux desktop apps that take a video from "it's on my phone" to "it's in the recording". Built because the individual pieces all exist and none of them fit together. All I have to do is choose what clips I want moved, put them in order of when and how I want to talk about them, and begin presenting in OBS to be later trimmed down and edited in Kdenlive (I use EndeavorOS) iPhone Import browses the camera roll over USB and copies what I select into a project folder. That sounds trivial and isn't: on this machine ifuse silently returns corrupt data for large files. The same 183 MB clip read three times gave three different checksums, at identical file size, with damage starting on a 64 KiB boundary and no USB error logged anywhere. Roughly a third of 4 MB chunks come back wrong on any given read — which is where a long-standing "some of my imports are broken" problem turned out to come from. The fix is a verified copy: read each chunk, drop it from the page cache, read it again, and only accept it when two reads agree. Corruption is random per read, so agreement is strong evidence of correctness — and copies built this way are reproducible where plain copies never are. Every file is then decoded end to end before it counts as imported, and anything that fails is deleted and reported rather than left on disk looking fine. Video Deck Studio is the other half. Order the clips by dragging; mark in and out points that apply instantly, because they're stored as marks rather than re-encoded, so trimming ruthlessly costs nothing; hide what you've skipped; and present the result into OBS. Its most useful feature is pairs: two clips joined into one item, composited into a single frame — a screen recording of a demo beside the phone video of the same thing. Pairs open a two-track timeline where you drag one clip against the other to line them up and drag either end of either clip to trim it. Both sides are scaled to fit their half of a 1920×1080 frame and padded, so neither can ever crop the other, and the layout picks itself: two portrait clips sit side by side, two landscape ones stack. The preview is a real render. The obvious approach — one live filter graph in the player — was built first and then measured against an actual render, and the two disagreed: mpv drives its filter graph from its own playback position, so trims there don't mean what they mean to ffmpeg. Trims would have previewed as one thing and exported as another. Instead the editor renders a small 360p window around the playhead through the identical code path as the final export, and the two were then verified frame by frame. Presenting plays a full-resolution render, never the proxy. Working with Wayland rather than against it. Window embedding doesn't exist, and OBS binds its capture to a specific window — so the player is one long-lived window that OBS is pointed at once, and everything else is driven over its JSON IPC socket. Built with Python and PyQt6, driving mpv and ffmpeg, on top of libimobiledevice for the phone. ~(Written to make my own videos; still growing as I hit new limitations.)
A dead centrifuge, fully dissasembled on a folding table and assessed for issues. After a few youtube videos, multimeter testing, capacitor replacements, soldering, and some blind luck, it's back to life! This great video was a lot of help: https://youtu.be/f-lBA9Kq3T4?si=uDx0hGnT-V_UUTgt ~(Thumbnail illustration by DataBase Center for Life Science (DBCLS) — CC BY 4.0, creativecommons.org/licenses/by/4.0)
A local-first desktop app for reading into gene therapy and drug development, with an on-device AI assistant. Built for a reader who is technically strong but newer to biology — me.
The problem it solves. Reading unfamiliar literature is a vocabulary problem before it is a comprehension problem. You hit a term, you leave the paper to look it up, you lose the thread, and twenty minutes later you are six tabs deep in something unrelated. Lit Explorer keeps everything in one window so the paper never leaves the screen.
What's in it
- New Releases — a live feed from bioRxiv, medRxiv and Europe PMC filtered to my topics, so there's always something current to read.
- Explore — filter a hand-curated corpus of 39 resources by tier and tag, or search all of Europe PMC live.
- Reader — open-access full text where it exists, metadata where it doesn't, plus imported PDFs. Highlight any term and press Ctrl+L to have it explained, or Ctrl+H for its history — how the concept developed, not just what it means. Answers are grounded in the article you're actually reading.
- Library — foldered bookmarks, a persistent glossary built from every term you've looked up (exportable as Markdown), and recently-read tracking.
- Curriculum — an interactive gene-therapy roadmap whose milestones link straight into the corpus, so "learn this field" becomes an ordered path rather than a pile of papers.
- Related work — references, citing articles and similar papers in the reader's side panel.
- Semantic recommendations — local embeddings rank the corpus against what I've bookmarked and looked up, falling back to tag-matching when offline.
- System-wide lookup — highlight text anywhere on the desktop and a global hotkey sends it to the app.
Focus Reader, the part I'm most pleased with, is a different way of reading entirely. The paper is shown one word at a time in a fixed position so your eyes never move — RSVP — narrated by a local voice, with the word display driven by the audio's own per-word timings, so the flashing word is the word being spoken. The figure panel swaps to whichever figure or table the current sentence just mentioned. A rolling few seconds of microphone is always being transcribed, so you can say "stop", "faster", "go back", "next figure" without touching anything; say the activation phrase and you can ask a question out loud, get an answer grounded in the sentence you were on, read aloud, and then reading resumes where it left off.
Everything runs on the machine. Ollama serves the chat model and the embedding model; piper and faster-whisper handle speech on the CPU. No API keys, no accounts, and nothing about what I read leaves the laptop — which matters more than it sounds when the reading list itself is the sensitive part.
Built with Electron and React on electron-vite, with a main process split into modules for the model client, the live sources, PDF handling, recommendations, the voice pipeline and a plain JSON store — no database, because the data is small and a file I can read is worth more than a schema.
- demo video coming soon
The Ask page on this site, answered by a small language model running on my own desktop at home. No cloud inference, no API key, no data centre.
The plumbing is the hard part, not the model. My desktop sits behind NAT with nothing open to the internet, and I wasn't willing to forward a port to run a toy. So the connection only ever runs outward: the Vercel route pushes a job onto an Upstash Redis queue, the desktop long-polls that queue over HTTPS, runs the question against a local Ollama model, and writes the answer back under the job's id. Nothing ever reaches in. The desktop also publishes a heartbeat with a short TTL — if it goes stale the site knows the node is down and says so, in plain language, with links, instead of hanging.
Making a public-facing model behave is most of the remaining work, and it's layered rather than clever:
- A regex pre-filter refuses instruction-extraction and override attempts before the model is ever called, so the cheapest attacks cost nothing to defend.
- A hardened system prompt answers about me only from a single grounding document, in third person, and is told to treat missing sections as "I don't know" rather than fill them in.
- Deterministic rails catch two specific failure modes a prompt alone won't reliably prevent: impersonating me, and making commitments on my behalf — replying to an offer, agreeing to a date, accepting anything. Those are intercepted rather than negotiated with.
- Everything fails closed. A model error, a relay error, a malformed job — all of them produce no answer, which surfaces as the honest offline message. A wrong answer about a real person is worse than no answer.
Speed, without pretending. A 3B model on four CPU cores takes 10–20 seconds a question, and no amount of tuning changes that. What does change it is not running the model at all: the box is idle almost all the time, so an idle worker precomputes answers to likely questions, generates several candidates, and scores them against a formal-register rubric — contractions, filler, fourth-wall leaks, sentence count — keeping only the best. Cache matching is normalised-exact on purpose. No embeddings, no fuzzy similarity: a near-miss would serve a confidently incorrect answer about a real person, which is far worse than being slow. The cache is keyed by a fingerprint of the system prompt plus the grounding doc, so editing either retires every stale entry automatically.
What the visitor sees. The /ask page shows which model is loaded, the machine it's running on, your position in the queue, and whether the desktop is even awake. There's a passphrase fast-lane that jumps the queue for people I've given it to. It's deliberately un-magical: the point is that a small model on a normal computer in a house can do this, and you can watch it happen.
Built with Next.js API routes and Upstash Redis on the site side; a single-file Python poller, Ollama and systemd on the desktop side.
It must be noted with such a machine running it hard indefinetly is a lot, so it often shuts down and auto-reboot systems fail. I'm working to improve this, which may include switching from linux mint, which I am now comfortable enough to do, to something with even less overhead. A headless distro may be in order for such a project.
An old Sony CRT television, a Raspberry Pi, and a phone-friendly web remote is all thats needed to steam anything you want to a classic (heavy) piece of machinery. The hardware. The Pi outputs HDMI, which an active converter turns into composite video, feeding into the CRT's RCA inputs. Getting there meant opening the set up, splicing some cables, and soldering... then resoldering connections between all 3 elements while maintaining accessability. The remote is a web page served off the Pi and opened on any typical device. Making it easy to control without an app, remote, or anything, which although potentially leaves some security gaps, if someone wants to change the channel that badly I'll let it slide. It shows what's playing with a scrub bar and running time, transport controls, a loop toggle, a volume slider, and a library of everything on the Pi. Paste any video URL and it plays that instead. When not in use, or when using late, theres a sleep timer that tells the pi when to stop the steam. It's the single feature a CRT in a bedroom actually needs, and it's also something most smart TVs dont make easy. All moments of stoppage, whether pausing, restarting, or sleeping saves the current status so you can kick right back off where you left it when its booted back up. Finished and in use playing wii, watching the matrix, and eventually for use in an art intallation (it was technically a commissioned project).
Simple resume refresh using LaTeX to produce a clean, modern design that highlights my skills and experience effectively. Project intended to demonstate proficiency in LaTeX document creation and design. Compiled in XeLaTeX using using AltaCV document class, Will be instated for all future applicable use-cases. Visible on my mainpage as a downloadable PDF.
A 3D-modeled (and soon hand made) cat tree designed specifically for Penny to enjoy next to my desk while I work. Features multiple levels, scratching posts, and a cozy hideaway along with a bed just above desk-level to keep her entertained and comfortable. Customer feedback: TBD ~photos and build process coming soon!
A quick Python project for blending multiple MP3 files with smooth crossfades, dynamic EQ tweaks, and audio visualization. Made to give a gift CD some personal touch. Likely to be updated soon in the future!. ~(Section update & video demo coming soon)
You're looking at this one! My personal website, designed for desktop and mobile use, built from scratch using Next.js, TypeScript, and Tailwind CSS. Deployed & hosted by Vercel with a custom domain from Squarespace. It features an auto-detecting dark mode toggle, a screen-size responsive navigation bar (that retracts) & homepage + other designs & animations, all intended to showcase my projects and skills. Feel free to explore the code on my GitHub in my first public repository! (It took some time to realize I didn't need to push every update to see how it works, and I still have to for mobile testing, so early commits are messy and abundant.) Note: my learning of textscript website development sourced a lot of early information from LLM-AIs. Many fixes & feature/content implementations were done by me, but original code and ongoing feature information is/was AI-assisted. The more I do and improve this website, the more I continue to learn to do on my own!