why aren't all 11 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
Prediction Not checkable as stated
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…”
Prediction Not checkable as stated
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,…”
Prediction Not checkable as stated
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…”
Prediction Not checkable as stated
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.”
Prediction Not checkable as stated
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.”
Prediction Not checkable as stated
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.”
Prediction Not checkable as stated
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?”
Prediction Not checkable as stated
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…”
Prediction Not checkable as stated
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.”
Prediction Not checkable as stated
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.”
Prediction Open · timeframe Dec 2027
Lauritzen Projects Legora Will Reach 270 Engineers by End of 2027
“If I have to put my, I want to say the lower number let's say two 70.”