Brady Joslin

Sr. Director, Engineering - Industrial IoT platforms.

🤖 Go & JS mostly, programming language promiscuous.

🐇🕳️ Wasm, plug-in architectures, extensibility.

[Brady Joslin @bradyj]

Humans bottleneck agents when HITL means inspecting outputs instead of managing outcomes.

[Brady Joslin @bradyj]

@nilslice Can you tell I had a python-based morning? haha

[Brady Joslin @bradyj]

Implementation: https://t.co/tk6EtVghHY uses wasm-based servlets to defend against tool poisoning attacks.

They run in isolated environments with explicit permission gating, enabling secure execution without compromising flexibility.
https://t.co/ZRmd0sADej

[Brady Joslin @bradyj]

MCP implementations raise unique security challenges.

Here’s a quick overview of recent architecture, middleware, and implementation approaches for securing them.

Before rushing into production, here’s what you need to consider.

[Brady Joslin @bradyj]

Framework: MCP Guardian is a framework for security middleware that sits between MCP clients and tool servers.

It handles authentication, rate limiting, and logging, centralized and consistent, with no changes to individual tools.
https://t.co/Rah2IPgtI6

[Brady Joslin @bradyj]

Read here:
https://t.co/J7JtCpLhpP

[Brady Joslin @bradyj]

AI isn't just software. It's labor.

It’s not here to replace your team, but to work for them.

Every employee should be empowered to direct AI labor.

That’s the core idea behind The AI Labor Playbook by Jules White. Highlights below.

[Brady Joslin @bradyj]

That’s the leverage in the modern economy.
Those who can direct AI labor will outperform everyone still trying to “use tools.”

[Brady Joslin @bradyj]

Speed and adaptability will be the primary sources of leverage in the GenAI era. But most companies are repeating the same old mistakes, overly focused on step-change automation.

Coordination, not intelligence, is the real unlock.
https://t.co/OqN3sU3LNr

[Brady Joslin @bradyj]

@kentcdodds “MCP isn't just about individual services. It's about getting different services to talk to each other seamlessly.”

You nailed it: glue code without the glue, just natural language doing the stitching.

[Brady Joslin @bradyj]

I’ve been trying to make sense of the new tariff policy—the backing theory.

It’s built on a premise: tariffs, paired with currency shifts, can rebalance trade without raising U.S. prices.

The theory seems wishful. The rollout makes it unlikely.

https://t.co/Ql4Thy8ft8

[Brady Joslin @bradyj]

@nilslice Web 2.0 was the read-write web.
MCP is the read-write logic.

[Brady Joslin @bradyj]

@nilslice Web 2.0 was the read-write web.
MCP is the read-write logic.

[Brady Joslin @bradyj]

@GergelyOrosz @joeton @Pragmatic_Eng Really enjoyed that particular insight from the article, how patterns from their work with LSPs served as creativity for the basis of the protocol.

[Brady Joslin @bradyj]

LLMs can be confidently wrong.
That isn’t a bug - it’s a mirror.

Of course they share our flaws,
they’re made to communicate like us.

Don’t try to use them as truth machines.
The leverage comes from the conversation -
the space to think, reflect, and understand.