i have ai psychosis and completely changed my schedule this year to maximize agent output.
what I’ve learned:
1. if you have N working hours, it’s now beneficial to spread those out as much as possible instead of work continuous blocks. aka work more days and start earlier/end later, but with more breaks.
models can work autonomously for days but still need your direction, and you need to sometimes unblock them. frequent touch points are important for that.
e.g. much better to find out at 7am that your models got stuck, and get two hours of progress before your work day, than find out at 9am.
similarly, a quick check-in on sunday morning sets up your models for a day of work.
this doesn’t have to mean actually working more hours if you don’t want to. a five minute chat from your phone is enough.
2. there’s now an entire second workday that can happen while you’re asleep. but it only happens if you make sure your models can work overnight.
it’s crucial you spend the end of your workday setting up your overnight agents for success.
my lazy life version looks like this: every night at ~9pm i go on a run, dictate what i think should happen while i'm asleep, and dump the transcript into grok bot. it takes 10 minutes and results in eight hours of work.
3. prioritize short, high intensity work sessions over long hours.
when you’re in front of your computer, all your time should go to unblocking your agents with *high quality* ideas and decisions, e.g. doing Matt Pocock style grill me sessions.
alternating a few high quality planning sessions with touching grass is more valuable than spending twelve continuous hours babysitting agent traces.
ofc it’s beneficial if you’re able to combine intensity with long hours, but that’s harder.
it reminds me of how athletes train: workout heavy multiple times a day and focus on recovery in between.
4. do whatever you need to maximize your capacity for idea generation and decision making.
don’t make stupid health and sleep sacrifices in pursuit of productivity.
you’re no longer getting paid for brute forcing solutions. that’s what agents are for.
it’s much better to get good sleep than 996 if the latter makes you even a tiny bit less focused or creative the next day.
I just finished talks about my software factories at two conferences. Afterwards a bunch of people came up and told me what they were surprised about. Here is a distillation of what people thought were hot takes from my two talks.
First hot take: I tell everyone to slow down. Most speakers go on about how fast they're going, but I strongly believe in pacing AI outputs to human speeds. I regularly tell AI-pilled CIOs and CTOs to chill: almost nobody is _actually_ going fast with AI. Engineering still moves at engineering speeds, and business moves even slower. The ones pushing too hard are starting to see downtime for it.
If you don't pace your AI to human speeds, everything starts breaking around you, even at small operations like my online video game. I only have about a dozen humans working with my factory, and only a few hundred active old-timer players in the community who get along well, and still, introducing AI has still been very rocky.
My agents have, at times, overwhelmed my players with features, my accountant with emails, my merge queue with tickets, and my machines with load. Agents have pissed off my admins, resulting in name-calling, they've made messes in the game, and they've launched broken OSS without permission. The list goes on.
I can get away with all this chaos because everyone involved in my operation is very forgiving. They're excited by the potential. But even so, I had to learn to slow down, real fast. And so that's what I preach.
Hot take #2: Should you buy a software factory? Do you even need one? No. You probably don't need one. Factories take an extraordinary amount of upkeep. They turn into garbage mountains unless you put a frightening amount of time and tokens into curating them. I had to burn my previous five factories down since it eventually became cheaper to rewrite them than to fix them. So I'm not out there advocating for software factories or swarms just yet. If you do want one, be aware that it is a significant commitment of both money and human leadership to keep one running.
Several people told me that I was the only one who stood up onstage, at either conference, and said Build, don't Buy. But my experience is that software factories grow to be highly bespoke to your domain. Mine is super tangled up with my game, and I think that's inevitable. Because the factory is not just building my product, it's supporting it too. It's a company in a box. And they're easy for Claude to build for you.
Third and arguably hottest take: Next year will have a lot of human/agent and agent/agent office drama, resulting from bringing in AI employees, and it will be gloriously funny, but also frustrating.
Many of you are already on this bandwagon, but everyone next year will have a personal chief-of-staff agent. Busy people, even hobbyists, will have whole entourages of helper agents. The hot take is that people will become so dependent on these little private entourages, that they'll bring them to work. Your people will talk to my people, etc. Whole protocols will emerge for private entourages negotiating work between humans, inside companies big and small.
Nearly all humans will wind up having to start working with AI employees next year, and it'll be the beginning of the biggest cultural change we've seen in a hundred years.
So that's the hot takes. Slow down. Only build a factory if you think you really need one. And focus on empowering yourself with your own agentic chief of staff (or team). Your entourage will define how you work with others, so start by perfecting how you work with them yourself.
When a Japanese teenager flies home after a year inside an American family, the program waits twelve months. Then it calls the parents with one question:
"Has your child had any problems readjusting to life in Japan?"
My aunt Tamaki has made that call for twenty-three years.
The parents are supposed to say no.
Almost none of them say no.
There is a little box on her form for the answer. Two lines. In twenty-three years, nobody has stayed inside the box.
Here are a few.
"He wears shorts in February. We live in the mountains. The neighbors think we can't afford pants. In January, one of them left a pair at our door. Folded. With a note. 'For the boy.'" (Mother. Son's year: Minnesota)
"He fixed our toaster. Then the neighbor's bicycle. Then the neighbor's neighbor's sliding door. He is seventeen and he wears a tape measure on his belt. To dinner. On Sundays there's a line outside our apartment. I sent a son to Michigan. They sent back a hardware store." (Father. Son's year: Michigan)
"She still wears the sweatshirt from her high school in Idaho. Every day. When they lose on Friday night, she doesn't speak at breakfast on Saturday. They went two and seven last fall. It was a very quiet autumn." (Father. Daughter's year: Idaho)
"Every time she pays at the register, she asks, 'How are you today?' And then she waits for the answer. That cashier has worked at our supermarket for 22 years. Nobody ever waited. Now she hides the best bananas under the counter for my daughter. Like contraband. Last week the cashier asked my daughter how SHE was. My daughter had to go stand in the rice aisle for a minute." (Mother. Daughter's year: Oregon)
"He stands up every time his grandmother walks into the room. She's 87. Nobody has stood up for her since her wedding. Now she leaves the room and comes back in. Four times during one TV drama. She put on lipstick for the fourth one." (Mother. Son's year: South Carolina)
"Every Saturday she takes a guitar to the old people's home down the street. She knows four chords. Every song she plays is the same four chords. They request songs anyway. There's a man there, 91, who stopped talking to anyone years ago. Now he claps. On the wrong beat. Loudly. The nurses say it's the most he has moved in a year. They have stopped correcting the beat." (Mother. Daughter's year: West Virginia)
"At the airport, he shook my hand. Firm. He looked me in the eye like I was a man he respected. He's sixteen. I told him I needed the bathroom. I stood in there a while. A stranger asked if I was all right. I said, 'My son is home.' He didn't understand. I didn't explain." (Father. Son's year: Wyoming)
And then there's the call Tamaki didn't write down.
There wasn't a box big enough.
Kanna, seventeen, spent her year with the Dorseys, in a farm town in Indiana. Every night at dinner, the Dorseys did something called high-low. Everybody says the best part of their day and the worst part. Nobody is allowed to skip.
The youngest Dorsey's high was always dessert. Mr. Dorsey's low, every single night for eleven months, was the lawn.
On her first night, Kanna tried to skip. They waited. So she said her low was that she missed her mother. Then she couldn't stop crying, at a table full of strangers, over a casserole.
Craig Dorsey passed her the rolls.
"That's a good low, kiddo. Means you've got a good mom."
There was one rule, he told her. Nobody fixes anybody's low. You just say, "Thanks for telling us."
Kanna brought high-low home.
Her family thought it was the strangest thing America had done to her. Her grandmother's high was the weather. Every night. Her little brother's low was having to do high-low. And her father, an office worker, 51, said the same thing every night, in the tone of a man reading out stock prices:
"High: nothing. Low: nothing."
Four months of that.
Then one night in November:
"High: nothing."
He stopped.
"Low."
He put his chopsticks down. He looked at the soy sauce bottle like it might help him.
"I don't have a job."
He had lost it in August. Twenty-eight years at one company, then one meeting. For three months, he had put on his suit every morning at 7:10, picked up his briefcase, said "I'm off," and spent the day on a bench by the river. He came home at 6:30. He even complained about the trains.
In Japan, some men do this. They will sit on a bench for months before they'll say it at the dinner table.
Nobody moved. His wife stopped breathing. His son put his game face-down on the table.
Kanna had no idea what you say to that. So she reached for the only thing she had. The Indiana rule.
"Thanks for telling us, Dad."
Then her grandmother reached over and put her hand on top of his. She's 83. She had not held her son's hand since he was in grade school.
And she said her high.
"Tomorrow you can stay home and watch my programs with me."
Nobody at that table had seen him cry before. Or laugh at dinner. Both happened at once. It made a sound nobody could identify.
He found a new job in February. Smaller company. Less money. Longer train.
That night:
"High: everything."
"And low?"
He thought about it.
"Your grandmother is upset I won't be home for her programs."
When Kanna told the Dorseys, Craig wrote back that his high that night was a man in Japan he has never met.
His low was still the lawn.
"So yes," Kanna's mother told Tamaki. "We have a problem. Dinner takes an hour now. Please send more children to Indiana."
So, America.
The high-low at dinner. Waiting for the cashier's answer. Standing up when Grandma walks in. You think it's small. You think it's corny. Your teenagers roll their eyes so hard you can hear it.
We sent you one of ours for a year. She came back corny.
And a man in Japan got up off a bench.
Stay corny, America. It travels.
I've fixed more friend's dead bedrooms by telling them to get their wife a weighted blanket and roll her up in it and leave her alone with no kids pawing at her for an hour a day than asking their wife what would fix it. The chores are the fixation because the truth is having kids climbing all over you all day causes a gate to slam down between physical touch and romance. Nobody wants to admit that, it sounds childish logically.
Non-autistic women immediately learn what it's like to be autistic sensory wise when it happens. Autistic people often don't know what they need either because there's no way being squeezed fixes that right? But it does. I laughed at that dude saying he sits on his wife to get rid of her stress because it totally works. Deep pressure stimulation causes your neuroticism to let go for awhile and lets your nervous system breathe. She needs a transition state between looking after kids and being your lover again.
I'm about to propose a term for a dangerous failure mode that every software engineer should be thinking about today. And another for its consequences.
Hot-state dependency: A condition in which a system's ability to function depends on organizational relationships, accumulated state, or operational knowledge that exists only in its current running configuration and cannot be reliably reconstructed following interruption.
Yes, I'm thinking about the Microsoft cloud outage that's going on right now. It could be recoverable, still most likely is, but it could also be the harbinger of a new category of systemic disaster.
Heat death: What happens when a system with hot-state dependency crashes and can't be recovered.
The obvious next question is: how do you engineer systems so as not to have any hot-state dependencies?
I don't have a complete answer to this. But I can think of a necessary part of the answer that I don't think we're taking seriously enough: unitary, replayable modification logs analous to version-control change histories.
It should be impossible - it should be an invariant of your system design - to change the state of the system without leaving a sequenced record of the change that can be audited by human and replayed in a future restart sequence.
This doesn't solve the whole problem. In particular, in a cloud-service infrastructure you don't have the option of resetting all your physical wiring changes and hardware deployments to a zero state and then replaying them.
But I guarantee you that in any sufficiently large or complex software system, you will eventually develop a hot-state dependency purely on the software level if you don't have replayable logs. So that's the minimum you have to do. The absolute dead bare minimum.
We haven't known this before because it took some time for our systems to evolve into the complexity regime where heat death is a critical risk.
But we are here, and the time is now. Be appropriately warned.
Nayib Bukele: “There is no State that cannot defeat criminals. If a State does not defeat criminality, it is because the State is complicit.” @nayibbukele
Elsewhere in the world, wonderful things are happening.
@nayibbukele is now in a very strange position, almost a historically unique one. He is simultaneously a democratically elected leader and an absolute dictator. And El Salvador is simultaneously a democracy and a dictatorship.
He is a democratically elected leader, whose administration came to power in a free and fair election. And that administration wields power with the just consent of the people of El Salvador.
But is also dictator, because the consensus in support of him is so overwhelming, his mandate from the people is so total, that he has a completely free hand to set Salvadorean policy as he chooses.
And his choices have done nothing but strengthen that mandate.
Imagine, for a moment, being a Salvadorean right now.
Imagine knowing that, while your nation is not the greatest, richest, or most powerful on Earth, it is led by a man who, should you suffer harm or danger on foreign soil, will gather his men in their thousands, and send them forth with fire and sword to save you, or to avenge what cannot be saved.
Civis Romanus sum. I am a Roman citizen.
This phrase was once a strong guarantee of safety and fair treatment throughout most of the known world. Not because Rome ruled everywhere, but because Rome would avenge its own.
In a stroke, Nayib Bukele has elevated soy ciudadano Salvadoreño to a similar status.
Can you imagine an American president, elected by securing the support of an opaque and fraud-ridden political machine, making the same promise? Can you imagine him making good on it?
Can you imagine a United States senator representing the native American citizens living in the state that sent him to the senate house, instead of Silicon Valley, or Wall Street, or some foreign nation with deep pockets, or a consortium of H1-b slavemasters?
There is a lesson here, and it is a simple one.
The rules matter less than the character of those in office.
A democratic republic which elects corrupt bureaucrats is a nation ruled by liars and thieves. And the dictatorship of a just and unselfish man is a nation ruled by a just and unselfish man.
The only real purpose of a "system" of government is to place power in the hands of wise men of good character.
If the system does not do that, it has no merit, regardless of its form, or philosophy, or reliance on checks and balances.
If you brought Diogenes and his lantern to Washington DC to search by daylight, how many wise men of good character do you think he would find?
Dear Muslims,
As Hanukkah is just 26 days away (and Christmas is only 47 days away),
Please avoid suicide attacks among those who are gathered for ceremonies.
Please avoid detonating in their presence.
Do not deliberately drive vehicles into celebration gatherings, markets, or other holiday cheer.
Jews and Gentiles will be celebrating from dawn until sunset. A little consideration and respect go a long way. ❤️
"We're in the Middle East because of Israel"
vs.
"We're in the Middle East because it's a pivotal region at the crossroads of everything and we're extremely lucky that we have Israel as our aircraft carrier and attack dog"
So why do high-IQ populations stop having babies when they reach a certain tech level?
Precisely because high IQs are so valuable.
When the combination of wealth and technology from high-IQ men reach a certain level, high-IQ labor becomes the bottleneck. At this point, wealthy industrialists, and indeed entire civilizations, face an irresistible temptation.
They can double the size of the labor force, and half the real wages of high-IQ workers while building more, by putting all the women to work.
And since women are instinctively compliant with social norms, all you have to do to accomplish this is convince women that society thinks careers are high-status, and children are low status.
Both radical feminists and reactionaries both noticed some time ago that when you educate women, they stop breeding.
Reactionaries thought this was because women are retarded, and they are genetically programmed to blow up society if you empower them.
Feminists thought this was because having kids is horrible oppression, and women everywhere hate it, and have only ever done it because they forced into it by rape and sexual slavery, so the moment you empower them, they stop.
Amusingly enough, these are actually the same idea, except written with snarl or purr words.
And either way, this idea is wrong. Women don't stop having kids because you educate them. You could send them to finishing school for six years and teach them about matters animal, vegetable, and mineral, along with many cheerful facts about the square of the hypotenuse, and absolutely nothing would change. Except they'd be better conversationalists, and terrific at educating their kids.
No, the reason women stop breeding when you educate them has nothing to do with education at all.
It's because of what you're educating them FOR.
You educate them to put them into the workforce, and once they are in the workforce, you have three things going on.
First, they can build careers or have babies, they can't do both. Two, you just told them kids were for low-class, uneducated, barefoot-and-pregnant loser women living in shacks in rural Kansas. But most importantly, three, when they compete with men in the workplace, and have their own incomes, they lose respect for men.
Women, whether you like it or not, whether I like it or not, only want to have babies with men they consider their superiors.
If they work in the same workplaces as men, they consider those men to be equals, even if his job is "senior multithreaded kernel programmer" and hers is "project schedule kanban board den mother".
So what you've done, what high-tech societies always do, is sacrifice their entire futures for one to three generations of increased shareholder value.
But hey, we know some really great recipes for seedcornbread.
The economically devastated Rust Belt resident asked God, “I had faith in you, but you didn’t save us. You let our town die. Why?”
To this God replied, “I sent you three data-center proposals. What more did you expect?”
If democracy is going to survive, we need to find a way to make it possible to build physical structures again. Because if you let the public have a say, they will say "no" repeatedly until we all live in caves.
update your boxes /now/
the default user on alpine's aws and azure images take any password longer than 256 characters.
yes, any password. yes. i know. yes.
I'm a storyteller.
I will tell you a story.
Not a thinly veiled allegory or analogy. Not a fable. Not a parody or a satire, or some smug little parable featuring characters "Ronald Grump" and "Alan Tusk".
No, this is a true story, and it means what it means, with no hidden symbolism whatsoever. It contains only facts, and general principles to derive from them.
It is a story about Rome.
We all know what Rome was. It was a republic, then an Empire, then nothing.
But every time we ask why, historians wish to tell us it is complicated, and that we desperately need historians, such as themselves, to sort it all out.
The decline and fall of the Roman Empire was not complicated.
The decline and fall of the Roman Empire can be explained in two words.
Cheap labor.
The Romans, as you know, had two classes, the patricians and the plebeians.
The patricians ruled Rome. But the plebeians were Rome. And the patricians forgot this.
Around this point in the story, you may be thinking you understand me already. You may think you have anticipated where I am going with this. You may think that this is going to be some general polemic about the importance of remembering the little people.
It is not. I have a very specific meaning, and I always choose my words very, very carefully.
Two words.
Cheap. Labor.
The Romans patricians, like the old and the rich of any society, owned land, and sold goods. To do this, they bought labor.
The Roman plebeians, most especially the young, sold labor. So that they could buy goods and land.
So, it should go without saying, but often doesn't, that it was in the interest of plebeians that goods and land be cheap, and labor be expensive, and in the interest of patricians that land and goods should be expensive, and labor should be cheap.
Now, markets have natural cycles. The price of every thing fluctuates up and down, looking for an equilibrium which is only ever temporary.
Sometimes goods and land are cheap, and labor is expensive. Then the plebeians become fat and prosperous, and they marry pretty girls and have lots of healthy children.
Sometimes goods and land are expensive, and labor is cheap, and patricians amass vast fortunes and build fine estates and eat honeyed dormice.
To every thing, there is a season.
But the patricians controlled Rome. Not fully or directly, not in theory, but they had money. And money buys power. Just as power buys money.
And the temptation, in the long run, became irresistible. To buy political power, and put the finger of that political power on the scales of the market.
To make sure the cheap labor stays cheap forever.
In Rome, cheap labor meant slaves. Elsewhere, it has meant other things.
In Rome, slaves kept labor cheap not only because slaves don't get paid, and can't quit, but also because every plebeian who sells labor must compete with the slave on price.
Little by little, this took away from the plebeians, not only because real wages were depressed, but more importantly because there were no seasons of labor scarcity. No cycles in the market where wages went high.
No fat seasons for the plebes, just an ever-increasing drought.
And, while the patricians controlled Rome, the plebeians were Rome. It was their blood, shed in the legions, that conquered the world. Their sweat that built the shining city of seven hills.
And their patriotism that defined what Rome was.
The patricians ruled Rome. But the plebeians were Rome, and when they ceased to bear allegiance to Rome, Rome ceased to exist, because the only thing that Rome ever was, the only thing that any city or nation ever is, is its people.
A man who has no work, a man who must compete with slaves, a man who is beaten down to want the hungriest beggar will take, is a man who cannot have a home and a family.
Not only because he cannot afford such things. But because no woman will have him. No woman will bear his children.
The ultimate expression, after all, of female lust and admiration, is "I want to have his babies".
Fewer people seem to realize that the reverse is true.
I was told once, by a man who should have known better, that Rome fell because the Romans forgot what it meant to be Roman.
Nonsense.
Rome fell because Romans knew exactly what it meant to be Roman. Which meant they knew that to be Roman meant to be replaced by slaves.
The patricians bore no allegiance to Rome, because it was cheaper to replace the Roman workers with slaves, and the Roman legions with mercenaries.
The plebeians bore no allegiance to Rome, because Rome bore no allegiance to them.
And so Rome simply ceased to be.
The outward forms hung around awhile, until the mercenaries, bearing no true allegiance to Rome, realized they didn't have to wait to be paid. They could just... take.
The patricians destroyed Rome because they thought like politicians instead of kings.
A politician buys a crown by offering the most to those whose support is most in doubt.
A king knows that crowns and thrones are only symbols, and power comes from armies of loyal men, whose loyalty must be bought with loyalty in turn. Not table scraps.
The Roman plebeians didn't want, and couldn't survive on, free bread and circuses. They needed work and land and incomes to have families and happy lives.
But no Caesar emerged in time.
Tick tock, Mr. Vance.
Tick tock.