What I've Learned

It's way easier to handle errors in Go than it is to test for them. Between wrap, unwrap, Is & As, the standard library provides a lot of great utilities to handle and recover from errors. Inducing those errors, particularly with IO or database calls is particularly challenging. That gets to the heart of building good software doesn't it? Errors are easy to find when using, but programming defensively takes skill & practice.

Yesterday

Noteleaf

  • Heiuristic article parsing enhancement

  • Implemented blob & facet handling

  • post & patch commands (foundational for push)

Skylibrary

  • A ton of plumbing and local development environment

    • Svelte + Barebones PG + Async Rust

  • Heiuristic article parsing (for wikipedia)

  • This is my first serious web application made with Rust. I'm pretty excited.

storm

  • Plumbing, but of the git porcelain variety

  • Interactive side by side diff viewer using bubbletea viewport & paginator

Today

Beacon

  • Auto-imports & debugging tools for the dependency graph.

  • Scaffolding the Zed extension, i.e. another instance in which I have to RTFM.

Skylibrary

  • Draft lexicons

  • Implement controllers for basic CRUD operations

storm

  • (Completed) a unified/top-down diff viewer.

  • I know it isn't super remarkable or interesting to make a diff tool (which this is not) but man is this nice to look at thanks to iceberg.