spooneybarger

Unless something has changed in the last year, a lot of teams have serious problems with stability.

It's taught in at least one of the universities there.

I've gone back to using Opus 4.6. It's quite nice along all these fronts.

Thank you. The tweet values the readers time. The blog post. Dear lord. So much noise.

This was a great summation.

well played sir. well played.

I, as a human, find that website decidedly unfriendly to quickly getting information. Particularly on mobile.

Same. But I got one from Anthropic.

It was never alpine.

Because the only thing keeping those vulnerabilities in existence was laziness.

Cirrus gave a ton of support for years to open source projects. I congratulate them on cashing out. Running a business like Cirrus did is always a hard road and I will never fault folks who gave time and resources on their platform away for taking the money.

I wish Fedor and everyone at Cirrus the best of luck and OpenAI and thank them immensely for the years of free CI they gave to us in the Pony programming language despite it not having any marketing value to them.

That's a very small list.

No

An important step with property based testing and similar techniques is writing your own generators for your domain objects. I have used to it to incredible effect for many years in projects.

I work at Antithesis now so you can take that with a grain of salt, but for me, everything changed for me over a decade ago when I started applying PBT techniques broadly and widely. I have found so many bugs that I wouldn't have otherwise found until production.

Came through personal contact who is close to the family.

Yes. He died last week.

More stuff for pony than you can shake a stick at.

predicting that a startup will fail is.. well, you got a ton of probability on your side there. so it isn't a particularly impressive thing to be right about.

well played sir. well played.

Well played sir. Well played

That's an exceedingly unkind summation of the piece in question.

No

working fine for me.

Well played sir. Well played

The OxCaml work is great. I don't use OCaml much but I have been following along with OxCaml as they are doing fascinating work that leverages a lot of research that interests me.

As a general rule, not all system calls are thread safe.

500k tech workers have been laid off since accounting for expenses under Section 174 changed on January 1, 2022.

This sounds like my experience with a "major" technical publisher except we managed to get to the end.

I'd say that almost no one should work with the major technical publishers more than once. There's some good basic skills you learn but otherwise, they contribute very little that you couldn't get done on your own.

Yes

There are a lot of public facing graphql servers that use it without issue other than frustrating users of non adversarial but complex requirements. The problem is that it is generally on a per request basis.

An adversary is going to utilize more than a single query. It mostly protects against well intentioned folks.

Other forms of protection such as rate limiting are needed for threat models that involve an adversary.

The same problems exist with REST but there it is easier as you can know query complexity ahead of time at end points. GraphQL has to have something to account for the unknown query complexity, thus the additional heuristics.