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 more than that it is a place to keep the work in motion. not just the polished outcome, but the parts that usually disappear on the way there: the experiments that turned into something real, the systems that keep pulling my attention back, the technical notes that save future time, and the unfinished threads that still feel worth following.
a few things worth pinning for now.
An older electronics project that still shows how I like to build, debug, and understand systems.
A private internal dashboard that pulled wallets, exchanges, card spending, and exits into one place while crypto still mattered a lot more in my day-to-day life.
A home server setup that keeps expanding into a wider self-hosted system of files, proxying, domains, and small services.
non-featured posts updated in the last 30 days.
a longer argument about swiss support systems, delayed stabilization, cost shifting, and why survival should not depend on being classified by the right institution first.
ai removes setup, syntax, terminal work, docs, and friction. i love that. but some of that friction used to be where technical depth came from.
iv, rav, social assistance, delays, loops, health, integration, pensions, and the idea that survival should not depend on being sorted into the right institution first.
non-featured posts older than 30 days.
react, graphql, strapi, auth, feedback workflows, and a proper school project that already had to behave like a real product.
expo, react native, api calls, comments, profiles, geolocation, image uploads, and one of the stronger older mobile app builds.
react native, expo, sqlite, ticket scanning, photo uploads, and a mobile app concept that already had a pretty clear event flow.
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.
poster, brochure, and ci/cd work from the mediamatiker apprenticeship, built in the phase where design still mattered as much as web.
the main buckets.
apps, backend work, scripts, and practical build problems.
electronics, physical builds, and things that have to work outside the browser.
docker, domains, reverse proxies, and owning more of the stack.
dashboards, tracking, and making messy sources usable.
notes about structure, friction, and recurring patterns.
where the code lives.