miguelspizza

I can’t even get past the popup on mobile to try it…

I recently took a contract with big tech after working with startups for about a year ( I was at this big corp a year ago)

Maybe it’s the small sample size, but from what I’ve seen, the thing hurting velocity more than anything is the fact that teams have too many “cooks”.

The way work is delegated is a bit broken when in reality the engineer who knows the code base or problem best should scope the work and just delegate it to their agents.

I can’t image how things look on the BI side.

I'm surprised I don't hear more people talking about code mode using existing SDKs for APIs like Google Workspace. That works so much better than converting the Google Workspace MCP JSON schemas to Types, then having the model write TypeScript to call those MCPs and then translate those back to JSON RPC calls. Just using that token from the MCP server and using the underlying fetch requests that the TypeScript Google Workspace SDK makes works infinitely better than teaching the model bespoke types. I'm assuming we're going to see a lot more of this as CodeMode gets more widely supported in harnesses

SAML is bad, but OAuth and OIDC are showing major cracks with identity and agents. Go to any major company right now and ask them how they are dealing with authenticating agents/what an agent identity even is.

The XSW part of the article was new to me though and kinda shocking

The article misses the point of MCP but he is not wrong that it was a mistake (in some ways)

The mistake of MCP was building it in such a way that it needed to be on a separate process from the API. The statefullness of MCP was such a massive detour for the industry that we will be cleaning up after it for years.

Now that MCP is stateless we can start building what is actually useful: extending API’s for agents.

When people ask me if they should do MCP today, I say absolutely. But because the Oauth protocol side of MCP is very good and is a net positive for all public API’s

This is not a dig at MCP, the original vision of MCP was much different from how the community used it.

The more I use the AIs the more I feel like I did at the end of reading blindsight. The things are undoubtedly “intelligent” by any practical definition of the word, but they are not aware.

This is also why I advocate against using AI as a writing partner. No matter the argument you lay out, a fresh context window will always have the “a few good things and a few bad things” feedback. There is no higher order opinion to align with.

The worst materialization of this are the slew of startups that are going to “watch your employees work so they can learn their job” as if random clicks on a computer can be reversed engineered to automate someone’s job.

This sort of audacity is a large part of the reason people increasingly hate AI

Not sure I understand the point your are making. how is this unique for bots with their own identity? Bots hijacking a user session can also be blocked

AI Session Hijacking is such a dead end and I think this will be the thing that kills it. Just register these things in the IDP and let them sign into their own accounts.

Maybe if we give these things their own identity people will stop letting their AIs post as them in linkedin

I used this for a POC analytics dashboard for a client recently.

Very very good, nice work.

What are your plans for the library?