i work across hardware and software: embedded systems, robotics, home automation and homelab infrastructure, mobile and web apps, and 3d/design. i'm self-taught, so i'm comfortable picking up an unfamiliar tool, reading the docs, and getting something working.
open to: internships, collaborations, and problems worth solving, especially where hardware and software meet.
| good at | working on |
|---|---|
| going from "i don't know this yet" to a working result quickly | syntax recall. i still look things up, and i'm building the habit of retaining it |
| iterating on something until it holds up | writing code without resources open. i can map the logic and design the system, and i'm getting better at turning that into code from a blank page |
| logic maps and systems design | staying in one language. i sometimes slip c syntax into python, so i'm learning to catch it before it breaks |
| software | hardware |
|---|---|
| web (html / css / js) | arduino, raspberry pi, iot |
| mobile apps (flutter / dart) | pcb design, circuitry, soldering |
| python automation, bash | cad / mechanical design |
| ui / ux | robotics and drones |
| video, audio, photo editing | homelab, nas, home automation |
| 3d modeling and rendering | pc building and modding |
| game modding | repair and troubleshooting |
programming & dev
hardware, homelab & electronics
creative tools
commit counts and green squares aren't a proxy for good work. when a metric becomes the target, it stops measuring anything useful (goodhart's law). judge the work, not the metadata around it.
open to internships, interesting projects, and problems worth solving