Blog

Releasing yet another Go SQL builder requires a reason. gsql aims for the unoccupied corner: type safety via generics, no code generation, and an explicit answer to Go's zero-value problem in partial updates.

How nadai runs gpdf, gsql, and renma in parallel as a side project: what to share, what to separate, and why the author hub absorbs marketing flow.

Working as a tech lead by day, shipping the Pure Go OSS libraries gpdf and gsql under MIT off-hours. Separately building a derived SaaS layer on top of gpdf (gpdf-api and friends) and, on a totally different track, a Flutter weight-training app called renma — none of those released yet. Why MIT first, what I've learned, what I'd change next.

Why I avoided CGO and wrote gpdf from scratch: the decisions behind a Pure Go, zero-dependency PDF library with native CJK font support.

Why gpdf's Go API uses closure-callback builders instead of chainable methods. The design decisions around Go's error handling, PDF tree structure, and how three different patterns split responsibility cleanly.