Possibly things are worse, but here’s an argument that we’ve gotten unrealistically ambitious about universal education through college:

What People Want From Our Schools Has Never Been Accomplished, Anywhere, Ever https://freddiedeboer.substack.com/p/what-people-want-from-o...

I don’t know if it will work, but here’s a startup that seems to be building an AI-controlled shotgun:

https://www.ycombinator.com/companies/9-mothers-corporation

Given the war in Ukraine, wanting to build such things is certainly understandable. But still, this is the stuff of nightmares.

I wonder who the audience is for an announcement about spending a lot of money on something vague?

I think that might make sense for teams or people working in multiple repos. Maybe less so for individuals working on a side project.

If it's a remote API, I suppose the argument is that you might as well fetch the documentation from the remote server, rather than using a skill that might go out of date. You're trusting the API provider anyway.

But it's putting a lot of trust in the remote server not to prompt-inject you, perhaps accidentally. Also, what if the remote docs don't suit local conditions? You could make local edits to a skill if needed.

Better to avoid depending on a remote API when a local tool will do.