Austen Allred

57.7K posts

Austen Allred banner
Austen Allred

Austen Allred

@Austen

Founder https://t.co/m6TigM4CJT: Free AI training for the smartest engineers. Will tweet as I wish and suffer the consequences. Accelerando: @kellyclaudeai

Austin, TX Katılım Aralık 2010
1.5K Takip Edilen466K Takipçiler
Sabitlenmiş Tweet
Austen Allred
Austen Allred@Austen·
Any time there’s a “flat org chart” and it actually works it’s because the entire company reports directly to one god-emperor who makes 999 decisions/day
English
88
140
9.1K
386.3K
Austen Allred
Austen Allred@Austen·
@jgebbia Also claw it all back. Anyone involved should have all of their assets seized and auctioned and every penny they earn taken.
English
0
0
8
582
Austen Allred
Austen Allred@Austen·
The average American will work their entire lives and pay $525k in federal taxes. So, on average, 2,667 people had to work and pay taxes for their entire lives just to fund last year’s hospice fraud in LA county.
Austen Allred tweet media
English
2
9
87
3.3K
Lydia Hallie ✨
Lydia Hallie ✨@lydiahallie·
@backnotprop @ClaudeDevs No extra cost, and yes it still runs on your subscription. claude -p just gets its own included(!) budget now,($20–$200/mo depending on plan) instead of sharing limits with interactive Claude Code ugly diagram but maybe it helps:
Lydia Hallie ✨ tweet media
English
11
1
6
6.8K
ClaudeDevs
ClaudeDevs@ClaudeDevs·
Starting June 15, paid Claude plans can claim a dedicated monthly credit for programmatic usage. The credit covers usage of: - Claude Agent SDK - claude -p - Claude Code GitHub Actions - Third-party apps built on the Agent SDK
English
848
589
8.9K
4.3M
Austen Allred
Austen Allred@Austen·
It’s dramatically more expensive but you get a few free credits toward the new expense to soften the blow. Your users aren’t dumb. Stop trying to dress everything up in 10 layers of PR speak and just say what it is.
Lydia Hallie ✨@lydiahallie

To add some clarity: you don't pay extra. It's the same subscription, same price per month. What's new our sub now covers two separate pools: · Interactive → sub limits, unchanged · Programmatic → new $20–$200 included(!!) credit, metered at API rates

English
4
4
87
9.7K
Austen Allred
Austen Allred@Austen·
Anthropic is trying very, very hard to have maximum price discrimination based on whether or not your code is being run “programmatically” or not. This, not surprisingly, is kind of confusing to programmers.
ClaudeDevs@ClaudeDevs

Starting June 15, paid Claude plans can claim a dedicated monthly credit for programmatic usage. The credit covers usage of: - Claude Agent SDK - claude -p - Claude Code GitHub Actions - Third-party apps built on the Agent SDK

English
13
6
261
43.7K
Austen Allred retweetledi
Matt Hulme
Matt Hulme@MattHProgrammer·
Speccing out the next big feature for @mopacsoftware today. Hint: it's really cool
English
2
1
3
2.8K
Austen Allred
Austen Allred@Austen·
Another filming day for a new secret thing at Gauntlet AI
Austen Allred tweet media
English
5
0
15
2.2K
Juniper
Juniper@JuniperViews·
@Austen What? How do you solve token burn by thousands of employees with "tooling"?
English
1
0
2
342
Austen Allred
Austen Allred@Austen·
This feels solvable with like 10 minutes of tooling? Am I missing something?
Laura Bratton@LauraBratton5

New: @ServiceNow is the latest major public company to say it’s blown through its full year budget for AI coding tools from Anthropic in the first few months of 2026, just like @Uber CTO @praveenTweets said abt his company. “It’s a really hard problem,” CIO Kellie Romack said.

English
12
0
27
12.3K
Austen Allred
Austen Allred@Austen·
Gauntlet AI is a factory for turning traditional engineers into AI-first forward-deployed engineers. We spend all day every day making them. DM me and we’ll help you get them.
Aaron Levie@levie

