Planning Against the Model
The physics-shaped heater model from 106 built properly, then a planner on top of it: every schedule, random guesses, the cross-entropy method, and replanning …
The physics-shaped heater model from 106 built properly, then a planner on top of it: every schedule, random guesses, the cross-entropy method, and replanning …
The EU AI Act in three questions (who you are, what the system does, and when), with the provider and deployer definitions annotated clause by clause, set …
The fourth client on the hot path. Rust has no HTTP in its standard library, so this one pays for ureq and serde_json on the leaderboard. It takes the lead on …
The C# client on the hot path was written the way the templates say and sat at 7.1 ms against Go's 4.4. This one throws out HttpClient, JsonNode and Console, …
The Triana street-sign tile, built by rule. Azulejos de letras is a serif typeface made of strokes rather than a font, painted across a grid of glazed tiles …
Go 1.23 iterators and the slices and maps packages, set against LINQ. What you can write now, what still needs a loop, and what Go 1.27 generic methods change.
Two English floors six hundred years apart, made the same way. Rosa y Granada is Catherine of Aragon's rose and pomegranate as a medieval inlaid tile, white …
I gave Claude the heater room from the last two posts and expected a plausible story. It fitted the physics and beat my world model, until the world model …
Two pieces about light on a material. Rejería is a wrought-iron grille on whitewash where the whole grille is cast as a shadow by a sun you can move and a …
From today, Fridays on this blog are for AI law: one article of the EU AI Act or the UK's rules each week, verbatim, with every clause annotated for the …
Every repeating pattern in the plane has one of seventeen symmetries, so every wallpaper does too. Papel Pintado draws one sprig by rule and makes the symmetry …
The third client on the hot path: HttpClient, System.Text.Json nodes and a StreamReader loop, published with Native AOT on .NET 10. The binary is smaller than …
Cross-posting to dev.to, generated share images, structured data, newsletter drafts and future-dated publishing on a Hugo site, with the gotchas that each one …
Sebka is the brick lattice of the Giralda with nothing drawn in shadow: every shadow is cast from three heights of wall by a sun you can move from six in the …
The complete C# to Go series, ordered as chapters for the first time. Who it is for, where to start, and three things I would write differently now that Go is …
Giving the heater model one private field and watching it work out a door that, according to the data, is not there. Thirteen weights, gradient descent run …
The second client on the hot path: net/http, encoding/json and a bufio scanner for Server-Sent Events, in a static binary from a scratch image. What the …
Trencadís takes the painted tiles of Azulejería, smashes them with a Voronoi crack and lays the shards back on an undulating bench in lime. The cutter that made …
Publication share, top-cited papers, talent flows, private investment and the open-weight lag, as six charts with the data downloadable. The argument from …
Knotwork is a page of Insular interlace grown on a grid: one parity rule for over and under, breaks that turn a plait into a knot, pointed corners, a …
The 2024 partial JSON parser for streaming LLM output is now a package called fenced-json, with a proper API, tests, and a playground. What changed in the …
Leonor is a hall of shields painted from sentences. A blazon grammar reads thirteenth-century English, the shields are enamel and gilt on oak, and the lions are …
Two more walls for the art pages, neither of them painted. Alicatado puts Çini's star geometry through a cutter so every region becomes a piece of glazed tile …
The fastest way from your code to Claude is one POST and one stream, and this is it in bash and curl, no jq. It launches a series: one language a week, one file …
How the Azulejería and Jerez art pages grow a tile wall from a seed: one diagonal-symmetric square, a brush that drifts, four ways to repeat, and the engine …
A Filament scene on mobile was paying for a directional light and a shadow map every frame, and not a single pixel showed it. How an all-emissive material …
Replacing a hand-written world model with one fitted from logged telemetry. Four weights, gradient descent in TypeScript, and a prediction for a room the model …
The world model equation explained in code. Conditional probability, latent variables and subscripts, shown to be the same thing as a SQL WHERE clause.
What a world model is, built in forty lines of TypeScript with no equations. State in, action in, predicted next state out, using a room and a heater.
Interleaved telemetry and commands from IoT and energy devices are already world model training data. What world models are and why sensor data matters.
Why the UK's sovereign compute fund misreads the frontier. Research talent, not GPUs, is what separates labs that lead from labs that copy.
Anthropic disabled its newest models outside the US overnight. What that means for UK AI sovereignty, and why building our own is harder than the slogan.
Streaming LLM responses end to end: Server-Sent Events, a chunk protocol for tool calls, a React Native transport and a renderer that upgrades to rich content.
What it legally takes to fine-tune an LLM on proprietary data in the UK and EU. Copyright, text and data mining exceptions, GDPR and the AI Act in practice.
Securing the open source AI supply chain. Model weights, pickle files, PyTorch dependencies and how to verify what you deploy under European sovereignty rules.
Running LLM inference on European sovereign cloud providers instead of AWS, GCP or Azure. Who offers GPUs, what it costs and what to expect.
How to build one AI platform that satisfies both the EU AI Act and the UK's lighter regime, with the regulatory split encoded as code rather than policy docs.
Why jurisdiction, not model capability, is the real constraint on European AI. How to architect AI platforms that stay under European legal control.
Code is not more trustworthy because its author suffered writing it. On AI-assisted development, accountability and why the suffering argument fails.
Six months of production Go after twenty years of C#. An honest retrospective on what was worth it, what hurt, and what I would tell past me.
The Go features a long-time C# developer would struggle to give up. Single binaries, fast builds, implicit interfaces and the rest.
The C# features I actually miss after months of writing Go full time. LINQ, proper enums, nullable reference types and a few others.
Go on AWS Lambda cold starts in around 100ms. How that compares with .NET Lambda functions, and how to build and deploy a Go handler.
Multi-stage Dockerfiles for Go that produce images under 20MB. How static binaries and scratch base images compare with .NET container builds.
A complete GitHub Actions workflow for Go projects. Build, test, lint, cross-compile and release, compared with the .NET CI setup you already know.
Liveness and readiness probes in Go for Kubernetes. Health check endpoints that tell orchestrators something useful, compared with ASP.NET Core health checks.
Running Go services on Kubernetes. Graceful shutdown, resource limits, health checks and why Go and Kubernetes fit together so naturally.
Instrumenting a Go service with OpenTelemetry. Metrics, traces and logs wired up end to end, compared with the .NET OpenTelemetry setup.
Shrink Go binaries with ldflags and control what gets compiled with build tags. A guide for .NET developers used to self-contained deployments.
Go compiles to a single static binary with no runtime to install. Why that changes deployment for .NET developers, and how cross-compilation works.
Versioning Go modules with semantic versioning and git tags. Major version suffixes, pseudo-versions and the differences from NuGet packaging.
Configuration in Go without IOptions or IConfiguration. Environment variables, flags, file parsing and the libraries .NET developers reach for.
Go's database/sql versus Entity Framework. Writing SQL by hand, scanning rows into structs and living without change tracking or LINQ.
Debugging Go with Delve after years of Visual Studio. What works, what is missing, and how to set up breakpoints and watches in VS Code and GoLand.
Code generation with go generate in place of C# reflection and source generators. Why Go developers write code that writes code, and the tools they use.
GORM for developers who miss Entity Framework. What the most popular Go ORM offers, why the community argues about it, and the alternatives like sqlc.
Building HTTP services with Go's net/http instead of ASP.NET Core. Routing, middleware, handlers and JSON without a framework.
JSON in Go with encoding/json and struct tags, compared with System.Text.Json and Newtonsoft. Omitempty, custom marshalling and the quirks that bite.
gofmt, go vet and golangci-lint for developers used to .editorconfig debates. Why Go formatting is not up for discussion, and the linters worth enabling.
Structured logging in Go with log/slog, compared with ILogger and Serilog. Handlers, attributes, context and when to still pick zerolog or zap.
Go has benchmarking and profiling built into the toolchain. A C# developer's guide to go test -bench and pprof, compared with BenchmarkDotNet.
Mocking in Go without Moq or NSubstitute. Hand-written fakes, small interfaces, and generated mocks with mockery and gomock.
Multi-module Go repositories and go.work workspaces, for teams coming from .NET solutions with shared projects and many services.
How to organise a real Go project. Packages, internal directories, cmd layouts and why .NET's solution and namespace hierarchy does not translate.
Testing in Go with the built-in testing package instead of xUnit or NUnit. Table-driven tests, subtests, test helpers and coverage.
Go has no inheritance at all. How struct embedding replaces C# class hierarchies, and why it stops being frightening after the first week.
Go interfaces are satisfied implicitly, with no implements keyword. Why that feels like chaos to C# developers and why it turns out to be better.
Go's any type explained for C# developers. How type assertions and type switches compare to object and casting, and when reaching for any is a mistake.
Goroutines explained for C# developers who think in async/await and Task. No coloured functions, no thread affinity, and a different mental model.
Go channels explained for C# developers who know BlockingCollection and message passing. Buffered, unbuffered, closing, ranging and the classic gotchas.
Go's context.Context compared with C# CancellationToken. Cancellation, deadlines and request-scoped values, and why every I/O function takes one.
Mutexes, RWMutex, WaitGroup, Once and atomic in Go's sync package, compared with lock and SemaphoreSlim in C#. When to use them instead of channels.
Go's select statement for multiplexing channels. Timeouts, non-blocking operations and cancellation, compared with Task.WhenAny in C#.
Pointers in Go for C# developers who have never needed them. Value versus pointer receivers, when to pass by pointer, and why it is less scary than it sounds.
Go slices are not arrays and not List. Length, capacity, shared backing arrays and the append gotchas that catch every C# developer.
How Go decides between stack and heap at compile time. Escape analysis explained for C# developers used to value types and the garbage collector.
Go error handling for C# developers. Why if err != nil replaces exceptions, how to wrap and inspect errors, and when the verbosity pays off.
Go's panic and recover look like exceptions but are not meant to be used like them. When they belong, and why Go developers judge you for throwing.
Go's switch statement compared with C# switch and pattern matching. No fallthrough by default, tagless switches, type switches and the surprises.
Go generics compared with C# generics. Type parameters, constraints and the deliberate limits that stop you building your usual abstractions.
Go has no enums. How iota, typed constants and stringer stand in for C# enums, and where the substitute falls short.
Go's nil compared with C# nullable reference types. Nil pointers, nil slices, nil maps, the nil interface trap and how to stay safe without the compiler's help.
Go has no properties and no public or private keywords. How capitalisation controls visibility, and how to encapsulate without getters and setters.
Go has structs, not classes. How methods, constructors and encapsulation work without inheritance, for C# developers who design class hierarchies.
Go modules and go.mod explained for .NET developers used to NuGet and csproj. No registry, no version ranges, and why it works anyway.
A C# to Go phrasebook. Familiar .NET concepts, keywords and operators mapped to their Go equivalents in one bookmarkable reference.
A .NET developer's first look at the Go toolchain. go build, go run, go test and go mod compared with the dotnet CLI and MSBuild.
A partial JSON parser in TypeScript that streams an LLM's structured output to the screen before the response is complete.
Replace the cookie-banner wall of toggles with consent negotiated in conversation. A GDPR-friendly pattern for LLM apps that users can actually understand.
Fixing a SIGABRT crash on iOS force-quit caused by Reanimated worklets outliving the app in a React Native and Filament project.
Building an Expo config plugin for Android Credential Manager Google Sign-In with AI assistance, for seven dollars of API credit and a day of experience.
An MCP server that lets Claude place and move geographic objects in a 3D scene, with the server doing the maths and the model doing the talking.
A Three.js viewer that renders scene data from an MCP server live in the browser, updating as Claude moves objects around through conversation.
3D models rendered on the iOS Simulator and Android but were invisible on a physical iPhone. Debugging Filament rendering in React Native on real devices.