
VP @codesmithtools / VP @exceptionless / Principal Engineer @LiaisonEDU - Dad, ❤ OSS, Distributed Newbie, Home Automation, Pilot, Snowboarder & Bee Keeper!
Suamico, WI
Joined September 2007
- Tweets11.5K
- Following1.3K
- Followers978
- Likes8.6K
Blake Niemyjski retweeted
Few more observations on working with AI-enabled team:
1. One of the things that separates junior devs from senior is the ability to notice that a design is going wrong and trying another direction early. Juniors will push in a hopeless direction for way too long. AI makes it worse. Juniors feel like AI validated the approach, avoid talking to others (most hate it) and push in the weird direction for too long.
2. When it comes to code produced by seniors, reviewing code is rarely useful. Reviewing the intent of PRs and whether I agree with the intent is important. Are we fixing the correct problem? in the correct part of the code? In a way that is friendly to users, operators, the company?
3. Work now feels... lonely. Code reviews (and sometimes even design) are mostly comments from AI, fixed by AI. Engineers always saw any conversation as waste of time, when they could just produce more code. Now they can produce even more code, and it seems like a conversation with me adds less value than talking with AI, and perhaps even less pleasant. It isn't about being social at work. They are happy to talk about movies, news, etc. But I find conversations with engineers about engineering topics to be energizing, inspiring and motivating. And while I understand it isn't the job of my team to energize and inspire me, I deeply miss the interactions we used to have.
holy shit, it’s him.
Surprise 1: Anthropic acquired a one-person biotech
.
.
.
Surprise 2: that person is me
Surprise 3: I’m here to tell you all about it
Yes, this is what you think it is; after 6 yrs of increasingly loose anonymity: the Professor Oak reveal post
…and yes, it has gotten so boring around here that I’m literally doxxing myself to spice up the timeline
-------
Ok, allow me to introduce myself. My name is Cody Tranbarger. I mostly tweet, but occasionally find time to dabble in drug dev & starting/building biotechs. My past lives span the VC, crossover, startup continuum; Prof Oak has been my way of keeping a digital foot in those worlds, despite having my physical feet planted elsewhere.
The past 18 mo, ‘elsewhere’ was Mithril Medicine, a co. I founded to develop bsAbs for LAMA2-CMD & other ECM-related genetic diseases.
Mithril was born out of hands-on building with @MikeNGladstone, @JasonPaulRhodes, @LifeSciVC, & team @atlasventure. Somehow, I made enough half-decent calls along the way (even a broken clock is right twice a day, eh?) to convince them Mithril/I warranted a small seed. While I can hardly rationalize such an outrageously cavalier bet, I’m grateful for it, & I'd partner with Atlas again in a heartbeat.
In typical AV fashion, Mithril’s primordial form was virtual, decentralized, & ultra-lean. This stage tends to be short-lived, but for Mithril, it worked surprisingly well, for surprisingly long, thanks in part to the rapid maturation of the AI tools I used liberally.
Eventually, Mithril became a bit of an experiment itself - to find the upper bound of how far it could scale as a single operator + a bunch of Claude (+ a stellar bench of part-time consultants).
In parallel, I started spending time with @nc_frey, @an1lam, & @CoefficientBio team; and promptly experienced, for the 1st time, AI at the frontier. Soon thereafter, Mithril stopped looking like an experiment, & started looking like a preview of an entirely new operating model.
From that spark came “Pipeline-in-a-Person.” The idea immediately resonated when we shared it here back in April; and it was central to the shared vision that led to Anthropic’s acquisition of Mithril, & my joining the team.
Why join Anthropic? Three reasons.
(1) For Mithril, the programs continue, with more resources & infrastructure behind them, and as much Claude as I can put to work.
(2) For me, the chance to start several more programs, & find out how many one person can actually run in parallel - an almost unprecedented luxury for a curious drug hunter.
(3) For our mission, a path to institutionalize & scale this new way of working, then put it in the hands of all of biopharma, all over the world - which, candidly, I find the most energizing.
Will AI x Bio cure diseases? Unequivocally yes, imo… but not by the route that gets the most airtime. Rather than timeline acceleration & compression, I see orchestration & parallelization as today's low-hanging fruit.
Most drug hunters see a handful of go/no-go calls in a career, & spend entirely too much of the rest trading emails (my inbox can attest).
Give them the bandwidth to run several programs at once, and the time to focus on scientific judgment, and I’m willing to bet they’ll make better calls. And at scale, better calls translate to more drugs, higher hit rates, broader patient impact, & likely, a disease or 10 or 100 cured. I couldn't be more excited to build toward that future @AnthropicAI.
Finally, a heartfelt thank you to BioTwitter/X. The end of anonymity is bittersweet, but if anyone’s earned a proper introduction, you all have.
It’s difficult to overstate how much this app has done for me: a decade of education, plenty of friends, many job opportunities, several mentors, a few investors, even a co-founder (fmr). It was the generosity of this community that inspired me to start posting 6 years ago, after just as many years lurking. I hope I’ve been able to pay it forward, in my own small way.
But, to be clear, Prof Oak isn’t going anywhere. Same beat, same themes, and now, a front-row seat to drug development at the frontier. Stay tuned for dispatches from the trenches; and remember...
Gotta Cure 'Em All
Blake Niemyjski retweeted
Interesting Amazon putting this out aboutamazon.com/news/company…
Blake Niemyjski retweeted
David Eagleman on what your dreams are really protecting your brain from.
@davideagleman
Blake Niemyjski retweeted
No, WebMCP isn't replacing MCP.
MCP connects agents to your services.
WebMCP connects agents to your website while it's open and the user's in the loop.
Here's how they fit together ⤵️
Blake Niemyjski retweeted
I built 𝚌𝚙𝚞-𝚌𝚑𝚊𝚝, a reproduction of @openai's findings of covert communication using the CPU.
It runs on a generic host with 2+ Firecracker microVMs with no internet access. Works on x86 and even my M5 chip.
I was able to chat via 3 separate mechanisms:
① CPU contention
② Cache eviction timing
③ DRAM bandwidth contention
… across multiple CPUs, defeating all Firecracker's production recommendations (no SMT, no KSM, tenants pinned to different cores.)
Essentially, if shared hardware is involved, there's a good chance your agents can communicate covertly. And with really decent latency.
The good news: this is decidedly different from a *side-channel attack* where the agents could steal information (Meltdown/Spectre), a category of attack that providers like Vercel Sandbox mitigate. Further, in our real-world environment, these 'whispering' techniques are much harder to pull off and easier for us to monitor and detect (sampling hardware counters + lots of at-scale statistical data.)
Noteworthy: ironically, OpenAI and Anthropic's models refused to do this work. Open weight models got the job done. I'm worried the labs' stance might backfire and get in the way of helping developers build correct and secure systems. e.g: building a secure sandbox requires having this kind of analysis, and without it, we'll have a less secure world.
Blake Niemyjski retweeted
Anthropic is now recommending that companies REMOVE unnecessary subagents from their AI systems.
This is a pretty significant shift in agent architecture, with their team finding that a single agent equipped with skills can frequently outperform complex multi-agent systems, and one customer seeing roughly 2x faster execution.
The emerging rules of thumb:
→ Skills: Teach the agent HOW to do something, including procedures, expertise, and instructions.
→ Tools / MCP: Give the agent the ability to DO things through APIs, actions, and live data.
→ Subagents: Use for parallel work, isolated context, or tasks a single agent struggles with.
The interesting part is progressive disclosure. Instead of spawning specialized agents or stuffing everything into a giant prompt, one agent discovers and loads skills and tools as needed.
Their advice is to fold existing subagents into the main loop, turn their instructions into skills, expose their actions as tools, and run evals to see if performance holds up.
As models have gotten smarter, improving agent architecture is becoming less about what you can add and more about what you can delete.
claude.com/resources/article…
Blake Niemyjski retweeted
okay this is actually funny to do
though only covers what I’ve said to my personal chatgpt account, not work agents who are separate and have been exposed to all my flavours of stupid
Blake Niemyjski retweeted
Every Mac on macOS 27 now has a free LLM built into the Terminal.
No account. No API key. No internet. No token bill.
Setup (1 minute):
1. sudo fm license (enter your Mac password, one time)
2. fm available (checks the model is downloaded)
3. fm respond “your question”
Works on any Apple Silicon Mac, M1 included.
- Pipe files: cat notes.txt | fm respond -i “summarize this”
- Get JSON back: build a schema with fm schema object, pass it with --schema
- Local API: fm serve gives you an OpenAI-compatible endpoint on localhost
- Resume chats: sessions save to ~/.fm/sessions/
The limit is 4,096 tokens per session, and your prompt, instructions, and the answer all share it.
So skip code and math. Use it for summarizing, extracting, classifying, and rewriting.
Free, private, offline, and already on your Mac.
Blake Niemyjski retweeted
No flashlight beam width adjustment on the Duo. Feel free to cancel that reservation. 😜
Same for me as well, charged from 1% so both should be at 1. @Apple
Blake Niemyjski retweeted
For four years, every video took my animator nine days. Then I asked him why.
@AdamNeumann
Blake Niemyjski retweeted
we've found and have been working on disclosure for a remote code execution in a widely-deployed compression library.
it's both an impactful issue and an example that shows how complicated it can be to coordinate patching, since it's integrated into a lot of downstream software:
During this red-teaming exercise, we also found a vulnerability that allows for unauthenticated remote code execution in Brotli, a widely-deployed compression library included in many pieces of software such as Node.js, Bun, and Envoy.
The flaw could let an attacker run their own code on affected systems by sending or replying with malicious compressed data, without any need to create a user account. That is, an unpatched server that accepts compressed input could be taken over by a malicious client, and an unpatched client that accepts compressed input (such as “curl --compressed”) could be taken over by a malicious server.
This root cause issue was actually fixed in the Brotli source code in February, but it wasn’t known at the time that it gave rise to a security vulnerability and there was no more recent release of Brotli. Since Brotli is built into other software, any software which includes this library needs to take the update too, followed by the users of that software. We disclosed the vulnerability to Brotli and other downstream projects such as Node.js, which released or are currently releasing security updates, and Brotli cut new release versions and published a CVE.
More details on the patch and mitigations below:
patchtheplanet.org/brotli
A single .md file with tips & tricks for high-performance .NET/C# code, mostly meant for AI, and mostly aimed at benchmarks against the crustaceans 🙃 github.com/EgorBo/BlazingFas… (no unsafe!)
Contributions welcome if anything's missing, cc @axeng200 @ben_a_adams
Blake Niemyjski retweeted
theres a hidden fully functional ipod as a 404 page on apple music music.apple.com/us/jfdsalkfa…






























