←
Andrew Rose24,372 posts
Andrew Rose avatar

Andrew Rose

@__drewface

Happy husband and father. Trying to make the world a teeny bit better each day with my family and friends. Teaching people to love the new era of computing.

◷ Joined September 2013▧ 1,328 Photos and videos
Andrew Rose avatar
Andrew Rose@__drewface·Jun 9

I haven't tweeted much about it, but I am running a part-time, 6 week program this summer at Fractal to help professionals master AI agents. It's based on everything I learned from training ~100 engineers over the last 2 years. Check to see if your employer will pay for it :)

Post attachmentPost attachmentPost attachment
Andrew Rose avatar
Andrew Rose@__drewface·1h

wow @visakanv did you know this story about how Sonic the Hedgehog's creator "just put Felix the Cat on the body of Mickey mouse"? Truly everything is a remix.

Post attachment
Andrew Rose avatar
Andrew Rose@__drewface·2h

It's a mix of people I'm completely unsurprised by and a bunch of people I don't even follow

Andrew Rose avatar
Andrew Rose@__drewface·Nov 16

If you would like to unashamedly have your full AI usage by an open invitation to your friends and colleagues to geek out with you about the future of work, join our upcoming fractal accelerator

in hindsight it's incredibly obvious that most-all AI usage is going to be a shameful half-secret

Andrew Rose avatar
Andrew Rose@__drewface·Nov 16

Rich said we should talk about the state of the network again, after privately talking about the state of the network. I'd love to do that/listen, maybe in a series of 3-4 person recorded podcasts?

many quotes from this conversation still ringing in my mind. recommend watching this is you wanna think about the state of the network

Andrew Rose avatar
Andrew Rose@__drewface·Nov 16

Prompt engineering is back baby

code for review : github.com/ChetasLua/moss-ke… Prompt : Create a 2D anime scene for the web. It must look completely like real Japanese anime, as if it were taken directly from a finished theatrical anime film. This is traditional-looking, hand-drawn 2D anime, not a 3D animation, a moving illustration, or a stylized web graphic. Deliver the final result as a single, self-contained HTML file. Use any tools, libraries, references, guides, literally anything etc. Use Studio Ghibli films as the art style reference for the design, line work, painted backgrounds, color, and atmosphere. Create an original giant robot as the main character. No people appear in the scene. Use any tools or techniques you want, including 3D, as long as the final result looks 100% like hand-drawn 2D anime. SCENE At sunrise, mist hangs over an abandoned forest. A giant robot has knelt here for so long that moss, wildflowers, and old trees have grown over its body. A small bird lands on its shoulder as the first ray of sunlight reaches its weathered face. Deep inside its chest, a faint light flickers on. The ground trembles and birds burst from the treetops. With a deep, creaking groan, the robot slowly rises as soil, vines, and leaves pour from its armor. It lifts its head toward a gap in the canopy. The engines ignite, sending a great ring of wind across the forest. The robot tears into the golden sky, leaving a curving trail of light and mist as leaves spiral down through the sunbeams. ANIME QUALITY STANDARD Every frame must look as if it was drawn by professional anime animators and painted by master background artists for a finished theatrical film. Robot: A hand-drawn anime mecha that feels heavy, ancient, and full of personality, with cel-colored forms, chipped paint, rust, moss, and believable weathering. Keep it on-model from every angle, and let its posture and glowing eyes express emotion. Line art: Confident, delicate, hand-inked anime line work with subtle variation in thickness and pressure. Coloring: Traditional anime cel coloring with clean color areas, simple hard-edged shadows, and a soft, natural palette. Backgrounds: Richly detailed, hand-painted anime backgrounds in a gouache style, with visible brushwork, natural color variation, layered foliage, and real depth. Lighting: Golden sunrise light, colorful shadows, glowing mist, and soft atmosphere that unite the robot and background. Animation: Authentic hand-drawn anime timing with real weight, strong key poses, natural holds, and overlapping movement in vines, grass, leaves, birds, and falling debris. The robot should rise slowly and feel massive, then launch with explosive power. Direction: Cinematic anime shots, beautiful composition, thoughtful staging, and pacing that starts quietly, builds tension, and ends in a soaring climax. IT MUST NOT LOOK LIKE - 3D: No plastic materials, CGI shading, visible polygons, game-engine lighting, or computer-perfect perspective. - SVG or vector art: No simple geometric shapes, perfect curves, uniform outlines, flat corporate illustration, or basic gradients. - Web animation: No sliding layers, constant bobbing, floating parts, smooth software easing, or puppet-like joint rotation. You are free to change any part of the prompt, if it would result, in better results. - AI art: No warped shapes, melted details, flickering, or changing robot designs. - Non-anime art: No Western cartoon designs, realistic rendering, soft painterly shading on the robot, or generic digital illustration. - Amateur work: No stiff poses, empty backgrounds, repeated trees, muddy colors, clip art, placeholders, or unfinished details. The result should feel awe-inspiring, nostalgic, and full of wonder, like the moment an old forgotten dream comes back to life. Before finishing, inspect random frames as still images. If any frame does not look completely like real 2D anime, keep improving it. Do not stop until every frame could pass as a still from a theatrical anime film.

