Josh is right. ActiveRecord, MVC, Front Controller(router + ActionDispatch), Template View(ERB) as well as a lot of what works under the hood in ActiveRecord comes from that book.
Though when I mean conventions I also mean where files are placed, how tables and fields are named, how migrations work and how DRY is part of the framework through and through.
A Loco app doesn't require fiddling with the database at all to replace its Rails counterpart. Hence why this naming of project confused me.
exactly right but think about it a bit, the responsibility is kinda off shored to the library owner and the library is used by many and battletested meanwhile
with ai the only one that use that code is only him and the reponsibility is still on him
reply