Pari Singh

244 posts

Pari Singh banner
Pari Singh

Pari Singh

@paritheengineer

Founder & CEO of @buildonfloweng Re-inventing how humanity develops its most important machines (Space, Aero, Nuclear, Robotics)

San Francisco 加入时间 Nisan 2009
581 关注2.6K 粉丝
置顶推文
Pari Singh
Pari Singh@paritheengineer·
We’re thrilled to announce our $23M Series A led by @Sequoia - joined by @patrickc, @collision, and @david_helgason. Honored to welcome @roelofbotha to our board. We’ve entered a new era of manufacturing. Reusable rockets. Humanoid robots. Self-driving cars. Humanity is reinventing how it builds. We started by building hybrid rocket engines. Along the way, we built tools that made us move faster - design, build, test, iterate. Those tools became @buildonfloweng. Today, Flow has become the default platform for next-gen hardware teams, powering the systems that will define our future.
English
118
105
1.9K
555.5K
Pari Singh
Pari Singh@paritheengineer·
NASA invented Systems Engineering -> SpaceX/SkunkWorks perfected it. Kelly Johnson wrote 14 rules, here are the 5 that matter most today: 1. Keep teams brutally small: "Restrict the number of people in an almost vicious manner. Use 10 to 25% compared to normal systems." More people doesn't mean faster. It means more coordination overhead and slower decisions. 2. Make changes easy + fast: "A very simple drawing and release system with great flexibility for making changes must be provided." Your change management system is either an enabler of speed or your biggest bottleneck. This is still the biggest slowdown in most programs today. 3. Record the important work. Skip the rest. "Minimum reports required, but important work must be recorded thoroughly." Not zero documentation. Not a thousand pages nobody reads. The right information, captured where it matters. 4. Test early and often. "The contractor must be delegated authority to test his final product in flight. He can and must test it in the initial stages." Test early. Don't spend three years in analysis before finding out your design doesn't work. Kelly was practicing iterative engineering 40 years before anyone called it agile. 5. Build daily trust across companies. "Mutual trust between the project organization and contractor, with close cooperation on a day to day basis. This cuts misunderstanding to an absolute minimum." Not quarterly reviews. Not 200 page status reports. Daily collaboration with shared context.
Pari Singh tweet media
English
0
0
3
142
Pari Singh
Pari Singh@paritheengineer·
We are vastly underestimating how big of a change AI agents will have on Physical Engineering. Humanity spends this much on people/yr: 2T - Software Engineering [Cursor, Claude code] 3.5T - Physical Engineering [Flow Engineering] Physical Engineering - 82% of Global Engineering can be automated with only 4% actual coverage today. I am a firm believer that: 1. 100% of engineering work will be done by agents. 2. Humans will be more important - as managers of an army of AI agents. We're not going to build the same products with fewer people - we're going to accelerate timelines and build much more ambitious things. It's pretty clear that by the end of 2026, all software code in Silicon Valley will be AI generated. I think my mid-2027, the same will be true for all Physical Engineering (hardware) development. The world will follow what Silicon Valley // El-Segundo (silicon valley for hardware).
Pari Singh tweet media
English
0
0
4
276
Pari Singh 已转推
Joe
Joe@JoeAverbukh·
Tier 1 VC rankings based on ~600 votes over the weekend
Joe tweet media
English
24
11
500
118K
Pari Singh
Pari Singh@paritheengineer·
@nectarios Yes I’ll do everything in my power 😂
English
1
0
1
7
Pari Singh
Pari Singh@paritheengineer·
Rivian x Flow Engineering announces Strategic Partnership Rivian’s needs & usage is insane: ∙1,000+ users ∙1M+ requirements (software + hardware) ∙95K API calls per night Rivian started with 40 users and grew to 1,000+ in just 4 months. When I first met the Rivian team, I was blown away by the scale of what they were building. Their vision for Systems Engineering represents what the entire industry has been chasing for decades. This partnership means everything to us. Flow is now the system of record for the R1 and R2 — but more than that, we’re partnering on the future of how systems engineering will be done for decades to come. A huge thank you to the engineers who took a bet on us early. Thank you Scott MacKenzie, Ahmad Sidawi, James Fullana , Kevin Sallee , Matt Aziz and too many others to count. You took a company level bet on us, we will not let you down
Pari Singh tweet media
English
1
0
24
2.1K
Pari Singh
Pari Singh@paritheengineer·
NASA's Administrator Jared Isaacman has confirmed - Nuclear thermal rockets are coming. Holy cow. 🚀 This is not something I thought I would see in my lifetime. For those out of the loop - this is a real technology that was tested in the 60's which is the successor to chemical propulsion. This is something *only* NASA can do given the risks/public perception problem. If NASA can deliver this, safely, this could be as big as re-usable rockets. NASA has always been best doing things that are too audacious for industry. Safety is going to be everything - and there are ways to pull this off. Hot damn it's getting exciting again.
English
0
1
10
798
Pari Singh
Pari Singh@paritheengineer·
@faunarobotics Weirdly bullish on this as a cute MVP that passes the social filter
English
0
0
1
113
Fauna Robotics
Fauna Robotics@faunarobotics·
Meet Sprout. Today, we’re releasing a new kind of robotics platform. One designed to move out of the lab and into the real world, closer to the people who will shape what robots become next. [1/4]
English
137
183
1.7K
274K
XHabib
XHabib@XHabib·
Comment for a Lego version of your profile picture
XHabib tweet media
English
127
3
338
72.6K
Pari Singh
Pari Singh@paritheengineer·
@bhalligan Multi-year hides the problem not solves it. Would update customers -> Product (NPS/activation) :)
English
1
0
2
119
Brian Halligan
Brian Halligan@bhalligan·
“You only find out who’s swimming naked when the tide goes out.” In ai land, that’s the renewal rate on the contracts you signed a year ago. If you want to fix churn, fix incentives. Sales org - clawback on churn; commission kickers on retention. Customers - longer contracts w no outs. Get ahead of your month 12 renewals.
English
16
1
85
9.9K
Pari Singh
Pari Singh@paritheengineer·
Medical needs to be more like modern aerospace. The agile wave is coming for all industries and I'm pumped
DANISH@astrodanish

