The idea that frameworks solve problems is mostly marketing. They shift the nature of the problems, making some things easier and others harder. The trick is choosing the right tools for your constraints.

Readability is not about clever code or terse syntax. It's about making the intent of the code obvious to the next person who reads it—which might be you, six months later, having forgotten everything.

Related

More on this topic

Most of the code we write is not rocket science. It's ordinary business logic, wrapped in layers of frameworks and abstractions. Sometimes the simplest implementation is the best.

The best code is often the code you don't write.

Type systems don't prevent bugs—they just catch certain categories of bugs earlier. The real benefit is the documentation they provide about what a function is supposed to do.