the added benefit of investigation first is you get verification steps out of the gate vs post-fact - the combination of anchoring your interaction with data gathering and verification baked in allows extended task horizons with significant outcomes.
The step change btw a prompt starting from a problem vs data gathering is the single largest step change you can make _today_ for your trajectory outcomes.
i.e:
> "page is slow when i ___ ... fix it"
V.
> "visit site[dot]com and collect a devtools trace..."
models have been post-trained to bend to your will - when you say something is slow - the model is going to make up 100 reasons for the slowness in thinking tokens
If you start by seeding the context window w/ perf data you anchor the interaction in data not hallucinated rational
diffshub[dot]com
Take any public diff from GitHub and virtualize it nearly instantly, no matter how large, with DiffsHub. Built to show off our brand new CodeView component.
To try it out, replace `github` with `diffshub` in your address bar.
🔨agent experience is the new developer experience
🗺️agent trajectories are the new friction logs
🧨The path to 10xing does not come from increasing token burn ... Efficacy of task and laser focus on understanding what is going wrong is the bottleneck - NOT YOUR MODEL.
Everyone is waking up to the fact that code-review is the bottleneck of 2026
I'm bullish on ramping review agents - but the vibes coming from
- https://t.co/m6s2fl9Sc9
- https://t.co/01VI28Obrx
- https://t.co/mcJaWwoEfB
start to hit closer to home on where we need to go
For earth day, Pierre Computer Company is excited to announce the first public preview of…
TREES[DOT]SOFTWARE
A new, feature rich trees library – tuned for machines.
Demo of AOSP fixture (1.5 MILLION files with fixed dirs - no blanking)