When I was a postdoc in genomics, one of my supervisors had a background in mathematics. Current bioinformatics training pipeline didn't exist yet, so most PhD students and postdocs had a background in something like CS, mathematics, statistics, or physics.
From the supervisor's perspective, people coming from pure mathematics were good at thinking about definitions. Coming up with useful definitions was the primary value they created, while theorems and proofs were just technical stuff they did to evaluate the value of proposed definitions.
My own background was in theoretical computer science, specifically algorithms. When you do algorithms without any qualifiers, you are studing them as mathematical objects in a simplified model of computation. The process often starts with a promising algorithmic idea. But if it looks like you can't prove anything nontrivial about the idea, you often stop studying it, regardless of the actual value of the idea. And if you manage to prove something, you start optimizing the algorithm for your theoretical model in order to prove better results. That usually makes it worse in practice.
The end result is that algorithms papers, both good and bad, typically contain theorems and proofs about algorithms nobody cares about. If you are a practicioner, you need to dig through all that noise to find the core algorithmic ideas, so that you can evaluate them in a more realistic setting. And if you are a theoretician, you are probably more interested in the techniques used in the proofs (which may also inspire future algorithmic ideas) than in the actual results.
You can find plenty of other similar situations. The value mathematicians create is rarely in the theorems and the proofs.
I was talking about the value created by mathematics. Which largely comes from training people to think about technical details. Which typically manifests as new ideas based on deep technical understanding of earlier ideas.
From the supervisor's perspective, people coming from pure mathematics were good at thinking about definitions. Coming up with useful definitions was the primary value they created, while theorems and proofs were just technical stuff they did to evaluate the value of proposed definitions.
My own background was in theoretical computer science, specifically algorithms. When you do algorithms without any qualifiers, you are studing them as mathematical objects in a simplified model of computation. The process often starts with a promising algorithmic idea. But if it looks like you can't prove anything nontrivial about the idea, you often stop studying it, regardless of the actual value of the idea. And if you manage to prove something, you start optimizing the algorithm for your theoretical model in order to prove better results. That usually makes it worse in practice.
The end result is that algorithms papers, both good and bad, typically contain theorems and proofs about algorithms nobody cares about. If you are a practicioner, you need to dig through all that noise to find the core algorithmic ideas, so that you can evaluate them in a more realistic setting. And if you are a theoretician, you are probably more interested in the techniques used in the proofs (which may also inspire future algorithmic ideas) than in the actual results.
You can find plenty of other similar situations. The value mathematicians create is rarely in the theorems and the proofs.