Yes: HTML. Seriously, just generate HTML on the backend and serve web pages like it's 1999. Easiest way to get 100% on all Lighthouse scores.

So long as you never have multi-page forms and don't worry about error handling on bad submissions and the back button, you're golden!

I still have nightmares of post-redirect-get complexity and giant balls of mud in session scope to support the back button.

Don’t write any code, easiest way to not have bugs.

You joke, but I have literally never had as great of a success at work as that one time my team didn't end up building the software.

We had great ideas about scheduling and caching and task priorities...

...and then we asked the customer what they wanted, and they wanted none of it.

So we built none of it, and produced a solution that just did the stupidest thing, and did it without any edge cases, without ever crashing, reliably, as a cronjob, once on Sunday night.

Some people would be disappointed that they couldn't put this on their CV because it didn't involve FancyTech #413, but damn it, I am still proud of that stupid thing.

I interviewed a (junior) candidate once that had tried and failed at a hackathon to build an Rails system that connected restaurants and shops with excess food to charities that gave food away to those that needed it.

I asked him what he’d done to work around the technical difficulties, and it turned out that he’d set up a Wordpress site with a phone number of the guy running the scheme, and a Google sheet to manage contact details.

A better definition of MVP I’m yet to see.

My take is that there's many unnecessary complexities (at least in many cases), where using an old, battle tested, "boring" technology suffice. The graph just seems to be an illustration of that, but it focus on storage (there could be a better graph that focus on the database only, but I guess the message is conveyed)

"You probably don't need as many back-end services as you think you do" isn't quite as good a title.