Paul Scivetti

Independent software developer/application architect.
Entrepreneur;
Techmaster;
Catalyst for Change

[Ben Smith @bensmithlive]

A single night of sleep can now predict 130 future diseases with up to 93% accuracy.

Stanford researchers just released SleepFM.

This is a multimodal foundation model trained on 585,000 hours of physiological data from 65,000 participants.

And it's actually insane: (1/5)

[Paul Scivetti @theideaguy]

@ericelliott_ Also consider a cancelled section. Putting cancelled deals in with closed is a little misleading. I.e.the closed count of 2 is green but really only one was $$$ closed

[Paul Scivetti @theideaguy]

@ericelliott_ Also saw a couple of defects...marked a deal signed and it isn't green.

[Paul Scivetti @theideaguy]

@ericelliott_ I rechecked... working as expected. You might want to switch the sign and cancel buttons so the back it up one step is immediately to the left of the sign button. Just a thought to avoid fat finger errors on small screens.

[Paul Scivetti @theideaguy]

@ericelliott_ It is possible I signed then put it back to unsigned and then re-signed. I can check it again.

This was all done on my android phone.

[Paul Scivetti @theideaguy]

@ericelliott_ Not at the moment. My current role is full time plus... heavy on the plus. I'd like to get back to it down the road... but not happening soon.

[Paul Scivetti @theideaguy]

@ericelliott_ One final thought, show the date each step occurred. That would also serve as a tickler to reach out for deals languishing in the pipeline.

Paul Scivetti
I was an indie consultant for 25 years until health insurance costs sank us.

[Paul Scivetti @theideaguy]

@ericelliott_ BTW, I sent through 4 replies... only see 3 on LinkedIn. The missing one was the review. Let me know if that got lost. Happy to resend

[Paul Scivetti @theideaguy]

@ericelliott_ Sometimes buttons are off screen

[Paul Scivetti @theideaguy]

@ericelliott_ @ericelliott_ very nice, especially for coming together so fast. Call me old school, but when editing a record, I really prefer save or cancel buttons to the 'just change as you type' paradigm.

I'd like an optional tag for lead categorization and a field for timeframe

[Sam Altman @sama]

I would like to clarify a few things.

First, the obvious one: we do not have or want government guarantees for OpenAI datacenters. We believe that governments should not pick winners or losers, and that taxpayers should not bail out companies that make bad business decisions or otherwise lose in the market. If one company fails, other companies will do good work.

What we do think might make sense is governments building (and owning) their own AI infrastructure, but then the upside of that should flow to the government as well. We can imagine a world where governments decide to offtake a lot of computing power and get to decide how to use it, and it may make sense to provide lower cost of capital to do so. Building a strategic national reserve of computing power makes a lot of sense. But this should be for the government’s benefit, not the benefit of private companies.

The one area where we have discussed loan guarantees is as part of supporting the buildout of semiconductor fabs in the US, where we and other companies have responded to the government’s call and where we would be happy to help (though we did not formally apply). The basic idea there has been ensuring that the sourcing of the chip supply chain is as American as possible in order to bring jobs and industrialization back to the US, and to enhance the strategic position of the US with an independent supply chain, for the benefit of all American companies. This is of course different from governments guaranteeing private-benefit datacenter buildouts.

There are at least 3 “questions behind the question” here that are understandably causing concern.

First, “How is OpenAI going to pay for all this infrastructure it is signing up for?” We expect to end this year above $20 billion in annualized revenue run rate and grow to hundreds of billion by 2030. We are looking at commitments of about $1.4 trillion over the next 8 years. Obviously this requires continued revenue growth, and each doubling is a lot of work! But we are feeling good about our prospects there; we are quite excited about our upcoming enterprise offering for example, and there are categories like new consumer devices and robotics that we also expect to be very significant. But there are also new categories we have a hard time putting specifics on like AI that can do scientific discovery, which we will touch on later.

We are also looking at ways to more directly sell compute capacity to other companies (and people); we are pretty sure the world is going to need a lot of “AI cloud”, and we are excited to offer this. We may also raise more equity or debt capital in the future.
But everything we currently see suggests that the world is going to need a great deal more computing power than what we are already planning for.

