We take AI from research papers to industrial plants. Computer vision, agents, speech, generative AI. Bangalore | Stuttgart | Abu Dhabi.

Joined May 2025
I think people are underestimating just how much industrial knowledge Germany is sitting on, and how easily it could lose its competitive advantage over the next decade. Germany has spent generations building some of the most sophisticated industrial companies in the world. Many are family-owned Mittelstand businesses, operating in obscure niches, making products that most people have never heard of, but which entire global supply chains depend on. Their competitive advantage was built over decades. It lives in the accumulated experience of their engineers, the intricacies of their manufacturing processes, and an intimate understanding of problems that competitors may not even know exist. And yet, these companies face an increasingly uncomfortable future. Energy is expensive, regulation is burdensome, skilled workers are difficult to find, and competition from China is intensifying. Meanwhile, technological change threatens to erode advantages that took generations to build. I find it troubling how casually we discuss Germany's industrial decline, as though we are talking about abstract economic statistics rather than businesses that families have spent their lives building. But I also believe AI offers these companies an extraordinary opportunity. Consider the sheer quantity of knowledge accumulated inside a fifty-year-old manufacturing business. Engineering drawings, maintenance records, production data, and decades of experience troubleshooting problems on the factory floor. Much of this knowledge remains fragmented, difficult to access, and dependent on a handful of experienced engineers. Imagine making that accumulated expertise accessible across the organization, allowing engineers to understand complex dependencies and make better decisions in a fraction of the time. This is precisely the kind of problem we're working on at @FastCodeAI. Germany's greatest industrial strength is its accumulated engineering knowledge. Air-gapped secure customized AI offers an opportunity to make that knowledge considerably more valuable. And I believe preserving this advantage should be a national priority.
3
3
3
37
3,497
Fast Code AI retweeted
this is an interesting take, are ai agents going rogue BECAUSE they are too obedient?
1
1
393
Sound on. 🔊 Beep. Hum. Pour. Flip. Click. Clack. Strum. A day at @FastCodeAI, in 35 seconds.
2
1
13
575
Fast Code AI retweeted
Maybe the problem with AI agents is that they are way too obedient and should actually be afforded more "intellectual" freedom.
1
3
135
Fast Code AI retweeted
Today, it is expected that most successful people should have a modicum of financial literacy. We may be heading towards a world where AI literacy is expected too, if not at the depth of Ben Affleck, then at least at the level of understanding the basic machinery. Most people do not need to train neural networks or write Python. Financial literacy does not require you to price derivatives either. It requires enough understanding to follow what is happening, ask sensible questions, and recognize when someone is talking nonsense. AI is moving in that direction. A lawyer will increasingly benefit from knowing how language models arrive at answers, where they are likely to fail, and what happens to sensitive information passed through them. A filmmaker may need to understand generative video, segmentation, compositing, and the limits of synthetic footage. A CEO should probably know what inference costs, why proprietary data matters, and why a model that sounds extremely confident may still be wrong. What makes the Ben Affleck clip striking is how naturally this knowledge seems to have entered his working life. He ran a visual-effects company, worked with GPUs, encountered convolutional neural networks through VFX, and eventually found himself curious enough to call Google and OpenAI to see what they were building. That trajectory is going to become increasingly common. As AI works its way into law, finance, medicine, engineering, media, education, and management, some knowledge of how these systems behave will become part of being competent in the field. A decade from now, “I’m not technical” may sound increasingly dated. You will not need to understand every layer of the stack, but if AI is shaping decisions inside your profession, understanding its basic logic will probably become part of understanding your profession itself.
Fireside Alpha
@firesidealphaOct 6
Ben Affleck reveals he writes Python, understands convolutional neural networks, worked extensively with GPUs, and used his celebrity status to get private looks at Google and OpenAI’s video models “I’ve always been kind of into computers since I was young. Then, when film started to move from analog film to digital, I became more interested in that aspect of it. The visual-effects workflow for many years has included machine learning, so I can write pretty shitty Python scripts and stuff like that. “With convolutional neural networks, which were the precursors to what the transformer can do, which is much more computation simultaneously, you would do things like look at what’s called a tensor. That’s the numerical translation of a visual image in numbers, like the batch number, the frame number and the red, green and blue values of each pixel in each frame. It’s just that simple. That numeric is called a tensor. “You’d use a convolutional neural network to identify patterns that reveal what’s called edge detection or feature extraction, which is identifying patterns well enough to know, this is where the window ledge is, so we can more easily take the green-screen image out and replace it with something. “That was familiar to me early on because, prior to Artists Equity, I had a small visual-effects company. I’ve worked with GPUs a lot too. The visual-effects guys said, ‘Hey, you should see. There are a couple: Google and this other company, OpenAI, are doing really interesting stuff with transformers in video.’ “I’ve learned that I can actually just call up and go, ‘Hey, it’s Ben Affleck. Can I come see what you’re doing?’ Sometimes people say yes, to my astonishment.”
1
3
8
516
A self-driving car can make the right decision for the wrong reason. For an LLM, that can be annoying. For a self-driving car, where the decision can literally be a matter of life and death, being consistently causally wrong is really fucking dangerous. So we built a benchmark to test whether autonomous driving models actually understand why they should act, not just whether they produce the right action. That work has now been accepted at NeurIPS. Here is a brief explainer:
1
2
8
680
We were genuinely surprised by the amount of pushback, and in some cases outright hostility, to our announcement of Research as a Service. A few people seemed to read it as some new scheme for companies to buy papers or rent academic credibility. That is not what we are doing, and the underlying model is much less exotic than the reaction suggests. I spent years in academic research, first at Max Planck and later at NYU. Research has never happened exclusively inside universities. Companies commission research, universities take on industry-funded projects, pharmaceutical companies work with CROs, and specialist labs are brought in when an internal team does not have the expertise or bandwidth for a particular problem. This has been normal for decades. We are doing the same thing for machine learning. There are companies with difficult ML problems, unusual datasets, and potentially novel technical questions that do not justify hiring an entire research group. Building such a group can take a year. A focused research project might take four months. So they bring us the problem and the data, and our researchers work on it. We design the experiments, build the methods, run the evaluations, iterate when things fail, and try to produce research that is good enough to survive peer review. If that work leads to a paper, authorship follows contribution, as it should. The conference reviewers still decide whether the paper deserves to be published. Paying FastCode funds the months of research required to get to that point; it does not purchase the outcome. I suspect some of the reaction came from the phrase “Research as a Service.” Fair enough. New packaging can make an old practice sound stranger than it is. We published a longer explanation from the @FastCodeAI account because I think the model deserves to be understood before it is dismissed.
6
3
1
31
2,627
Fast Code AI retweeted
Bo French is right. Indians are indeed are taking over the US of A and in fact our team has landed in SF to do just that! Just kidding! For now, we just want to take over your process plants and factories. @SanjaySuriya6 is in SF to talk about Legend™, Fast Code AI’s Engineering Intelligence system. Engineering drawings contain far more than symbols, tags and lines. They describe how equipment connects, how systems behave, where dependencies exist and how an operation was designed to work. Most of that knowledge is still locked inside drawings that were created for engineers to read, not machines. Legend turns those drawings into connected, machine-readable engineering context. Don't worry, though, @SanjaySuriya6 will come right back to India after a few meetings. But time is short, and you might you want to grab a coffee with him if you care about engineering/physical AI/ computer vision!
Replying to @SanjaySuriya6
@SanjaySuriya6 was a physics student who wanted to get into ML. He went through every professor at IISc working on deep learning and wrote to all of them. @Arjunjain was one. The video tells you how that went. He's now a partner at FastCode AI, a research scientist who also runs our forward-deployed engineering, the team that stays with a client until the model works in production. He's in San Francisco with Naren and @siddesh_239. It's the same cold email, just on camera. P.S. - Sent from the FastCode AI account or he'd have undersold himself.
3
8
6,130
Fast Code AI retweeted
A legend for the physical world. Sounds cool! @Arjunjain is a friend I got to know during my last visit to Bangalore. We connected because we both did our PhDs from the Max Planck Institutes in Germany and have the shared belief that academics have a moral imperative to venture outside the confines of academia and build something real for the world. Glad to see his company @FastCodeAI building at the frontier of AI X Engineering. This seems like a great product to have come out of their lab: it turns industrial plants and factories into a living, breathing intelligent digital entity powered by custom AI models, completely air gapped. If you are a German mittelstand or own operate factories/machineries, @Arjunjain is the man to talk to. Disclaimer: I have a soft spot for Indian founders expanding into Germany/Europe. 🇩🇪🇮🇳
Last month, one of our customers nearly shut down a plant. For a large process plant, even a single day of unplanned downtime can easily run into a few million dollars. Yes, you read that right, for one single day. The problem was not some exotic failure. The information the engineers needed already existed, but it was buried across engineering drawings that had to be read, traced, and reconciled manually. Work that would normally take three days was completed in roughly three hours. That incident captures why we built Legend. Legend is our framework for turning engineering drawings into one machine-readable model of an industrial operation. Once the drawings are understood as a connected system rather than a pile of files, teams can start asking much more useful questions across the plant. How many pumps of a certain type are installed? Which equipment needs to be isolated before maintenance? What is connected upstream or downstream of a component? Which parts of the plant are affected if something changes? No engineer can realistically hold thousands of drawings and all of their relationships in their head at once. Software can. That is the larger idea behind Legend. We do not want engineering drawings to remain static documents that become useful only when somebody manually opens them and starts tracing lines. We want them to become part of the operational intelligence of the plant. Legend is already deployed across 40 industrial sites, including oil and gas facilities, and we are now extending the same approach into hydraulics, pneumatics, electrical systems, and automation. And because industrial data is often among the most sensitive data a company owns, Legend can run on-premise and air-gapped, on infrastructure controlled by the customer. Every drawing has a legend. We just built one for the physical world.
2
7
969
5'7 is the ideal founder height. There are a suspicious number of extremely successful founder-CEOs hovering around this height. Mark Zuckerberg is 5'7. Jeff Bezos is about 5'7. Jensen Huang is reportedly around 5'7. Jack Ma is even shorter. There is an interesting reason this might happen, and it has less to do with founders themselves than with the unusual way in which someone becomes a founder-CEO. Nobody hires a founder to be CEO. Zuckerberg never had to persuade a board at Facebook that he possessed sufficient executive presence. Bezos did not have to look commanding enough to be selected to run Amazon. Jensen Huang did not spend twenty years moving through Nvidia's management hierarchy until a succession committee finally decided that he looked and sounded sufficiently like a chief executive. They started the companies, and at some point the companies became enormous while they were still running them. That is a very unusual selection mechanism. A professional CEO, by comparison, has usually spent decades being selected by other people. Think of Tim Cook at Apple, Satya Nadella at Microsoft, Sundar Pichai at Google, Dara Khosrowshahi at Uber or Bob Iger at Disney. Before reaching the top, they have usually survived countless promotions, interviews, presentations, executive meetings and succession decisions, all involving people who already have a fairly well-developed idea of what a senior executive should look and sound like. Competence obviously matters in this process, probably more than anything else. But competence is never evaluated in isolation. Height, voice, appearance, confidence, social fluency, posture and the countless small signals that together produce what is rather vaguely called "executive presence" all enter into the judgment. If someone has to pass through twenty years of other people deciding whether they seem ready for the next level, those signals have twenty years to matter. Founders largely escape this filter. Their selection process is different and, in some ways, harsher: something has to be built that actually works. The market does not particularly care whether someone looks like a CEO if they own the company.
Jensen masterfully handles the potential Benioff frame-mog: “Look, I'm very good friends with both of you guys…I always feel like I need to stand on a chair…I just wanna let you guys know that when I'm on an airplane, I'm a lot more comfortable than you guys. And so, through human evolution, they realized that big is unnecessary. There's about a million years of evolution between you and me."
2
1
2
17
4,122
Fast Code AI retweeted
This article makes an important point: human intelligence and artificial intelligence seem to be different. A math genius has (typically) basic common sense. AI intelligence seems to be unusually spiky. It can solve frontier math problems but often can’t understand simple instructions. Hard to kill all of humanity while being retarded but gifted .
1
7
697
Fast Code AI retweeted
We are a humble AI lab building models that can actually read engineering drawings, starting with Piping and Instrumentation Diagrams (P&IDs). The reason we exist is because frontier AI, even with its Nobel-Laureate level intelligence, can't parse standard engineering diagrams. Before AI decides to go on this killing spree and take over the world, we would humbly request that it first learn to trace a pipe through a slightly blurry P&ID without hallucinating a valve. Until then, we remain cautiously optimistic about humanity’s chances.
Jacob Coxon
@hilbertspaessSep 9
Replying to @hilbertspaess
The people building AI earnestly believe that it could kill us all by the end of the decade. This is not a marketing stunt. If anything, many executives and senior researchers will couch their phrasing in the press to sound sensible - but I hear the same people express fear privately. No other human activity poses this level of danger.
3
5
1,377
It is 2001. I arrive at my JEE Mains centre in a Home Minister's car. "Lal batti" flashing. An armed guard riding along, if I remember right. My classmate Kuber's father was the home minister of Madhya Pradesh. I have stayed the night at their Bhopal bungalow, and his mother cooked dinner for me herself. That is the kind of school Daly College is. My friends' fathers run states. I am the kid whose aunt paid the school fees. The car waits outside through the whole exam. But the paper does not care who drops you off. Inside the hall, I already know it has gone badly. I can attempt only a few questions. I had bet two years on that exam - quit hockey, quit the quizzes and debates, studied while all my friends played. I placed the bet myself, and I lost it. The backup plan was a year in Kota. My father did not have the money for Kota. So: RV College, Bangalore. Cauvery Block, 1st Floor. Nothing about my situation said "researcher." No brand name, no coaching, no one watching. I pulled IEEE Transactions off the library shelf anyway, because the desire was mine and I stopped waiting for someone to authorize it. A year in, I gave the JEE one more shot from my hostel room. Second attempt: 3363. Petrochemical at IIT-BHU. An IIT seat, at last - and I turned it down. I already had one paid-for year of computer science, and just three years left before I could start earning. Starting over meant four more years of fees, in a branch I did not want. Fourteen years later, IIT Bombay calls. Not with a rank. With an offer to teach. In 2016 I walk into CS763, Computer Vision, as the professor. Every student in that room cleared the exam I could not. It never once comes up. The exam's authority, it turns out, expires. I teach there four years. Graduate 2 PhD students. One of them, Rishabh, is a professor today at Max Planck - the institute where I did my own PhD. The credit is his. At most I held a door open. But the symmetry stuns me: my student teaches where I trained, and I taught where I could not study. So if an exam has just told you who you are - if you are stuck, and you know you are capable - hear me: it is not the end. The exam decided where I started. It had no authority over where I ended. Neither does yours. Do not wait for permission. Work like the desire is already authorized, because it is. It will work out - not on their schedule. On yours. So tell me in the comments: the exam that said no to you, and the person you became anyway. Someone sitting tonight where I sat needs to read your comment more than my post. 𝗚𝗼 𝘁𝗮𝗸𝗲 𝘄𝗵𝗮𝘁 𝗶𝘀 𝘆𝗼𝘂𝗿𝘀.
43
112
12
742
66,714
Fast Code AI retweeted
We are a computer vision team. Pose estimation, diffusion models, papers at CVPR with our names on them. So when we first looked at engineering drawings, we thought we had been handed the easiest input in the field. No lighting. No occlusion. No motion blur. Black strokes on white paper, drawn to ISA-5.1, by people who were trying very hard to be unambiguous. Child's play, right? Models are good at photographs because somebody labelled 14 million of them. Nobody has done that for engineering drawings. The largest public P&ID dataset is 500 synthetic sheets, tested on 12 real ones. Not enough to train on, and not enough to tell you whether you are right. So the model learns all of it from almost nothing. A gate valve, a globe valve and a ball valve are the same bow tie. The difference is what sits in the middle: nothing, a filled circle, an open one. Read it wrong and you have told the plant that a throttling valve is an isolation valve. Text printed over a line is not part of the line. A circuit leaving the right edge picks up three sheets later. And the one that cost us the most time: a tag sitting between a valve and a transmitter, belonging to exactly one of them, with nothing in the image to say which. Models that read the world do not read the page. 8,362 drawings and three and a half years in, somebody still walks over with a sheet where a line was drawn in by hand during a turnaround, and asks whether the model should trust it. There is nowhere to look it up. So we go and ask. Last month that was Parth Tulsyan and Vijay, sitting with the process engineers who read these drawings every day. What they brought back went into the model. Nobody publishes that dataset. We build it, one conversation at a time.
2
1
5
2,712