Working on more complex, logic heavy projects with strong performance needs I find the models to be useful but certainly not 'one shot' on pretty much anything. And often incredibly frustrating and genuinely bad code that collapses performance and bloats systems - like what a really bad junior might write.
When I'm working on large standard crud web projects with already decent architecture and a good harness and skills, honestly they work pretty well a lot of the times, the code looks good, does what it needs and fits in with the architectural style.
I really think a lot of hn people just write simple repetitive software, and a small portion works on complex, weird, dense, and novel'ish logic projects. The two obviously don't have the same experiences.