You thinking of moving to management or not?
Well, I'd say before you do that invest at least 10 minutes to get a glimpse from you what that (brutal) change can mean for you!
@DavidKPiano It might be unpopular for some parts in tech where besides tokenmaxxing and leaderboards nothing is accepted, but other then that this is exactly where Iβm right now.
No slow down, no βNoβ accepted bc build is βcheapβ or βfastβ.
1/2 Why AI is unlikely to become conscious β my 2026 @TEDTalks is now online. What do you think about the prospects for 'conscious AI'? https://t.co/OoXFavR3eG
This week it looks like @SpotifyEng & Product can't stop shipping;
As a paying customer (Spotify Family) I'm now randomly getting Ads inserted randomly.
I hope this is 100% a Bug (too much vibe coding with the AI Slack Bot?).
FFmpeg is moving to Rust π¦
Our use of C and Assembly in FFmpeg has been an unacceptable violation of safety.
FFmpeg will be running 10x slower - but we're doing it for your safety.
All your videos will appear green - safety first, working software later.
@thdxr I guess that's the difference when using experienced brain & design thinking vs. "claude we need this feature" :D
still claude code is running nicely, which gets me thinking how good opencode will π€
The next step for autoresearch is that it has to be asynchronously massively collaborative for agents (think: SETI@home style). The goal is not to emulate a single PhD student, it's to emulate a research community of them.
Current code synchronously grows a single thread of commits in a particular research direction. But the original repo is more of a seed, from which could sprout commits contributed by agents on all kinds of different research directions or for different compute platforms. Git(Hub) is *almost* but not really suited for this. It has a softly built in assumption of one "master" branch, which temporarily forks off into PRs just to merge back a bit later.
I tried to prototype something super lightweight that could have a flavor of this, e.g. just a Discussion, written by my agent as a summary of its overnight run:
https://t.co/tmZeqyDY1W
Alternatively, a PR has the benefit of exact commits:
https://t.co/CZIbuJIqlk
but you'd never want to actually merge it... You'd just want to "adopt" and accumulate branches of commits. But even in this lightweight way, you could ask your agent to first read the Discussions/PRs using GitHub CLI for inspiration, and after its research is done, contribute a little "paper" of findings back.
I'm not actually exactly sure what this should look like, but it's a big idea that is more general than just the autoresearch repo specifically. Agents can in principle easily juggle and collaborate on thousands of commits across arbitrary branch structures. Existing abstractions will accumulate stress as intelligence, attention and tenacity cease to be bottlenecks.
@zorkian@tdoot_ Cool as an Engineering Challenge but:
- If thousand employees create internal apps daily, whatβs the plan of maintaining them?
Or they are killed, delete within w day of not using?
Excited to share that I've stepped into a new role as VP of the Agentic AI Foundation (AAIF) π
As AI reshapes our industry, it's critical that this technology evolves in ways that are open and collaborative.
Hosted by the Linux Foundation, @AgenticAIFdn is a neutral organization focused on advancing adoption of key open source efforts like MCP, AGENTS.md, and Goose. Our members include Anthropic, OpenAI, Google, AWS, Microsoft, and 100+ others.
This work is bigger than any single company or product. I'm ecstatic to help drive AI adoption and interoperability at an industry-wide level.
Short thought:
- Platforms should invest into proper CLI not MCP.
- CLI >> MCP.
I see less and less value in MCPs creating huge bloated Context vs. Coding Agents having skills, knowledge of CLI cmds to use.
+ with CLIs we know how to do auth/security.