@AnthonyCodexi
iAccount based inUnited States
About this account
- Account based in
- United States
- Connected via
- United States App Store
Account-level information from X, not a live location or the device used for a specific post.
tinkering with ai
Joined November 2016
- Tweets307
- Following97
- Followers33
- Likes507
Pinned Tweet
Step outside incentives (the goalpost) and really examine what’s happening externally (terrain) and internally (what I do and don’t know) - then direct efforts at the unknowns.
Do this long enough and without an ego.
And you get a feedback architecture.
On a brighter note, Wuxia open world and martial arts fighting game would compelling.
I can see the allure of exploring new territories and traditional customs, and engaging in legendary battles
I’d be interested
最近 X 上 AI 版 GTA 太火了!
奶奶版、护士版、辣妹版都看过了。
那我肯定要来点不一样的 —「东方武侠游戏」全新体验
用 @itsPolloAI 玩转 Seedance 2.5,
纵马、拔剑、踏入江湖。
武侠开放世界,正式开服,兄弟们,上号!🔥
This is good point.
It’s easy to focus on AI agents as tools during day to day work without thinking about the ramification about system architecture and requirements that these AI agents become clients of.
Learning to build more resilient backend infrastructure and API endpoints to the increased load from agents seems to be a very real need.
And related note, also how to better secure such systems from orchestrated agentic attacks by bad actors or similar exploits such as the HuggingFace incident.
For the last year, whenever I met other founders, I was asked "How did coding agents change things for you".
Obviously, it changed a lot internally. Coding, reviewing, fixing... But for me, the more interesting aspects is how the workloads on our system have changed. And what this means for distributed systems architecture.
I've been chatting (and sometimes info-dumping) on this topic for months now and I'm excited to share all these ideas with QCon audience! This talk will be 60% stories of what the agents did to various systems, and 40% ideas on how to build better systems for agents.
It’s a sharp framing.
AI empowers each team to output way more in a single sprint than pre-AI, meaning each “increment” is linearly/exponentially increasing in volume (code, features, and also bugs).
So while teams are still Agile, each increment is becoming more like a waterfall - large in scope, lots of code merged, too much for any team to get meaningful feedback on. This scale breaks the benefits of Agile’s small increments and feedback loop.
Good food for thought.
This vision of (fake)Agile👇 drives me nuts. Just No. There are no waterfall tracks. I collect just enough information to start, not finish, the work, and I do that just before starting. I write my tests first and run them every few minutes (TDD). I deploy often—minutes, not hours or days (CI/CD). I get feedback (and additional requirements) as I work and adjust what I'm building based on that feedback. The whole team works on each story and does not split the work into parallel tasks (scatter/gather). The relationships between stories are a (mostly undirected) graph, not a hierarchy (epics). There is no central orchestrator—decisions are made by the team as a whole.
There is nothing at all Agile about that diagram, though many people work that way. Small waterfalls are still waterfalls. This is a waterfall shop holding onto dysfunctional ways of working with a death grip.
Organizational maturity has never been more important.
Giving every employee an AI subscription can be roughly compared to hiring an average 5-10 extra workers (mileage may vary) per current headcount, and with that means more points of failure.
Feedback loop, direction setting, evaluations, observability… all matters when you have more “workers” in the picture.
This a good example of how building with AI and having productive discourse with an engaged community, that we can quickly discover what we don’t know and learn.
I think the core problem lies in choosing the right problem we want to sink our hours and tokens on.
Doing 10 things is good for discovery. To stand out above everyone else, do 1.
Replying to @dymokomi
Thank you! I am working on a deterministic algorithm to create different track types, I am refining it and adding a "difficulty" level from smooth to hell-no! 😂
Anytime you ship something mostly because it was cheap to build, that's AI slop for product.
I think slop may be more a decision problem than a quality problem. Every feature used to survive a resourcing fight before anyone built it, and that fight was quietly filtering out bad ideas for free.
Take the cost away and the filter goes with it. Nothing says no except taste now.
AI has collapsed the cost of building products, but not the cost of knowing what to build.
- The old loop: spec, scope, build
- The new loop: build, play, design, ship
Prototypes are cheap. Great products still require taste, judgment, and a clear understanding of what users actually need.
a16z's @joshelman on the artifact a product manager actually produces: a16z.news/p/product-manageme…
Anytime an engineer uses AI to build something without understanding the code is also vibe coding.
I think vibe coding may be more a state rather than an identity, at least for us with real software engineering experience.
I want to strongly echo this. Time and time again, I tried to do too much. It’s hard to say no to things that peek my interest.
Yet the truly life defining moments for me have been when I tripled down on one thing whether it’s some academic target or career milestone.
Learn to say no.
Having a singular focus on one goal is really powerful.
I don't think I had the luxury of being able to even have one all defining goal since I was 28 or so when I was trying to become a software engineer.
I had just quit my job as a PM at a hardware company, put my entire life on hold and just spent all my waking hour trying to learn this thing that had consumed my life.
Things progress really fast when you just have one focused goal.
No need to make plans, no distractions, no decision fatigue.
What would have taken you years can really be condensed down to months. Just think about college and the core eng classes. There is probably like 8-10 that is required info you actually need for work and the rest is just nice to know or if you want to specialize.
For one course
~3 hours of lecture per week
~15 weeks per semester
~45 hours of lecture total for the whole course
~360 hours of lecture time for the most important courses.
Its not a lot.
Yeah I know just listening to lectures is not the same as understanding but the point is that if you are focused you can get to your goal fast. Extremely fast.
There’s also the pretense of slowing down to fool competitors.
No one is stopping them from building in stealth, other than a few upstanding potential whistleblowing employees… though wouldn’t be surprised if they have NDAs for that
Two very real moats:
1) the sheer number of active real users
2) the resilient systems that allow an app like Instagram to operate at that level of scale and performance
Main gripe is
1) how inefficient and technologically unskilled the government is
2) how prone the government is to being strong armed by powerful and rich lobbyists
Contrarily, IPOs would give everyone more transparency than if frontier labs were nationalized
And we’ve all seen what happened the last time we audited the government spending…
serious question, at this point why not simply cancel the ipo’s & nationalize the labs?
theoretically nationalization would solve some of the incentive problems immediately. the us treasury becomes the only shareholder. the govt can coordinate compute, model releases, security standards, & pacing without asking rival firms to collude.
you could theoretically put openai, anthropic, & eventually other designated frontier labs under something analogous to a federally owned strategic technology corporation, with the president appointing the board rather than literally having sam & dario file weekly tps reports to the oval office.
Sharp point. Vibe coders optimize speed and won’t let lack of taste stop them. They just want a working app.
And for the ambitious vibe coders, nothing is stopping them from building taste if they tried inspecting and learning from every app they vibe out.
Nobody said “vibe” coders are replacing senior engineers on a 12 year old enterprise platform.
They’re building the other 90% of software:
a tracker for the shop
a family recipe app
a WordPress workflow that used to take a whole Saturday
a local agent that actually does one job
You don’t need to know every framework convention to ship that.
You do need taste, persistence, and the ability to tell the model “that smells wrong, try again.”
That’s the new class.
Not “fake developers.”
Just people who can now finish things they used to only describe.
I’d venture people should have access to large portions of a workflow to reduce dependencies on others.
A 10 step linear workflow can then be chunked into 3 parts, reducing the dependencies from by over 400%.
The addition of an embedded browser to cmux is fascinating. On one hand, you could argue we’re slowly reinventing the VS Code webview model from the terminal up. On the other hand, co-locating browser previews directly alongside agent workflows and terminal logs in a native split completely removes context-switching friction.
Feels like an inevitable baseline feature - it’s only a matter of time before other multiplexers and harnesses follow suit.