Register and share your invite link to earn from video plays and referrals.

Jeff Ma
@18jeffreyma
CS PhD @Harvard + researcher @Meta Created
1K Following    1K Followers
super timely work, and a really great explanation for why models might feel "benchmaxxed"! SWE evals definitely feel extremely Markovian, which lends really well to compaction (since your codebase is essentially agent memory) real-world agent use is clearly multi-turn and partially-observable (uncovering requirements once you see your own spec assumptions challenged and overturned)
Show more
so exciting to see our work SWE-fficiency used and some really incredible results on designing agents for codebase optimization! one step closer to self-maintaining codebases :)
super refreshing take! i think the "software engineering is solved" perspective forgets that one of the most core parts of the job is turning smaller unstructured messiness/goals into a candidate (but likely imperfect and iteratively improved) artifact that helps more complex goals get solved. writing code used to be part of this recipe, but the supervision of the artifact is definitely still the same with agents code generation throughout the years has always been about putting bigger and bigger "holes" in your spec and and having an automated solver try and fill it in (it's a feature not a bug!), and while we should definitely strive for Good Code™, what makes code "good" has always been contextual: not just whether an implementation works, but whether its tradeoffs make sense for the messy, evolving goals of the system it's meant to serve. benchmarking this will be a super fun thing to do :) more interestingly, the frontier of software engineering research might increasingly be about understanding how much ambiguity we can safely delegate. making the holes in specs bigger is only useful as long as we can have reasonible feedback loops that tell us whether the solver filled them correctly, and the hardest part is often that we don't even know what correctness means until we've built something and seen how it behaves.
Show more
awesome to see our work featured again in another @AnthropicAI release, and some incredible multi-agent results in the Opus 5.5 model card evaluating how a swarm of 100 agents coordinates to solve ProgramBench! love how agents are becoming bigger computational threads: wondering if we'll need agentic system concurrency primitives as multi-agent really starts scaling
Show more