Turtle

added this today since you mentioned it, and I’ve been working on more of userland in the last 48h.

works well with the FSM / event driven architecture approach.

Debating whether the first public demo should be for a file system project, integrating a permission model, tree of trees, etc. This would be a comprehensive demo, but pushes the timeline out slightly.

I live in a science fiction novel.

Thinking about creating a new derivation target for .md files to automate some of my doc creation too. Enough of the other work is data, that we can specify it cleanly

@gordon.bsky.social hey, it’s been a while since we’ve chatted. what are you working on these days?

Thinking about a dumb wrapper on databases, with different search algorithms scoped to the core providers I’ll use (postgress, qdrant, neoj4, etc).

Starting to see compounding returns from my derivation pipeline, so this should be easier now.

Tomorrow I should be integrating Loro (CRDT) to allow for concurrent agents and humans while avoiding races for parallel work

So now, I should be able to ingest any design system. Then provide proper state management, accessibility, drag and drop, support for keybinding, focus states, tab order etc for free to components designed solely in Figma.

Got design system ingestion working today.

Separated functional / behavior code out, so it can be applied to any new visual component designs.

Wrote a wrapper to override react’s terrible state management with my finite state machine system, without modifying components.

Validated types for everyone, and extension of the core platform without third-party developers needing to pick up Haskell!

Thanks! Building out a system for extending the platform through client-specific additions as well, which uses the compiled library with my codegen system to pass it all through a derivation pipeline.

Congrats Ha! Do you know if it was recorded? Would love to watch if they’re planned to be released for the public.

I’ve been building infrastructure first, prototyping with live systems on top.

Design tooling so that you’re building with systems for grids, auto layout, animation curves, color. Ingests and works directly with design system code.

These lines are blurring already, but the fundamental challenge is that designers aren’t engineers, they make obvious technical mistakes.

Enabling designers think about a much larger slice of the software building process.

Infrastructure like db indexes, CRDTs, permission models, schemas, hydration, vector and graph based features.

These are all composable and produce prototypes in a day that would have previously taken months.

Back to share an update: I’m working on a narrow compiler and design tool to expand the depth of the design discipline.

This seems like something worth pitching to stripe, with their Japan offices / focus?

@djmicrobeads.bsky.social dj is back!

I’d expect nothing less, this is really great, Ha! Are you planning to write or present more about the process and work in the future?

Also nice to see your writing again, missed enjoying your working out loud after the departure from the other site.

bsky.app/profile/gord...

Indeed

This week I added emotional valence and logarithmic compression to an LLM memory system. Going for a ‘Darmok at Tenagra’ approach for the overall system. Subjective time.

Framed product development principles, organizational research, etc as the solution to horizontal problems across org systems.

Yes, covid created existential threat for a company I was working with at the time.

Previous services model meant ‘r&d’ was outsourced.

Created alignment around a
compounding consolidation model, allowing us to model second order effects across org systems for demonstrating value chain quickly.

I’ve found it significantly increase the rate at which I can identify / map / create ‘systems of systems’ work and manage abstractions, explore the translation or abstraction of domain-specific patterns.

A smarter rubber duck with pattern matching capabilities?

@michaelnielsen.bsky.social You had a question on Twitter about whether/how ai tools have improved work. Wanted to share here as I’m inclined to use this platform in a looser / scratchpad capacity

Indeed, and there’s so much strategy / framework writing available (of variable quality ofc) that the synthesis of experts is likely to generate a better approach than the majority of individuals.

Also, a moat that scales proportionally to context windows. And they’re going to keep increasing in size.

‘How can the system self-improve?’

‘How can the system improve how it self-improves?’

Will be sharing more throughout the year, both here and Twitter.