Phillip Carter

Why they matter

Practitioner with public evidence across Compute & infrastructure.

AI signals
6
past 30d
Sources
6
distinct domains
Discussions
43
past 30d
Latest signal
14d ago
View every signal from Phillip Carter →
morbjs maintainer work: salesforce, past @honeycomb.io and @microsoft.com play: computers, backpacking, snowboarding, hiking, kayaking

Articles & links

More to throw in the Big Deal pile openai.com/index/openai...

openai.com
View on Bluesky · ♥ 1 ↻ 0 ↩ 0 · 3 from the directory shared this · 54d ago

Well this reads as quite the combo breaker, at least with agents powered by LLMs ~3 months ago, developer-submitted and LLM-created AGENT md files don't seem to improve task performance for python projects, but do burn ~20% more tokens arxiv.org/abs/2602.11988

Evaluating AGENTS.md: Are Repository-Level Context Files Helpful for Coding Agents? arxiv.org
AI Weekly's analysis
  • Context files like AGENTS.md tend to reduce coding agent task success while raising inference cost by over 20% on average, the paper reports.
  • On a new 138-issue Python benchmark, LLM-generated context files added 3.92 steps per task and pushed costs up by 23%.
  • The finding held across Claude Sonnet-4.5, GPT-5.2, GPT-5.1 mini and Qwen3-30b-coder, so it is not tied to one model family.
Read full analysis →
View on Bluesky · ♥ 26 ↻ 2 ↩ 4 · 2 from the directory shared this · 50d ago

Holy shit this is awesome, hand-cranked LLM inference squeezlabs.github.io/handcrank/

CrankGPT — fully offline, human-powered local AI squeezlabs.github.io
AI Weekly's analysis
  • CrankGPT runs a full voice-interactive AI pipeline on a Raspberry Pi 5 with 8GB RAM, powered solely by a 20W hand-crank generator.
  • Cold-start to functional conversation takes roughly 30 seconds; time to first token ranges from 0.8 to 2.9 seconds depending on model size.
  • Memory bandwidth, not raw compute, is the primary bottleneck for on-device LLM inference, with DDR5 hardware achieving 29-58% faster token generation than DDR4.
Read full analysis →
View on Bluesky · ♥ 3 ↻ 2 ↩ 0 · 7 from the directory shared this · 64d ago

Some early research definitely shows less click-throughs, but it doesn't say much about if the clicked link was a garbage site or not. In theory with wikipedia, .gov, reddit, etc. showing up more in sources there's more opportunities for better content I guess www.pewresearch.…

Do people click on links in Google AI summaries? | Pew Research Center pewresearch.org
AI Weekly's analysis
  • Pew found Google users click a traditional search result in 8% of visits when an AI summary appears, versus 15% without one.
  • Users clicked on a link inside the AI summary itself in just 1% of visits, per Pew's 68,879-search dataset.
  • Browsing sessions ended on 26% of pages with an AI summary, compared with 16% of pages without one.
Read full analysis →
View on Bluesky · ♥ 9 ↻ 4 ↩ 2 · 2 from the directory shared this · 49d ago

I'm about 25% accurate on takes so my take is that this is going to be wildly successful for OpenAI ads.openai.com

ads.openai.com
AI Weekly's analysis
  • OpenAI opened its 'Advertise in ChatGPT' self-serve portal on July 22, 2026, with Best Buy, Lowe's and VistaPrint as named early advertisers.
  • Sponsored blocks appear below ChatGPT responses and are served only to adult Free and Go plan users; Plus, Pro and Business remain ad-free.
  • Targeting runs on conversational context signals rather than keywords, and OpenAI states ads do not influence ChatGPT's answers.
Read full analysis →
View on Bluesky · ♥ 1 ↻ 1 ↩ 1 · 27d ago

Recent commentary

job change out --> salesforce in <-- github Gonna help build some systems behind Copilot and see if we can make it way more capable than it is today. So much ground to cover for all coding agents, maybe Copilot will soon be The One now that claude has murky vibes

View on Bluesky · ♥ 85 ↻ 2 ↩ 9 · 6d ago

Oh not a whole lot of PMs in my follows but two bad things are currently surging in PM world: 1. Writing overly verbose specs/PRDs with AI, not even bothering to get creative with prompts 2. Using claude code to spit out a hifi gestalt of a UI prototype and dev teams getting pressured to ship

View on Bluesky · ♥ 46 ↻ 7 ↩ 7 · 78d ago

Still stunlocked that Marc Andreessen and his big brain prompts AI models with “don’t hallucinate”

View on Bluesky · ♥ 57 ↻ 2 ↩ 5 · 50d ago

My dumb AI take of the day is that I think it was wrong to introduce 1M+ context windows on account of coherence != capacity

View on Bluesky · ♥ 24 ↻ 1 ↩ 5 · 71d ago

What's the state of the art on coding agent memory these days? I haven't used it much, at least not with Claude. So far the best memory implementation I've seen is just normal ChatGPT. It seems to do retrieval quite well.

View on Bluesky · ♥ 10 ↻ 0 ↩ 9 · 52d ago

I hadn't realized how easy it is to get started with base llama.cpp these days. I gave up on ollama a while ago since they started getting weird. Anyways: brew install llama brew install pi pi install git:github.com/huggingface/pi-llama llama serve <model> pi Got muh gemma4 on muh macbook

View on Bluesky · ♥ 22 ↻ 1 ↩ 2 · 62d ago

I see ChatGPT has no sense of irony. Or maybe it has an incredible one?

View on Bluesky · ♥ 15 ↻ 1 ↩ 1 · 13d ago

It's nuts how much a modern codebase with good DevEx practices can move so fast with AI compared to ... not that. One of my teams now has daily (as opposed to weekly) turnaround times for most features with Claude. Another team's "velocity" is imperceptible compared to a year ago.

View on Bluesky · ♥ 14 ↻ 1 ↩ 1 · 31d ago

I think there’s something to it that Ed Zitron gets a lot of readers who love his overly verbose writing … and that a lot of people get impressed with the overly verbose words barfed out by LLMs in default settings These groups are nominally non-intersecting but I don’t buy it

View on Bluesky · ♥ 12 ↻ 0 ↩ 2 · 73d ago

I bet Terry A. Davis would be doing some pretty wild shit with LLMs if he were around today

View on Bluesky · ♥ 11 ↻ 0 ↩ 0 · 17d ago

In Phillip Carter's orbit

Center = Phillip Carter. Left = members they follow (green edges). Right = members who follow them (blue edges). Top = mutual follows (orange edges, slightly larger). Drag any node to reposition; click to open that profile.