Forward deployed engineers, or equivalent, are about to become one of the most in-demand jobs in tech. And one of the most important functions for AI rollouts. Deploying agents is far more technical of a task than most people realize, often far more involved than deploying software. Software generally works the same way every time, and generally for the past few decades has been updated versions of an existing technology or concept (which basically means easier for the enterprise to update their workflows on a newer system). With agents, you’re actually deploying the equivalent of work output within the enterprise. The customer is effectively using you as a professional services provider for a task, which they expect to get solved nearly end-to-end now. This means you need to actually deeply understand the business process as a vendor, and get the customer from the current to the end state seamlessly. Companies need help figuring out which models will work best for their workflows, they need extensive evals setup often, they need change management support for workflows, they need to get their data setup for the agents, and constant tuning of the agentic system for their process. Massive role in tech now. And another example of the kind of highly technical work that AI is creating.

English
2
5
38
10K
Invidium0x
Invidium0x@invidium0x·
@Austen Why is everyone acting like Tim Apple is new?
English
1
0
2
189
Austen Allred retweetledi
Eric S. Raymond
Eric S. Raymond@esrtweet·
It can be unsettling when you notice that a technical assumption you've been making for 40 years has quietly expired. This happened to me a few minutes ago. I maintain a game called "greed". It's an old-style game from the days of character-cell terminals. Not quite a classic deserving of museum status like Colossal Cave Adventure or nethack, but worth keeping alive because it's still solidly playable. And people still are playing it, because yesterday I got a minor bug report about it. Nothing user-visible, just a silly C build problem. I fixed it. Then, because I'm generally trying to get my old C projects out of C into more modern and safer languages, I tried asking my robot friend to port it to Rust. Which it promptly did. But then I noticed something that irritated me. The Rust code had a bunch of unsafe blocks in it, which went directly against my reasons for moving it to Rust. On further examination, I discovered that it was calling the C curses library to do its screen painting. This is where I have to explain about curses. It's an ancient C library for writing TUIs. It looks in your environment for a variable named TERM, uses its value to dredge a bunch of magic strings out of a system-wide database called "terminfo" that tells it how to manipulate your terminal, and then uses those magic strings for screen painting. On modern systems, TERM is always some variant of a color ANSI terminal. In times past, when people attached a wild variety of character cell terminals to Unix systems rather than just sitting at the console, it could have been lots of other things. Those days are gone, but the habit of always going through terminfo so you can support a couple of hundred terminal types has persisted. I prod robot friend to find me a pure Rust equivalent of curses so I don't have to do unsafe and call C code. It says, yes, there is such a thing and it's called crossterm. I tell it: change this code to use crossterm. Robot friend grinds for a bit, and then tells me it can't do that because I don't have cargo (the Rust package manager) installed. This is because I never write Rust by hand. When I ship programs written in Rust, it's because I ported them from some other language and don't expect to ever touch them again without having a robot to do the code-grinding for me. This is when things get slightly strange. It tells me that instead of porting to crossterm, it has written into the greed Rust source its own little screen-painting backend the implements a subset of curses calls and (this is the important part) assumes it's talking to a color ANSI terminal. Robot friend is not an old Unix hand. It doesn't know the unwritten law of the deep magic that you always go through terminfo because...because you might have to support hundreds of terminal types that no longer exist in this century? I blink. I look at the Rust code for the back end. It is small and elegant. No more unsafe. No more dragging around a bunch of C library code. This is ... the right thing? I push it to the public repository. What sealed the deal is that code, even code in a language as rebarbative as Rust, is wet clay now. If, against all odds I get a bug report that says somebody wants to play greed on something that isn't an ANSI terminal emulator, reinstating full curses support will take a one-sentence prompt to my robot friend and mere minutes. I hadn't had to directly confront before the fact that the entire set of assumptions that made TERM and terminfo a thing are as obsolete as dial-up acoustic modems. Still, the moment when I tossed away one of the ancient laws of Unix coding felt a bit like the universe lurching sideways. Indeed do many things come to pass...
English
118
146
3K
208.3K