The Ledger
Every statement that passed quotation and attribution checks. Mix any filter with any other: certainty 1/5, debate potential 5/5, or both at once.
why aren't all 17 resolved? a statement only gets an assessment when the public record can support or contradict it. opinions and what-ifs never can, and 0 checkable ones are still open, waiting for their date. predictions held up or didn't; assertions are supported or contradicted. on every card: ▮▮▮▮▮ certainty · ▮▮▮▮▮ debate potential. speakers are clickable
Osika: Enterprise AI strategy should target product velocity, not dev productivity
“If I was a CEO or like a CTO of a large enterprise company, I wouldn't think in terms of, oh, how can we make our engineers more productive? I would think in terms of how can we get the most information about what we should build as quickly as possible into ne…”
Osika: AI makes generalist skills far more important than deep specialized expertise
“Like, I think being a generalist becomes more and more important with everything, in everything with AI, so that you can understand how things come together as a larger whole, and then you use AI for the, like, deep expertise that you don't need in the future …”
Osika: AI model benchmarks decay over time due to Goodhart's Law
“I mean, they turn more and more bullshit over time. There's something called good hearts law. So when you start optimizing for a number, that number stops being a good measure for success.”
Osika: AI startups must build broad UX flywheels before launching autonomous agents
“In the context of lovable I thought we should be building an agent Before, like, the models were ready for it, and because the models were starting to get optimized for an agentic system, and what I realized is that, no, no, no, you need to have a product that…”
Osika: Early-stage AI founders should prioritize growth over defensibility
“I think that's my recommendation to just be like, execute fast, grow faster and then when you're starting to get up there, you can start, maybe start thinking a bit about the defensibility.”
Osika: Prioritize intense work over balance for short two-year stretches
“I think over a 10 year period, I would advocate for some balance, but over a two year period if you really care about something, then you should make sure that you have, like, you get your exercise, you sleep in really, really well, and maybe something that, y…”
Osika: Early startups must say yes broadly, but scaling requires focus
“What works in the beginning Is to say yes onto a lot of opportunities and try out what works. Once you become more people and you have to follow up and maintain everything that you start, you have to be much more focused.”
Osika: Domain experience can be a negative signal when hiring
“So I think experience can be a negative thing in some cases. You often want people who are super ambitious, they have a lot to prove, and they are more open-minded towards how, how you should work together in the team.”
Osika: Having a team slows down founders shipping V1 SaaS products
“Hey, if you want to ship the first version of your SaaS and start making money, it's all you. It's not a team. Like a team just slows you down.”
Osika: Founders should prioritize minimizing equity dilution over growing the pie
“Here again, like I have a very wise person who was like, no, dilution doesn't matter so much. It's all about the size of the pie. And I think that was, I was both affected by that advice as well as my, like, no, minimize dilution. This is my life, life's work.…”
Osika: Say no to most features to maintain Apple-like quality
“You should say no to as many things as possible and make it more of like an apple feeling. The things you do them superb.”
Osika: Hire Top Young Talent Before They Become Founders
“The best people that you can hire at a young age, they would go on and become founders, and then you can't hire them anymore, right? So, so that's why junior people are often quite good.”
Osika: Putting LLMs inside a for loop enables autonomous AI agents
“Hook them up and make you basically put the large language model in a for loop and then you can have it do a lot of agentic things.”
Osika: Product waitlists exist to control onboarding pace and conduct user research
“I think the waitlists are useful in that you can control exactly how many people you want to get on board and take user interviews with them.”
Osika: AI can easily destroy existing codebases without engineer oversight
“But once you have existing software, With users, and then you want to iterate and change that software, AI might absolutely bring down, kind of mess up your entire codebase.”
Osika: Startups should not innovate heavily on pricing models
“Otherwise, I think you shouldn't, don't innovate so much, too much on pricing. Do whatever works today.”
Osika: Product user research requires separating UX observation from pain-point discovery
“So they, I think for us, there are two different types of user interviews. We have this type where we just see them use the product and see, like, where do they understand the product? And so that's more of a user experience interview. And the other one is to …”