Jacob Lauritsen
22 statements across 1 episodes · 5 bullish · 7 bearish · 1 people on the record · first statement Jun 6, 2026 by Jacob Lauritzen · said 5 times in 1 episodes since 2026 · across every show →
Mentions by year
brought up most by Harry Stebbings (4)
tap a year for its mentions
Everything said about Jacob Lauritsen, oldest first
Jun 6, 2026
Jun 6, 2026 bullish
Jun 6, 2026 negative
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?”
Jun 6, 2026 negative
Jun 6, 2026
Jun 6, 2026 bullish
Jun 6, 2026 positive
Jun 6, 2026
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…”
Jun 6, 2026
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…”
Jun 6, 2026 positive
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…”
Jun 6, 2026
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.”
Jun 6, 2026 negative
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…”
Jun 6, 2026 negative
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.”
Jun 6, 2026
Jun 6, 2026 neutral
Jun 6, 2026 bearish
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…”
Jun 6, 2026
Jun 6, 2026 negative
Jun 6, 2026 neutral
Jun 6, 2026 positive
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.”
Jun 6, 2026 negative
Jun 6, 2026
Lauritzen: Hiring Untrusted Players Forces Top Engineering Talent to Leave
“I'd rather miss my number and have A players than hit it with B players, because I think as soon as you introduce players, as soon as you have people that you don't trust or that the team doesn't trust, the A players won't stick around.”