Yaser

6.7K posts

Yaser banner
Yaser

Yaser

@YaserBi

Building ORGN

Decentralized Katılım Eylül 2013
1.9K Takip Edilen9K Takipçiler
Yaser retweetledi
Origin
Origin@orgn_official·
We shipped cryptographic attestation before the AI IDE. Most people would think it's backwards. The logical sequence would be to build the product first, then layer in the compliance later. But we couldn't have retrofitted it later. It had to be the foundation.
English
17
25
52
1.1K
Yaser
Yaser@YaserBi·
@chamath Through our propriety OLLM you access to more than 100 LLM. One simple click. Check Orgn.com Ollm OLLM.com
English
0
0
0
53
Chamath Palihapitiya
Chamath Palihapitiya@chamath·
This is increasingly becoming a very useful feature for Enterprises as they a) decide to swap models because of cost b) decide to swap models because of one's ToS c) decide to swap models because of security d) decide to swap models because of capability etc etc etc Being tied to one Foundational Model is quickly becoming a bottleneck that can and should be avoided if you value your independence and flexibility. Software Factory resolves this for complex projects within Enterprises. A very useful, under-repped feature as it turns out...
8090@8090_Factory

Switching from Claude Opus 4.7 to Codex GPT-5.5 is one keystroke. The prompts, evals, and checklists tuned for the old model are not. Software Factory is the control plane: Requirements, Blueprints, Work Orders, Tests, & Feedback bound by the Knowledge Graph. Build once. Swaps are free. 8090.ai

English
33
15
373
170.2K
Yaser
Yaser@YaserBi·
@chamath Agree. We just launched Orgn.com. Confidential AI dev platform. That is the future.
English
0
0
0
437
Chamath Palihapitiya
Chamath Palihapitiya@chamath·
Told you. At 8090, we’re actually helping organizations (large and small) implement their AI transformation methodically and in a disciplined way that a) doesn’t leak all their data into model training and b) doesn’t just blow their OpEx budget to the benefit of yet another tool provider.
Hedgie@HedgieMarkets

🦔An internal Amazon document obtained by Business Insider reveals that AI is making the company's existing tool duplication problem significantly worse. Teams are spinning up AI-powered applications so quickly that overlapping systems are proliferating faster than they can be consolidated. When AI ingests internal data and converts it to new formats, those outputs are stored separately from the original source, meaning if the original data is deleted or access is restricted, derived versions persist. In one documented case, a system called Spec Studio continued displaying software details that had been made private in Amazon's internal code repository. Amazon's proposed solution to the AI sprawl problem is more AI. My Take This document is the organizational context underneath the AWS outage story from December, where an AI tool deleted an entire production environment while fixing a minor bug and took 13 hours to recover. That kind of failure is what happens when you've layered AI tools on top of AI tools inside a company where teams are independently spinning up systems faster than anyone can track them, where derived data persists after the source is restricted, and where the culture of autonomous two-pizza teams means nobody has full visibility into what's actually running. Mandating AI adoption without the governance infrastructure to manage it produces exactly what Amazon's document describes. The speed at which AI lowers the barrier to building new tools is being treated as a feature while the document makes clear it compounds in both directions, more duplication being created faster and less of it being cleaned up. Amazon's answer to the AI sprawl caused by AI is more AI, which is also exactly what they proposed after the December outage. At some point that stops being a strategy. Hedgie🤗

English
45
22
393
236.6K
Yaser
Yaser@YaserBi·
We are in DC
English
0
0
2
218
Yaser retweetledi
Origin
Origin@orgn_official·
Introducing Origin: The world's first confidential dev environment After months in stealth, Origin is live! Now, devs never have to choose between building and security. Enterprise-grade encryption keeps your IP safe from start to finish Origin scales from startup to enterprise, so you can innovate without limits Join the confidential coding revolution at orgn.com Build Everything. Expose Nothing. #Origin #ConfidentialCoding
Origin tweet media
English
28
37
87
4.6K
Yaser retweetledi
Origin
Origin@orgn_official·
We've been building something big behind closed doors. Tomorrow, we reveal it. Introducing ORGN, the world's first confidential coding platform. Your code stays yours. Always. Build Everything. Expose Nothing. → orgn.com #ORGN #ConfidentialCoding
English
20
34
84
5.9K
Yaser retweetledi
Origin
Origin@orgn_official·
Certificates don't protect your code ORGN is different: • Confidential compute for total code isolation • Cryptographic proof your code ran in isolation • No retention or cross-use of your IP Build Everything, Expose Nothing.
Origin tweet media
English
28
23
75
1.9K
Yaser
Yaser@YaserBi·
50% workforce cut because of AI. Societal unrest is coming.
jack@jack

we're making @blocks smaller today. here's my note to the company. #### today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone. first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay. we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly. i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures. a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers. we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold. to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward. to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow. jack

English
1
0
1
158
Yaser retweetledi
RetroOptions 📈
RetroOptions 📈@RetroOptions·
@theo See comments below this post for source links:
RetroOptions 📈 tweet media
English
1
1
3
4.4K
Yaser
Yaser@YaserBi·
Introducing ORGN (pronounced origin) Every enterprise wants to build at the speed of AI. But regulated industries can’t use Cursor, Devin, or Copilot - compliance won’t allow it. Built-in cryptographic security. Enterprise-ready from day one. In fact our engineers stopped using Cursor. We’re now building Origin with Origin. We’re opening access to a select group of early testers. If you’re building AI in defense, finance, or healthcare DM me or comment below to join. orgn.com
English
1
0
1
140