Explore >> Select a destination
|
You are here 
|
www.kalzumeus.com | ||
| | | | |
konradreiche.com
|
|
| | | | | Ruby on Rails applications are modelled around active record yet what if your application is based on a domain which needs to be provided in a programmatic way? In other words, your application, controller and views stand on a fixed set of Ruby classes yielding the context. In a manual fashion one would implement this by creating controller and views for each specific class. Assuming that the classes of this domain share the same interface this approach would introduce a lot of redundancy. With meta-programming this amount can be cut down. | |
| | | | |
blog.jayfields.com
|
|
| | | | | The default architecture for Ruby on Rails, Model View Controller, can begin to break down as Controllers become bloated and logic begins to... | |
| | | | |
postmodern.github.io
|
|
| | | | | ||
| | | | |
www.seancdavis.com
|
|
| | | Conditional email notifications may be immortal, but we can still figure out how to implement them on emerging Jamstack websites. | ||
