Copying addresses into a map app and subtracting travel time from every meeting is a nightly ritual for anyone who travels for work. BookingButler derives the origin from the calendar and works backwards from arrival. Here is what got automated and what stayed manual.
[Read More]
A Travel Calendar in Go, Gorilla Mux, and React: How BookingButler Is Built
How BookingButler turns Google Calendar events into departure times: a Go + Gorilla Mux API that exchanges the auth code, resolves stations with Google Maps, and fetches routes from NAVITIME. The design, the code, and the gaps left in it.
[Read More]
Reversing the Order of House Hunting: Designing a Gym-First Search
House hunting starts with the office; the gym comes after the move. Muscle Real Estate flips that order into four stages: facilities, commute area, gym, property. The design, its trade-offs, and what is still mock.
[Read More]
Choosing a Home From the Gym Outward: A Go (Gin) + React API for Commute-Aware Search
Muscle Real Estate reverses the usual house hunt: pick a gym first, filter by commute area, then look at nearby properties. The layering in Go and Gin, the PostGIS complex search, and the commute API that is still mock.
[Read More]
No One to Critique Your Drawing, and No Wish to Upload It
Drawing alone means no reviewer nearby, and uploading practice sketches to a cloud service feels wrong. How Dessan-sensei removed both walls with a local vision model on the LAN, using text-only history as context and level-aware prompting.
[Read More]
A Drawing Critique App in Go, SQLite (WAL), React, and an Ollama VLM
Dessan-sensei scores a drawing photo on six axes out of ten using a local vision model. A tour of the four layers — Go, SQLite in WAL mode, React, and Ollama — through the prompt builder, the JSON parser, and the transactional save.
[Read More]
Preventing Missed Sequels by Design: Stop Relying on Remembering at the Bookstore
Missing the next volume is not a memory problem, it is a problem of where the state lives. How tsuzukan records owned volumes by ISBN and reports what the series is missing, including the cases a machine cannot decide.
[Read More]
How tsuzukan Tracks Manga Sequels: Go, React 19, and Three Bibliographic APIs
A tour of tsuzukan’s internals: a Go 1.26 + Gin API, a React 19 frontend, PostgreSQL, Firebase Auth, and three bibliographic sources with very different personalities — openBD, NDL Search, and Rakuten Books — folded behind one interface.
[Read More]