Post attachmentPost attachment
Tekon Burns avatar
⟳ Andrew Rose retweeted
Tekon Burns@TekonBurns·Nov 13

🚨Claude code users!! Your 5-hour and weekly limits will stretch much further. Anthropic published a new official documentation page for experimental Code Mode in Claude Code v2.1.323+. Instead of sequential tool calls, Claude writes JavaScript to run parallel tool calls in one step. code.claude.com/docs/en/code…

Andrew Rose avatar
Andrew Rose@__drewface·Nov 15

Btw using reference images is a powerful technique for building creative worlds

Fable 5.2 been cooking up something 👀, it made this in 30 mins, gonna polish this and make into a full fledged game, stay tuned 😈 All it took was just one reference image!

Post attachment
0:24
Andrew Rose avatar
Andrew Rose@__drewface·Nov 15

Tldr; slow down, focus on doing great work at whatever speed you can, you probably don't need a software factory. As you unbottleneck yourself, a software factory might emerge if you are doing a good job.

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.

Andrew Rose avatar
Andrew Rose@__drewface·Nov 15

"companies use surge pricing to maximize consumer welfare" is just not strictly true. Companies are mostly maximizing their own surplus. What is true is that surge pricing creates a strong incentive for more supply to come online in a market to meet demand, which can be great!

Andrew Rose avatar
Andrew Rose@__drewface·Nov 13

cool

Introducing Claude Meetings: add Claude to your team’s video call and it builds docs, whiteboards, and other artifacts with you while you’re still talking. Starting to roll out in beta on Team and Enterprise plans.

1:03
Jakeup avatar
⟳ Andrew Rose retweeted
Jakeup@myhandle·Nov 11

I want good video game studios to use 100x as much AI as they're using now. I want them to crunch less and experiment more, to create new great things and leave the remakes, remasters, and rehashes to novices with LLMs. I'm utterly baffled why 90% of gamers are against this.

Zyan🔸 avatar
⟳ Andrew Rose retweeted
Zyan🔸@zyansheep·Nov 11

working on linear interaction net stuff, still allegedly reflective but decided to drop the tree calculus (since binder encoding has a lot of overhead👀) in this language erasing and copying are explicit agents that have to be designed in and if you don't use them everything should *in theory* be reversible. my intuition is that once I implement this on a cellular automata, there should hopefully be obvious further simplifications able to be made around turning certain kinds of agent-agent reductions into just like strait adiabatic reversible logic circuit-type thingies, and anything irreversible changes the logic gate/cell configuration itself. aaaaaaahhh i'm so excited!!! :3 JustWrite Nov 10

0:22
Andrew Rose avatar
Andrew Rose@__drewface·Nov 11

GiveWell is so cool

