Lab notes
Blog
This blog is the older name for what is now the lab notes section. The index below points to the current notes so older links continue to find their way to live content.
What this index is
This is the historical blog path. The writing that used to live here is now under /lab-notes/, where it sits next to the demos, docs, and papers it relates to. The lab notes are short technical write-ups rather than diary entries. Older links to /blog/ continue to land here, and from here you can go straight to a current note.
The five notes below are the working set.
Current lab notes
- Ubigraph server and graph streaming - how the viewer accepts changes one at a time and why that matters for animation.
- XML-RPC graph control - the small set of calls a client actually needs and how to translate older examples to current Python.
- Graph visualisation alternatives - what to reach for when the original viewer is not available and you want to keep working.
- Random graph layout notes - layout behaviours that random graphs surface and how to read them.
- C++ template papers and graph tools - where the older papers in the references shelf connect to graph tooling work.
How the lab notes are written
A few principles, kept short.
- A lab note answers one question. If a draft drifts onto a second question, it is split.
- A lab note is dated when there is a reason to date it. Most of the material is timeless and is left undated to make that clear.
- A lab note links to the demo, doc page, or paper it relates to. The point is to keep the network of pages legible rather than to write essays in isolation.
- A lab note does not pretend to be neutral on questions where there is a sensible answer. It says what works.
If you are reading the lab notes for the first time and want a place to start, the XML-RPC graph control note is the most practical and the one that ties most of the other notes together.
What this section is not
It is not a news feed. It is not a roundup of unrelated programming topics. It does not cover trending tools, language drama, or industry commentary. The writing stays on graph visualisation, the original viewer, and the surrounding ideas.
Where to go from here
If you came in from an old link to /blog/, nothing has been moved away. The same writing is here, under a name that fits it better.