The Candid Startup

Summer time, and the living is easy.

My frozen shoulder problem means I haven’t had a chance to keep dependencies up to date on my InfiniSheet project.

My last post was on May 11th, two months ago.

I’m putting my TypeScript Structured Concurrency sketch into practice on my InfiniSheet project.

Over time I’ve come to realize that there’s more to error-handling in concurrent programs than rejected promises or async Results.

The typical playbook for a supply chain attack is to use some form of social engineering to compromise a maintainer’s account, then use that account to directly publish compromised packages to npm.

After some refactoring to decouple event log and snapshot loading, followed by many other distractions, I’m finally ready to implement multi-tile snapshots.

Recently, I’ve been seeing a glut of dependabot security alerts for my Infinisheet project.

Two months ago our prototype Heat Geek NanoStore was rebuilt.

I’m a strong believer in unit tests.

Asynchronous code is great.

Last time, we got a load-on-demand chunked snapshot format working.

We’re ready to start making our event sourced spreadsheet scalable.

The news is full of npm supply chain attacks.

Six months ago I was spending all my time on Infinisheet, my event sourced spreadsheet project.

Last time, I left you with a cliffhanger.

It’s been more than two months since my post about our prototype Heat Geek NanoStore.

I’m putting my money where my mouth is.

It’s been a while since I investigated Home Assistant’s concurrency model.

Lambda functions work best for short lived, compute intensive tasks.

Once again, I spent the week after re:Invent gorging on YouTube videos at 1.5x speed.

We’ve had our Kia e-Niro EV for five years now.

We had a cold snap here in the UK.

We recently had a Vaillant heat pump and Heat Geek NanoStore installed.

A few weeks ago I described our heat pump installation, which included a mystery hot water system.

I touched on Open Energy Monitoring briefly when talking about my heat pump install and Home Assistant integration.

Now that we have a heat pump up and running, the obvious next job is to get it hooked up to Home Assistant.

Like many houses in the UK, we rely on a gas combi boiler for heating and hot water.

I like to think of myself as a computer scientist.

The Hypervolt EV charger integration is an important dependency for the automations and dashboards that I’m running on Home Assistant.

Last time, we touched briefly on how to extract electricity meter readings from the Home Assistant Octopus Energy integration.

I now have useful data being collected and displayed on the Home Assistant built-in energy dashboard.

I’m finding the Home Assistant Energy Dashboard to be pretty but not very useful.

Last time, I took you through setting up a Home Assistant Green, installing HACS, adding custom integrations and then creating an automation to disable discharge of my home battery while my EV is charging.

I was about to get started turning my stub react-spreadsheet package into a real one, when I noticed a new Vitest related warning from VS Code.

This is a blog, not a set of living documents.

Home Assistant has been on my radar for a while.

The framework for our event sourced spreadsheet is in place.

We don’t yet handle the case where a snapshot completes when a client is already up and running.

It’s finally time to create snapshots as my event sourced spreadsheet’s event log grows.

I have all the bits of infrastructure needed to start saving snapshots of my event sourced spreadsheet.

Now that I have interfaces and reference implementations for a Blob Store and Workers, we can try to wire them up to our tracer bullet prototype.

I’m building an event sourced spreadsheet on a foundation of an event log, a blob store and background workers.

We left our scalable cloud spreadsheet project in a good place.

I’m a strong believer in unit tests.

I recently made my spreadsheet data interface more explicitly asynchronous.

Last time, I naively updated my spreadsheet frontend component to use an asynchronous update API.

Last week’s tracer bullet development showed that I needed to make my SpreadsheetData interface more explicitly asynchronous.

I’ve been working on my scalable spreadsheet project from opposite ends.

I’ve created an event log interface and reference implementation.