Problem: I was building an chat app with @qavernX and for the most part it works. All the over-engineering delights like local-sync, virtualization, actual markdown support, inline image support, etc... qave.chat Under the hood, we were using PlateUI which under it's hood uses prose-mirror. The issue with that is React will fight prose-mirror on rendering and became really hard to wire in complex logic and feel confident things are working. github.com/nytimes/react-pro… I had a few choices 1. Continue building on top of React Prosemirror and force it to work 2. Wait for NYT to release their solution and use it 3. Build my own one Me and @qavernX also recently attended a hackathon and felt the power of expressing intent and things just working when we used Effect v4 effect-atom. I then stumbled on foldkit.dev and had the idea of owning the whole flow from service/repo to the rendering engine with foldkit. Currently, building this rich text editor from scratch has been me applying Gall's principle and it's been fun! Things are working, tests are catching stuff, extending it gives me confidence. Once the rich text editor is in a good state, I'll tackle the local-sync and see if this is doable as well.

Building a Rich Text Editor from scratch! Taking inspiration from prosemirror with nodes What's nice about foldkit is state message forces correctness that I can test like below and it makes adding complexity simple.

Noticed I need to add this often. Hoping future models just do this on their own

I think everyone should try to build a rich text editor. It’s such a good project of state complexity and you can redo it afterwards and build a better version and most languages (including React) doesn’t have a nice one for all cases

React brought in `ui = fn(state)` But what if state = sum of events? foldkit.dev/core/architectur…

lol what is this british naming convention

If you’re an engineer building product. You’re in a unique spot where you can test UX intuition without being blind to the technical debt and tradeoff. Be very ambitious on building the best UX. It’s much more fun

Token output being slow has forced me to parallelise my workflow. Before I would go deep on one task, wrap it up and do the next. Now I'm checkpointing hard tasks more often for the sake of parallelisation. Definitely feeling the context switch tax, but it's an interesting skill to practice. I suspect as models get released I'll switch from one to the other. Codex Spark will switch me back to deep flows quickly, and the next frontier model will switch be back to parallelise.

With how much fun I’ve been having with rs-sdk. There should be a whole new genre of gaming called scriptable rpgs. It satisfies that grind itch without needing to sink too much time.

Limitless software Before the bottleneck was capacity. MVP was a tradeoff leaning toward it just barely works. But to make it fast you’ll need much more investment. Now you can lean MVP toward polish. Request/Response too slow? Rewrite it with a sync engine and local cache. Need to integrate with GitHub? re-write repo management as a feature. The only thing that matters now is user experience. All engineering tradeoff is speedrunnable. More importantly, it’s so much more fun.

We built a Slack alternative so you can do ChatOps with code without the need of a server or vendor bots. Here's some of the things we've learned.

Vibe coding gets a lot of hype (and hate) It brings in large amount of change quickly and that’s very easy to break. I want to talk about vibe refactoring. The speed of refactoring to what you want is so much cheaper now that vibe refactoring overtime improves code quality.

I've joined the bandwagon, this is so satisfying.

If one happens to be looking for a Discord alternative that doesn't have ID verification in place - qave.chat could be what they are looking for.

Writing software should be fun, usually when I write at work it's easily the best time where I'm deep in the problem just thinking and writing. Writing qave.chat has been like that, but instead of just writing I can leverage AI and powerful primitives like railway and cloudflare and electric and have something working so nicely. This project was born partly out of pain in using Slack but also out of the joy of writing good software. Hope you enjoy it! qave.chat/blog/hello-world

anyone needing a chat app to try in light of the discord stuff. qave.chat should help!

I used to have opencode on the left and lazygit on the right. It’s now opencode left and right and lazygit in another tab.

I was using opus 4.6 for a hard feature and it failed to do it twice. I took the PR attempts and told the 3rd try to look at that, ignore these attempts, zoom into these ones, change a few things. And on the 3rd try it got it right. Ralph with HITL might be a good bet.