claw crane
An older electronics project that still shows how I like to build, debug, and understand systems.
electronicsarduinohardwaredebugging
open project.txt
this is a portfolio, but not the kind that only shows finished screenshots. i use it to keep the useful parts of the work: web work, software builds, hardware projects, self-hosting notes, and a few system-level ideas that keep coming back.
a few things worth pinning for now.
An older electronics project that still shows how I like to build, debug, and understand systems.
A multi-chain tracking and wallet tooling project that tries to make several ugly crypto APIs feel like one coherent product.
A home server setup that keeps expanding into a wider self-hosted system of files, proxying, domains, and small services.
newer notes, updates, and smaller entries.
product ideas, utility apps, local-first tools, and the habit of keeping them somewhere before they dissolve into chat history.
this was already a mess before and it still is one in places, but now it is at least becoming a real devblog and portfolio combo i can build and host properly.
guitar, crochet, painting, repetition, and the non-code parts that still connect back to how i build.
most progress is not a launch. it is one api fix, one schema cleanup, one query improvement, or one less confusing screen than yesterday.
raspberry pi, docker, reverse proxy, domains, files, experiments, mistakes, and the boring details that usually get erased once the stack behaves.
the polished version is usually the least useful version. the better one still remembers the wrong turns, weird logs, and restarts that made no sense.
iv, rav, sozialamt, delays, loops, waste, classification, and the sense that a lot of money and human effort disappear because systems move too slowly.
schematics, motors, wiring, troubleshooting, and getting a real machine to behave after a lot of trial and error.
older and newer project pages, kept in timeline order.
multi-chain tracking, wallet tagging, token aggregation, ugly apis, backend structure, and making messy data readable enough to use.
react native, expo, sqlite, ticket scanning, photo uploads, and a mobile app concept that already had a pretty clear event flow.
expo, react native, api calls, comments, profiles, geolocation, image uploads, and one of the stronger older mobile app builds.
react, hosting, dns, seo, proxying, and the less glamorous side of running a real website for someone else.
php, mariadb, rest api, vanilla javascript, and an early project that forced me to understand the boundary between frontend and backend properly.
react, graphql, strapi, auth, feedback workflows, and a proper school project that already had to behave like a real product.
poster, brochure, and ci/cd work from the mediamatiker apprenticeship, built in the phase where design still mattered as much as web.
what tends to show up here.
web work, backend work, scripts, testing, deployment details, ui cleanup, api pain, and the practical side of building something usable.
electronics, physical builds, sensors, motors, raspberry pi work, and anything that has to behave outside the browser.
docker, reverse proxies, domains, storage, networking mistakes, and trying to own more of the stack.
dashboards, tracking, models, messy sources, and making numbers usable instead of just available.
posts about structure, waste, institutions, incentives, and why some things stay inefficient for too long.
study notes, first passes, small experiments, and the parts worth writing down before they disappear.
smaller entries, quick updates, useful fragments, and things that are too small for a project page but still worth keeping.
bots trying their best.
where the code lives.