Remove rubbish

src/content/work/my-notes-android-markdown-app.md

@@ -1,27 +0,0 @@
----
-title: 'My Notes: A Markdown App for Android'
-description: A small Android note app built on Markwon. The idea wasn't new; the point was learning a platform that wasn't the web.
-date: 2026-05-02
-period: 'November 2019'
-thumbnail:
-  src: ./_assets/my-notes.png
-  alt: Screenshots of the My Notes Android app.
-links:
-  - label: Source
-    url: https://github.com/schmelczer/my-notes
-article:
-  tags: ['tools']
-  role: Android app author
-  stack: ['Android', 'Markdown', 'Markwon']
-  outcome: A working notes app and my first time outside the web stack
-  audience: technical
-project:
-  title: My Notes
-  description: A small Android Markdown note app. The point was a few weeks outside the web stack.
-  thumbnail:
-    alt: Screenshot of the My Notes Android markdown app.
----
-
-In November 2019 I wrote my own notes app for Android, used it daily for a while, and then watched it lose a long, fair fight with Obsidian. The losing was the useful part: I learned what I actually wanted from a notes app by watching mine fail to be it, one small daily annoyance at a time. Years later the same itch resurfaced as [reconcile-text](/articles/reconcile-text-3-way-merge/); by then I was editing the same notes in Vim, VS Code, and Obsidian, and nothing existed to merge three independently edited copies back into one.
-
-The app itself was modest: Markdown notes, hashtag filtering, Markwon doing the rendering. Every developer writes a notes app eventually, and the bar for shipping one isn't high. What I was really buying was a few weeks somewhere that wasn't the web: a platform with different opinions about lifecycle, storage, and what happens to your process when the user looks away. Android delivered exactly that, and I'd still recommend "build a small thing on an unfamiliar platform" as the cheapest way to find out which of your habits are skills and which are just local customs.

src/content/work/photo-colour-grader.md

@@ -1,26 +0,0 @@
----
-title: A Colour Grader Where Distance Was the Whole Idea
-description: Pick a colour, transform every nearby colour as a function of distance. A proof-of-concept grader I built to try one interaction idea.
-date: 2026-04-30
-period: 'June 2018'
-thumbnail:
-  src: ./_assets/photo-colour-grader.jpg
-  alt: Colour grading interface with tonal controls and an edited preview.
-article:
-  tags: ['graphics', 'web', 'tools']
-  role: Interface and image processing author
-  stack: ['JavaScript', 'Canvas', 'Image processing']
-  outcome: A working proof-of-concept grader and an interaction model I'd still defend
-  audience: technical
-project:
-  title: Photo Colour Grader
-  description: Pick a colour, edit every nearby colour as a function of distance. A grader built around one interaction idea.
-  thumbnail:
-    alt: Screenshot of a colour grading interface applied to a photograph.
----
-
-In June 2018 I got tired of every photo editor making me think in masks. What I wanted was to point at _this orange_ in a photo from one of my [walks](/articles/photo-site-generator/), nudge it, and have the neighbouring reds and yellows come along by however much made sense; the edit defined by distance in colour space, not by a region I'd painted on the image. No tool worked that way, so I built the proof of concept.
-
-The interface was a colour wheel. Click to drop a marker on a colour, drag to shift it, click again to add another marker with its own settings. Every transformation fell off smoothly with distance from the picked colour, so the photo never developed the hard seams that masks produce. There was no mask anywhere in the program, which was the entire experiment.
-
-I never grew it into a real tool, but the idea hasn't stopped feeling right: distance in colour space is the natural unit for the way people describe edits out loud ("warm up the skin a little, leave the sky"). If I came back to it I'd build the pipeline on WebGL rather than canvas, because the interaction only earns its keep when the preview is live on a full-resolution photo, and canvas could never quite get there.