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 57 resolved? a statement only gets an assessment when the public record can support or contradict it. opinions and what-ifs never can, and 1 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
Lauritzen: Legora is avoiding hiring remote engineers to prioritize in-person collaboration
“Well, we're very opinionated about who we are and who we aren't. We, if you're a great engineer and you want to be remote, then you probably also want to work on very isolated problems, and that's, that can be fine. We'll, we'll, we probably have those, and we…”
Lauritzen: Writing code is no longer software development's main bottleneck
“And number two was the primary bottleneck for the past hundred years, almost. So like the rate limiter was how quickly can you write code? That is now super cheap. So that's sort of been compressed. And so the bottleneck now is like the two other ends, which i…”
Lauritsen: Enterprise engineers will primarily define guardrails for autonomous agents
“And I think that type of guardrail setting will see everywhere. And so, if you're a big enterprise, and you're rolling out AI tooling, and you have agents that build your own internal software, you know, you have AI tools that build your HRAS system, and your,…”
Lauritsen: Vibe coding clones hit 90% easily, but enterprise edge cases are hard
“It's very quick to get to the 90% where it looks the same, and in, like, 80% of the cases it works similarly. It's the other 90% that are difficult. You know, it's like ensuring all the edge cases work, and all the unhappy paths, and all the audit locking, and…”
Lauritsen: Enterprise Customers Do Not Buy Legora Based on AI Models
“Let's say you took away a model from LIGORA, people would still pick LIGORA. So they don't buy it based on the model.”
Lauritsen: Lawyers Prefer Superior Output Quality Over Fast Latency
“Almost always performance. Performance is more important. Almost always. If you're a lawyer, you can wait two seconds more for the output if it's better. You can probably wait an hour more for the output if it's better.”
Lauritsen: Traditional IDEs will die and reading lines of code will disappear
“The current shape of an ID will die. Yes. I think we, I don't know what the new, the next ideas, but it's not reading lines of code. It's maybe it's graphical, honestly. Like maybe it's the systems, the architecture that you look at and you review and you plan…”
Jacob Lauritsen: Elite engineers create more value than superior AI models
“Engineers. For sure. Because the models they change all the time, they get better all the time, but if you have really good engineers, you can build a system that exponentially improves, and that's worth a lot more.”
Lauritsen: Lawyers will shift from contract drafting to high-level risk strategy
“Eventually, lawyers will not be nitty gritty about the language of the contracts. They will work a level above, which is maybe like, What's our negotiation stance? Like what risks are we okay? Which ones are we not okay taking? And not sit and type into word.”
Legora CTO: AI tooling opportunity cost outweighs token expense
“I don't want to say infinite, but for me, it's a question of opportunity cost. We're in a competitive environment. There's so many things that we can do, and the cost of not doing it is extremely high. It almost outweighs any sort of token cost.”
Lauritzen: Incumbent enterprise giants suffer from a lack of employee enthusiasm
“No one in the 800 pound gorilla is extremely excited to be there.”
Lauritsen: Legora will soon create a dedicated role for AI agent meta-engineering
“I think the other thing that engineers are doing more and more, which is an explicit role with us soon, which is like kind of the meta engineering of making agents really effective.”
Lauritsen: Claude and Cursor generate over 50% of Legora's code
“Actually, I took a look recently, and it's Claude and Cursor on the top, and there's like, I think it's like two percent between them. So they are really, really close. And then it's, you know, miles above the next engineer. So they're way above 50%.”
Lauritsen: Software teams will skip the design phase for individual feature functionality
“Probably some companies will skip the design phase. I think we can skip the design phase on functionality.”
Lauritsen: Without product taste, unguided AI outputs converge to generic grayness
“I think if you don't have taste, then you let AI slop converge to sort of grayness, and everything looks the same, and everything's just like, I think you need to have taste to have sort of An opinion and it stands in the world. This is who we are. This is wha…”
Lauritzen: Internal vibe coding will become the future for enterprise software
“It will be the future. I don't know when, but it will be the future.”
Lauritsen: Custom software development makes sense for shallow, highly customized apps
“If it's a shallow app, and it requires a lot of customization from you, maybe you just build it. That's probably actually the right thing to do. If it's a very deep one, there's just too much stuff for you to build, and it's not viable for you to do.”
Lauritsen: Legora engineers run 10 background coding agents concurrently
“We have our own background coding agent that they built. That allows each engineer to have, like, 10 different agents running concurrently with, like, all of our local development, a browser, all the iteration stuff.”
Lauritsen: US engineers are less risk-averse while European engineers are more loyal
“In the US, people are generally less risk averse, so like, they'll, they'll be ready to jump on a lot of things to test. I think in Europe, people are more risk averse. People in Europe, and I'm super generalizing now, but I think Generally are more, I don't w…”
Lauritsen: Evaluating employees using AI token usage leaderboards is stupid
“Having a leaderboard, a lot of people say this, get a leaderboard and bring up token usage at performance reviews, And that leads to token maxing, which is people just burn tokens just to look good. That's a really stupid way to do anything.”
Lauritsen: Compute deficits force AI coding tools into harmful vertical integration
“Obviously they don't have enough compute. They can't train their own models. They probably have to train their own models. It's I just think it's a shame that the industry is, is vertically integrated in that way.”
Lauritzen rejects idea that executives are suited only for specific startup stages
“No, I don't buy that. I think It's, to me, it's a question of how quickly can I solve problems? Am I the person that can solve the problems that we have right now the fastest, or can someone else solve them faster than me?”
Lauritzen: Co-locating PMs, designers, and engineers eliminates handoff friction
“If you have a PM and a designer and an engineer, and they just sit together, You can almost not even have the handover. You can just be like, run at this problem and do it together, the three of you know, next week, and then it's done. But if you have them sil…”
Lauritzen: Legora Gives Firing Ultimatums to Underperformers Within Two Weeks
“I give really strong feedback after two weeks. What does really strong feedback mean, Jay? Really strong means you're not gonna stay if you don't change this. And feedback is feedback.”
Lauritzen: No Legora Employee Has Recovered From Ultimatum Feedback
“No. But they need to get the chance. And if they do, they stay.”
Lauritsen: Technical engineering managers who have scaled are extremely hard to hire
“I think senior management is extremely difficult to hire for. No yeah, or like engineering directors, engineering managers within, yeah, within product and engineering, yeah. Maybe that's always been difficult, but I think it's because we only have really tech…”
Lauritzen: Engineer productivity gains are reshaping software organization structure
“Each engineer can produce much more than they could previously and that just has a ton of ripple on effects throughout the org, basically, and how you structure it”
Jacob Lauritsen urges founders to build startups solving AI code review
“Current review tools are not good enough. I think we need something new. I keep telling people at all events that I'm at, like, if you're gonna do a startup, please do something that solves the review thing.”
Lauritsen: Code review should focus on architecture and security, not lines of code
“No one wants to look at the, all the lines of code. It's like, what's important is, what are the, what's the impact on systems architecture? What's the impact on systems design, stability security boundaries? How does it sort of take our system in the right di…”
Lauritsen: Software engineers will shift from writing code to system design
“Yeah, I think so. I think so. I think that's right. The job of assist, of a, of an engineer is changing from typing a bunch of code to sort of one layer above it, which is what does the system look like?”
Lauritsen: Legora vendor suffered security incident; predicts more breach events
“One of our vendors had a security incident just yesterday. We just rotated a lot. I mean, just, you know, to be clear, this was internally doesn't affect any of our clients or anything like that, but it's just, I think we're going to see more of them.”
Lauritzen: Legora Uses SRE AI Agents to Draft Incident Post-Mortems
“If you have an incident, now you just unleash an SRE agent, a sort of an incident agent, and it will just super quickly figure out what's going on, look at all the logs, look at all the metrics, metrics, sorry, Telemetry, and it's surprisingly good. It's reall…”
Lauritzen: AI Allows PMs to Test Prototypes Before Involving Engineers
“PEMs can prototype super, super fast. Which is really, really great because that means you can front load a lot of the work. So like a PM can start hyper long before once he or she has the, you know, smallest inkling of an idea that we might want to do this. T…”
Lauritsen: Legora still uses Figma for design system consistency and UI standards
“We still use Figma, yes. I know where you're going with this. As soon as you start building a system that's larger than something very small, you want consistency, and you want to have a design language and all that kind of stuff, and so you need somewhere to …”
Jacob Lauritsen: AI speed, product speed, and human adoption speed are distinct
“We have this notion internally that there's the speed of AI, there's the speed of our product, and then there's the speed of humans, you know, and they're like, they're not the same necessarily.”
Legora employee vibe coded a custom immigration app in one day
“Ryan, who joined from Canada, we have a team of people joining from Canada, they're all moving to Sweden, and he vibe coded an app to help everyone migrate. So like very specifically, if you're Canadian, these are like all the laws and all the steps you take, …”
Lauritsen: PMs should vibe code prototypes to reduce handover costs
“So it's good if PMs do some amount of vibe coding to, like, show very high fidelity, here's a prototype, this is exactly what it looks like.”
Lauritzen: Enterprise IT will evolve to build internal AI tools in 5 years
“I think the internal AI systems role thingy for enterprises, I think IT will, can have like a flowering moment here and, you know, go from being internal IT that's like setting up your computers and whatever to maybe have a system that's building a tons of int…”
Lauritsen: Legora may not need forward-deployed engineers in five years
“We currently do, yeah. But I think that's just, that's an education thing. In five years, maybe we don't at all, to be honest.”
Lauritsen: Harvey was more aggressive with hiring than Legora
“I think they've been more aggressive with hiring, which I actually think I have not been aggressive enough with hiring because I've always tried to have a very, very small, very lean team, which I believed a lot in.”
Lauritsen: Delaying Legora's Developer Experience team was a management mistake
“We have a developer experience team. Relatively new. Again, a mistake I made. I should have staffed that earlier.”
Lauritsen: European candidates struggle to properly value tech startup equity
“It's actually something that we had to sort of educate people on in Sweden. And in Europe, I think it's, people are just not used to the venture thing. They don't know how to value equity the same way.”
Lauritzen: Legora now designs all software systems to scale to 100x usage
“Now, now I make sure everything we build will scale to 100 X the usage. I used to say 10 X, but then that was not enough, so now everything needs to scale to a hundred X.”
Lauritzen: System fair queuing should prioritize small interactive requests over bulk tasks
“If you're running a 100,000 cells, you're probably okay waiting a bit. You can go grab a coffee and that's fine, but if you run 10 cells at the same time, those should be really fast.”