Second, “Is OpenAI trying to become too big to fail, and should the government pick winners and losers?” Our answer on this is an unequivocal no. If we screw up and can’t fix it, we should fail, and other companies will continue on doing good work and servicing customers. That’s how capitalism works and the ecosystem and economy would be fine. We plan to be a wildly successful company, but if we get it wrong, that’s on us.

Our CFO talked about government financing yesterday, and then later clarified her point underscoring that she could have phrased things more clearly. As mentioned above, we think that the US government should have a national strategy for its own AI infrastructure.

Tyler Cowen asked me a few weeks ago about the federal government becoming the insurer of last resort for AI, in the sense of risks (like nuclear power) not about overbuild. I said “I do think the government ends up as the insurer of last resort, but I think I mean that in a different way than you mean that, and I don’t expect them to actually be writing the policies in the way that maybe they do for nuclear”. Again, this was in a totally different context than datacenter buildout, and not about bailing out a company. What we were talking about is something going catastrophically wrong—say, a rogue actor using an AI to coordinate a large-scale cyberattack that disrupts critical infrastructure—and how intentional misuse of AI could cause harm at a scale that only the government could deal with. I do not think the government should be writing insurance policies for AI companies.

Third, “Why do you need to spend so much now, instead of growing more slowly?”. We are trying to build the infrastructure for a future economy powered by AI, and given everything we see on the horizon in our research program, this is the time to invest to be really scaling up our technology. Massive infrastructure projects take quite awhile to build, so we have to start now.

Based on the trends we are seeing of how people are using AI and how much of it they would like to use, we believe the risk to OpenAI of not having enough computing power is more significant and more likely than the risk of having too much. Even today, we and others have to rate limit our products and not offer new features and models because we face such a severe compute constraint.

In a world where AI can make important scientific breakthroughs but at the cost of tremendous amounts of computing power, we want to be ready to meet that moment. And we no longer think it’s in the distant future. Our mission requires us to do what we can to not wait many more years to apply AI to hard problems, like contributing to curing deadly diseases, and to bring the benefits of AGI to people as soon as possible.

Also, we want a world of abundant and cheap AI. We expect massive demand for this technology, and for it to improve people’s lives in many ways.

It is a great privilege to get to be in the arena, and to have the conviction to take a run at building infrastructure at such scale for something so important. This is the bet we are making, and given our vantage point, we feel good about it. But we of course could be wrong, and the market—not the government—will deal with it if we are.

[Eric Elliott @ericelliott_]

Think GPT-5 is great for AIDD? I have mountain of empirical test data that disagrees. GPT-5 frequently neglects important constraints and has the highest error rate of any of the models currently in my flagship model selection. @OpenAI @OpenAIDevs

[Paul Scivetti @theideaguy]

@ElonMNews A. Yes

[Paul Scivetti @theideaguy]

@_ericelliott Critical thinking is, sadly, almost a lost art these days. Very few people seem to actually think about data points or 'facts', consider overt or inadvertent bias, or consider reasonableness. We've gotten to 'if the computer says so, it must be true'. Very scary times.

[Paul Scivetti @theideaguy]

It is a great time to be alive, but all this techo magic is going to wreak havoc on the justice system. You can't trust anything you see or hear unless you were there, in person, as a witness.

Think about that. Can you really trust that surveillance video or audio recording?

[Alex Banks @thealexbanks]

We are at the iPhone moment of AI.

It will transform the future of speech, creativity & biology forever.

Here's every AI announcement from Nvidia's GTC event:

[Eric Elliott @ericelliott_]

Tech leads should be involved in the product discovery process.

[Paul Scivetti @theideaguy]

Not often reality, but yes.

[Eric Elliott @ericelliott_]

Marketing, biz dev, and sales should never dictate deadlines for engineering. If there is a hard deadline, scope must be very flexible to compensate.

[Paul Scivetti @theideaguy]

So true. Pay me now or pay me later...but pay the piper you will. The difference is when you cut too many corners, you pay forever. That leads to very poor long term ROI

[Eric Elliott @ericelliott_]

Beware of the tech debt firehose: Often the fastest feature builder. Managers love them, but they slow down the rest of the team with poor planning, inscrutable code, poor test coverage, and no docs.

[Steve (Builder.io) @Steve8708]

JavaScript Maps (new Map()) are more performant, ergonomic, and overall useful than you might think.

You may want to consider using them more often than you likely are.

Full video is now out!

[Paul Scivetti @theideaguy]

@avonelleL Keep it rolling! Way easier than having to start over.