Innovating the boring stuff

There is no innovating it, you simply have to just do it.

This us a purely logical requirement, the cide is already abstracted to the maximum feasible point.

You simply have to write the code that connects the output of pipe A to the input of pipe B

This is called the Domain Rules or Business Rules, its the stuff specific to your apps needs that simply cant be abstracted further.

If we define for example "This endpoint lets you add a person to a room, but a room cannot have more than 8 people" you cannot get around needing to somehow define this business rules in your logic.

Even at its absolute most abstract form, its at least a couple lines of code minimum.

Now, most api endpoints have several rules. And often apis can have hundreds of endpoints. And often businesses maintain multiple apis.

So, 3 x ~7 x ~100 x ~3 puts you at like 6300 lines of code baseline for defining business rules.

And then for every. single. rule. You have to write a test that positive and negative tests these rules.

Which puts us at about 2100 rules, multiple by about easily 10 to 12 lines per test easy.

So 11 x 2100 = 23,100 lines of code for tests, though its prolly closer to double that.

ALL of this is extremely simple and easy to do, its just a lot of fuckin typing lol.

AI can pump this out in about 1/10th the time I can, prolly closer to 1/20th tbh.