I happen to know something about this case, and I don’t think it’s quite as you describe it.
Most of the research in this area describes itself as “algorithm engineering.” While papers do typically prove correctness, they don’t provide strong theoretical time and space bounds. Instead, they simply report performance numbers (often compared against a more standard algorithm, or against previous results). And the numbers are based on real-world graphs (e.g. the highway network for North America). In one paper I read, there was actually a chart of various tweaks to algorithm parameters and how many seconds or milliseconds each one took (on a particular test case).
This is probably the best of both worlds, but of course, it is only applicable in cases where algorithms are the hard part. In most cases, the hard part might be called “customer engineering”—trying to figure out what your customer really needs against what they claim to need, and how to deliver enough of it to them at a price you and they can afford.
I happen to know something about this case, and I don’t think it’s quite as you describe it.
Most of the research in this area describes itself as “algorithm engineering.” While papers do typically prove correctness, they don’t provide strong theoretical time and space bounds. Instead, they simply report performance numbers (often compared against a more standard algorithm, or against previous results). And the numbers are based on real-world graphs (e.g. the highway network for North America). In one paper I read, there was actually a chart of various tweaks to algorithm parameters and how many seconds or milliseconds each one took (on a particular test case).
This is probably the best of both worlds, but of course, it is only applicable in cases where algorithms are the hard part. In most cases, the hard part might be called “customer engineering”—trying to figure out what your customer really needs against what they claim to need, and how to deliver enough of it to them at a price you and they can afford.