[FerociousTimes]

Writing boilerplate code manually is not something that should be touted as best practice esp if you intend to reinvent the wheel every time you want a use case implemented that was probably covered thoroughly by a framework somewhere else.

With frameworks esp the ones like RoR, the Convention over Configuration (CoC) consideration trumps all the purported benefits that may arise from building your own framework from scratch.

You just learn the fundamentals of one of the most robust and well-established frameworks once, and forget about all the fluff and cruft for good, and just focus on building the business logic and satisfying the user's/customer's needs.

The Not Invented There (NIT) anti-pattern is one hell of a drug!

[npn]

well one of the weakest point of crystal is it's slow compiling time. A full-featured framework for crystal looks nice on paper, but after your app grow it will become a hinder instead, solely for the additional compiling time overhead of all the nice features the framework provided.

It hurts my productivity so bad I have to split the code base to multi independent services, each one use a simple server to serve some part of the system. After this those frameworks just cease to being helpful.