aranw

When I saw the blog post about DeltaDB I thought oh okay cool but so what I don't really know what this is for me and how it helps me or what it does for me. Then again today I saw this link and looked at it and I can't help thing what is this to me? How does this help me, why would I want to request early access cause I have no idea what it does?

I'd much prefer some more time spent building a solid editor which is why I switched to Zed early on in it's development cause I was frustrated and tired of VSCode. But saying that ever since Zed AI I've felt more and more frustrated with Zed and it's quality is starting to lack?

Is this closed-source? I was unable to find a link to the source code for it?

t once had to tell claude 3-4 times to stop assuming the state of a system was the way it kept iterating it was cause it was in it's memory. I repeatably told it to otherwise and it just never updated it's memory and instead kept referencing it's memory about the state of a particular system

I really like Zed but it's most recent big changes to Git integration and Parallel Agents has forced me to disable both of those features as the way they work just didn't suit me and my workflow

The Parallel agents feature seems to be built around git worktrees or local projects. But I think local project mode defeats the point. In my day to day development workflow I've switched fully to jj and jj workspaces, so this isn't something I'll be using until Zed gets jj support. Also this change ended up with a reshuffled layout I didn't really expect and I can't really figure out how to revert it now

Really enjoyed that although my final two tiles were stacked and couldn't finish the game!

Was on an overnight bus and ended with game over

I've written to my MP several times about this. Each response just repeats the same talking points about safety whilst completely missing the underlying technical issues and consequences.

Which SQLite Go library do you use? My biggest pain with using SQLite in Go is often the libraries and the reliance of CGO which is what puts me off using Turso

Edit: Looking at the go mod file I noticed github.com/mattn/go-sqlite3 which I think is a C wrapper library so I'm assuming you rely on CGO for compiling

The problem with mocks is that they test your assumptions, not reality...

When you mock a CRM client to return one account, you're assuming it always returns one account, that IDs have a particular format, that there's no pagination, that all fields are populated. Each assumption is a place where production could behave differently whilst your tests stay green

Your contract tests use cached JSON fixtures. Salesforce changes a field type, your contract test still passes (old fixture), your mocks return the wrong type, production breaks. You've now got three test layers (contract, mock scenarios, E2E) where two can lie to you. All your contract and mock tests won't save you. Production will still go down

I have zero confidence in these types of tests. Integration tests and E2E tests against real infrastructure give me actual confidence. They're slower, but they tell you the truth. Want to test rate limiting? Use real rate limits. Want to test missing data? Delete the data.

Slow tests that tell the truth beat fast tests that lie. That said, fast tests are valuable for developer productivity. The trade-off is whether you want speed or confidence

> I really dislike this idea of testing in go: only ever use an interface, never the real implementation + mockgen the mocks based on this interface + use the mocks to assert that a function is called, with exactly this parameters and in this exact order.

Same I have zero confidence in these tests and the article even states that the tests will fail if a contract for a external service/system changes