Articles, notes, and series from the projects and experiments behind this site, ordered by publication date, newest first.
How I use F#kYeah across projects to analyze, implement, validate, and review semantic ports without a human in the execution loop.
F#AI workflowsSemantic portingAutomation
Read note →
A fun physics project in Go: turning editable roads and tyre-force limits into racing lines, ghost comparisons, and two-car experiments in overtaking and defence.
GoPhysicsSimulationVehicle dynamicsPerformance
Read note →
How canonical codecs, radix routing, structural sharing, and lazy snapshots fit together in a generic content-addressed trie.
GoGenericsMerkle treesPersistent data structuresContent addressing
Read note →
How generic methods let Mixology put typed middleware operations on the pipeline they configure.
GoGenericsMiddlewareDeveloper experience
Read note →
How Mixology replaced its embedded bstore backend with SQLite while preserving transactions, typed queries, domain ownership, filtering semantics, and application errors.
SQLitePersistenceApplication boundaries
Read article →
What I learned from building and benchmarking a compact local code index for coding agents.
LLMCode searchToolingExperiments
Read note →
A planned vertical-slice workshop that adds Procurement to Mixology, connects it reciprocally with Inventory, and finds the boundary between transactional handlers and explicit workflows.
Vertical slicesReciprocal eventsProcess managers
Read article →
How explicit replacement, review states, readiness reports, and historical snapshots let a modular application degrade honestly without erasing business context.
Domain modelingLifecycle stateCross-domain consistency
Read article →
How Mixology projects authorization and lifecycle prerequisites once, then lets GUI and TUI render native action state without sharing their views.
GoCedarAuthorizationGUITUIArchitecture
Read note →
A worked path from direct cross-domain orchestration to transactional retirement, owned reactions, and package rules that preserve both current operations and history.
Bounded contextsTransactional eventsExecutable architecture
Read article →
How Mixology gives people and programs one typed filter language, then translates its safe subset into SQLite while retaining exact application semantics.
Typed filtersExprSQLite
Read article →
How Mixology carries Cedar authorization through workspace discovery, dashboard summaries, row filtering, and action availability without turning the interface into a second policy engine.
Cedar authorizationNavigationInformation boundaries
Read article →
What Mixology shares across CLI, Bubble Tea, and Fyne, and why each surface keeps a presentation model shaped for its own runtime instead of adopting a universal view model.
Application boundaryThree surfacesPresentation architecture
Read article →
A layered testing strategy for Fyne applications, from deterministic presentation models and virtual widgets through composed lifecycles, fresh processes, race tests, and visual evidence.
Fyne desktopHeadless testingGo testing
Read article →
What Mixology's Fyne client revealed when a third, substantially different presentation runtime had to use the same application boundaries as its CLI and TUI.
Three surfacesArchitecture testingApplication boundaries
Read article →
A development journal for adding a retained-mode Fyne desktop client to Mixology while preserving bespoke surfaces, executable boundaries, and testable application behavior.
Fyne desktopThree surfacesTestable MVVM
Read article →
A step-by-step implementation of generic, rateless set reconciliation in Go, from XOR-coded cells through peeling and measured communication.
GoGenericsRIBLTDistributed SystemsAlgorithms
Read note →
How Mixology combines proven MVVM ideas with Bubble Tea's message loop to create a consistent, testable terminal application without inventing another framework.
Bubble TeaMVVM patternsTestable TUI
Read article →
A preview of eleven lessons about turning architectural intent into executable constraints, using Mixology as the worked example.
11 lessonsWritten + videoGo architecture
Read article →
An ordered path through the architecture, domain modeling, persistence, authorization, and three user interfaces of the go-modular-monolith reference application.
GoModular architectureApplication design
Open series →
A practical translation from familiar Windows concepts to Linux filesystems, permissions, shells, services, SSH, and containers.
LinuxWindowsShellSSHContainers
Read note →
How cedar-dotnet establishes correct Cedar behavior through conformance tests, then uses benchmarks to make it fast.
CedarAuthorizationGo.NET
Read note →
An executable tour from non-associative octonion multiplication to a Furey-inspired eight-state particle pattern.
F#OctonionsMathematical Physics
Read note →
Using phantom dimensions and F# operators to make invalid matrix arithmetic fail at compile time.
F#Linear AlgebraType Systems
Read note →
What F#'s algebraic types teach about modeling identifiers, validated values, closed variants, and typed workflows in Go, including where Result pipelines fit.
Algebraic typesGo domain modelingGeneric methods
Read article →
How immutable Parquet batches, snapshot metadata, DuckDB, Arrow, and Protobuf form a columnar event path from storage to results.
ParquetDuckDBArrow
Read article →
A ground-up path to ECDSA through groups, finite fields, elliptic-curve point arithmetic, and scalar multiplication.
CryptographyECDSAMathematics
Read note →