This has been my major issue transitioning from aerospace to biomedical engineering. In aerospace, EVERYTHING is up for debate. you wana put the wings backwards on a plane? fuck it, Sukhoi su-47. Oh you want intermeshing rotors? Kaman K-max it is. In medicine, people flex their credentials (“doctor here 👋”) and rely on prior art: “usually are not” “standard practice” “typically not” EVERYTHING should be grounded in first principles and rigorous testing. Medicine is not like that, because of people like Dr. Kelly Morrison who look at a miraculous full body scanning technology that can see through you at unprecedented resolution- LITERALLY SCI-FI TECHNOLOGY- and can’t imagine using it for preventative means- simply because people haven’t done that before. You could give a magic X-ray gun to some third world, medieval shaman or witch-doctor and the first thing they would say is “yo we should scan everyone and make sure nothing looks weird inside”. How is this not the obvious response? I can’t see a future in which everyone isn’t getting MRI’d and having their images analyzed by AI. The future of medicine IS PREVENTATIVE. i don’t give a fuck what any doctor or pharma company says about it. Their incentive structures have been broken for the last hundred years. An ounce of prevention > a pound of cure. Please, for the love of God, think a LITTLE outside the box for once!

English
0
0
0
393
Pari Singh
Pari Singh@paritheengineer·
Hardware development's biggest problem is not engineering, it’s communication. 10 engineers -> 45 connections 20 engineers -> 190 connections 30 engineers -> 435 connections Every time you 3x your engineering organization, you 10x the number of connections (Metcafes Law) Engineering used to be single player (one person on CAD), then it became multi player (CAD Engineer, Sim Engineer, Electrical Engineer). Now it’s Multi-disciplinary. Systems are now so complex that the tiniest change in one engineers excel power budget model, effects a CAD engineers design, effects a sim engineer’s boundary conditions, effects the multiphysics model, which the breaks a mission critical requirement. Most teams are still relying on word of mouth, slack, email and design reviews. The moment you cross 10 engineers, and dont have a solution to this, its hard to build important things. How do you solve this? The answer is iteratively. Iterate your communication system at the same speed you iterate your product (or in reality, org chat). This is a hard problem, how do you think about configs, variants. Do you group by function (analysis, structures, systems) or by products (Gen 1, Gen 2, Gen 3). How do you enable teams to move fast in thier bubble (engines, powertrain) but stay deeply connected to changes that may effect them. The system that works at 30 people one team, won’t scale to 100 people with 5 teams, it doesn’t scale to different functions (analysis, systems etc) and it doesn’t scale to multi program. We’re privileged enough to be working with the fastest growing important automotive, robotics, nuclear, space and defense companies globally. If you're growing from 10 -> 50, 50 -> 100, or 100 -> thousands - we'd love to hear how you're solving this!
Pari Singh tweet media
English
0
0
1
288
Pari Singh 已转推
Seth Bannon
Seth Bannon@sethbannon·
Venture is healing.
Seth Bannon tweet media
English
14
25
179
14.3K