I don't think so, and depending on your familiarity with the topic, your opinion might be different too.

Creating a web application framework that handles your needs can be incredibly easy. I can, and have multiple time, done so in Perl for a quick project in the distant past. It takes about 20-30 lines or so on top of loading the modules you would probably already want available for a system like that. Pull in HTTP::Daemon, pull in the HTTP modules, tie them together with a little regex foo for route parsing, done. In the very simple case, it's easier to do this than pull in a framework. In the very complex case where you need intricate control over odd parts of the process that frameworks don't usually give you, it's easier if you had written your own from scratch. In all the other cases, which I feel I was being generous in saying was only 99.99% of the time, you're better off having offloaded the concern to someone else.

Creating a database is also very easy. In the simplest case, you choose a record structure and write to disk opportunistically or on every change. Again, for the very simplest case, that's actually easier than even pulling in SQLite. In the very complex case, you can do interesting preprocessing and specialized storage techniques to store your data in ways that aren't amenable to anything except for a custom format.[1] Again, the vast majority of the time, you just use SQLite, Redis, or a RDBMS and it does a passable job at dealing with all your data integrity and warehousing needs. If you're a company trying to manipulate a dataset in a heretofore unseen way (either much faster or much more detailed that before), you might actually need to do it from scratch.

Creating a car is also fairly easy, if you have the prior experience (about as much or less as expected above). Like above, you're largely throwing existing parts together and the hard work is knowing what goes where and shaving off the pointy bits that prevent it from fitting really well. If you need to race something (because why else do you create a car?), in the simplest case you might just grab some cheap broken down beater and put a little work into it where needed and you have something that goes in a circle and you won't care too much if it barely finishes. If you have the money, you can buy a pre-built race-ready car and compete as am amateur. If you're an F1 team, you build the whole thing from the ground up to exact specifications.

This is, of course, all presupposing that the people involved actually have the knowledge and ability to do the really simple or advanced things. Often, they don't, or at least don't have enough to make it even feasible. For example, I know how to read and write CSS, but I'm not very good at it. Similarly, I know how to write HTML and apply CSS fairly in an amateur manner. I'm not a UI or UX designer. Does it really behoove me to learn the intricacies of design layout instead of using Bootstrap? I either don't care about how it looks at all, in which case I'll make it text/plain or at the most a couple of header tags, or I care enough that to make it somewhat passable visually I'll use Bootstrap. In what situation am I better off using CSS? In what way does that apply to more than 0.01% of the people out there?

1: https://news.ycombinator.com/item?id=15350115