Simon Klee
413 posts

Simon Klee
@simonklee
Recovering web dev. @opencode at @anomalyco


My brain is reeling with the implications. I keep having these revelations and I'm beginning to wonder when they will stop. It turns out that property testing is yet another hardening technique that the agents can profitably engage. Agents can determine whether a function is appropriate for property testing, and can specify the range and domain of those tests. They can implement them quickly, run them, and fix any detected issues. I just found two production bugs this way. Property testing is going to be part of my normal practice, along with Crap analysis, Function mutation, acceptance test mutation, Dry analysis, etc.


You get used to it. I don't even see the code. All I see is blonde... brunette... redhead...






An early beta of Grok Build, an agentic CLI for coding, building apps, and automating workflows is now available for SuperGrok Heavy subscribers. Through this early beta, we will improve the model and product based on your feedback. Try it at x.ai/cli



For you this is probably the right decision. You know best. Your product. From my point of view it means less stability because this version of Bun has not been used on millions of computers with endless of configurations (yet). For the foreseeable future this will stay true independent if ClaudeCode ships using it. Bad news because less bug fixes to the version of Bun that has been tested and used by millions of users.


For you this is probably the right decision. You know best. Your product. From my point of view it means less stability because this version of Bun has not been used on millions of computers with endless of configurations (yet). For the foreseeable future this will stay true independent if ClaudeCode ships using it. Bad news because less bug fixes to the version of Bun that has been tested and used by millions of users.




















