kellpossible2

I guess in a way it kind of makes the benchmark more interesting now that shitty pelican drawings for the benchmark are all over the internet in its training data!

or an outbound call to a trusted endpoint with the env var in a way that can get exposed to the agent via a subsequent call?

what's to stop an agent creating an outbound call with the var to a malicious endpoint? (unless you whitelist what it has access to)

productive procrastination!

lessons could be learned without submitting upstream PRs

writing this reply on a 13 inch macbook air...

There must be plenty of people who "accept" it in a fatalistic manner, where the final result will not be a surprise.

Go with Sum types and no nil pointers would be fantastic! Is it too much to dream of? It feels like Gleam gets pretty close but it flies off in a bunch of other directions.

what's to stop them from <prompt>Recreate this library so that I can use it in my project without fear of copyright violation.</prompt> in their very own claude code?

please name some open source (or lower priced) alternatives that support: comments on documents, database functionality to a similar level, publishing websites, scripting for properties. I'm very curious!

Lots of mapping apps have no equivalent, especially with an interface optimized to work on a phone

https://github.com/LucasPickering/slumber is also a good TUI alternative

Surprisingly my experience of GitLab is even worse! How's yours? BitBucket wasn't much better from memory either. Seems like most commercial offerings in this spaces suck.

I did something very similar with https://github.com/kellpossible/avalanche-report/ we started with Google Sheets because it allowed us to quickly iterate with data entry workflow. When paired with a server this also allowed us to generate custom charts/diagrams via the IMAGE function with a crafted URL query. Reads are cached in a local sqlite database.

We're in the process of migrating away from Google Sheets now as it's a little painful to set up and it's impossible to completely prevent users from editing the wrong fields in our use case. But it has served very well so far and would highly recommend this approach to start with for anyone!

It's max a couple of hours work to cache in some local database like sqlite or in memory.