Couple thoughts: 1) After several people pointed out that Lyman couldn't substitute all-cause mortality for malaria-specific mortality like he had done, he fixed it. His initial estimate for $/lives saved was $19000; revised it’s about $8,200. 2) I think, though I could be wrong about this, that his calculation to get $8200 still has a problem: he calculates the costs of the distribution based on the whole population but the benefits based on 75% of the population (since he argues the other 25% is already sleeping under nets). But as he himself identifies, the nice thing about an intention-to-treat analysis is that you don't need to do this and shouldn't: you just ask how much to expect mortality to fall in a village after handing out the nets, and the answer is 17%. (You only care about the fact some people are already sleeping under nets if that makes your village unlike the one where the 17% was measured; more on that below.) If he changed this one factor this would make his numbers quite close to GiveWell's. 3) He then applies an adjustment for the long-term: "If bednets reduced short-run all-cause mortality by 18% in the 1990s and maybe reduce it by (who knows?) 14% today, they probably reduce actual child mortality (i.e. across 5 years of early childhood) by 7-11%." But GiveWell actually accounts for that even more stringently by just excluding all benefits past the first two years, one of several places where they are intentionally conservative. 4) He accuses GiveWell of misrepresenting Cochrane's statistics but they actually just report a bunch of different numbers and I think he mixed them up. He complains "GiveWell cites that review to support a “45% reduction in malaria incidence.” That’s an error, that review did not find a 45% reduction in malaria incidence." But the review absolutely does report almost exactly that: "Insecticide-treated nets also reduce the incidence of uncomplicated episodes of Plasmodium falciparum malaria by almost a half (rate ratio 0.55, 95% CI 0.48 to 0.64; 5 trials, 35,551 participants, high-certainty evidence". Rate ratio 0.55 means a 45% reduction. 5) He expresses concern that a lot of the Cochrane studies are old and describe a different environment (Africa in the late 1990s/early 2000s). However, GiveWell's most recent grant to nets in the DRC - which I believe that my donations helped to fund - is based on data from a 2023-2024 large scale demographic survey in the DRC, so the nets are being distributed in an environment very close to the one studied. It found about a 14% all-cause mortality reduction in the first year after a distribution, close to the 17% in Cochrane. He also expresses concern that Cochrane's mortality estimate here is low-powered but I don't think it is (the analysis says "rate ratio 0.83, 95% CI 0.77 to 0.89; 5 trials, 200,833 participants, high-certainty evidence") so it's between 11% and 23% with a 95% CI! 6) He also raises questions about whether there are more people trying to hand out nets than nets to be handed out. GiveWell looked into that and determined that in the DRC, there was not enough funding to do all the distributions that were indicated, in part because the Global Fund caps how much it'll spend in any one country. 7) Finally, he argues we should instead - from an altruistic perspective - spend our money however maximizes GDP. But I think there's a serious case that health interventions like combatting malaria are necessary for GDP growth to take off in DRC, just like the American South was kind of a backwater until we eradicated malaria there. Being constantly sick is horrible for productivity. Being only able to hire employees who are constantly sick is horrible for a business environment. GiveWell estimates that a $1,000,000 donation increases adult income for 80,000 children by 0.6%, which means that much of their modelled benefit of malaria nets *is* their GDP effects. My best guess is that if you were a hard-nosed GDP maxxer you'd invest a lot in reducing the disease burden in poor countries. Or maybe you'd go all in on making AI happen as fast as possible, something I rarely see EAs criticized for failing to do. I would probably donate more money to making AI go well if I had more of an idea of how to do that and it wouldn't create a bunch of conflicts of interest with my reporting work. I agree it would be cool if there were an organization focused on effective institutional capacity building in poor countries, but the reason I and man others don't donate to this is not that everyone fails to realize how important institutions are, it's that even though many people have worked very hard on the problem for a long time they do not have a way better than the nets to turn my money into GDP growth in poor countries. There was a bit of a Our World In Data article I read this fall that has stuck with me: "I’ve never had malaria, but I know several people who have. They describe it as one of the worst experiences of their life. What starts out feeling like the flu — which is bad enough — can quickly progress into something far worse. The body swings from intense fever and sweats to chills deep enough to make you shake uncontrollably. Everything aches, from your muscles and joints to the pounding headache that makes it impossible to think clearly. Your body is so fatigued that it’s a battle to make it to the bathroom when the nausea and vomiting arrive. That’s what a pretty standard infection feels like. For some, it goes much further. Here is how one account describes it: “I awoke to what felt like lightning going through my legs, and then spreading through my body and in my head. Probably the worst headache, body aches, and chills you could possibly imagine. It felt like I was being stung repeatedly by an electric shock gun and could barely control my movements. The pain was so intense; I actually believed I was dying, literally crying out in pain so bad that I was taken to a 24-hour clinic that night at 3am.” In Senegal, the median child experienced 43 attacks of malaria over the course of their childhood. My hard-nosed productivity obsessed persona says "I bet that's rough on their human capital development, and it's quite cheap to prevent." But mostly I don't, actually, say that to myself. I just buy some nets. If something even better comes along I'll do that, but I haven't seen it yet.