From f600eb8550561d619ae6c0d93163a786359a9541 Mon Sep 17 00:00:00 2001 From: Carson Gross Date: Sun, 24 Nov 2024 18:00:42 -0700 Subject: [PATCH] essay fix --- www/content/essays/codin-dirty.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/www/content/essays/codin-dirty.md b/www/content/essays/codin-dirty.md index c15c6ccb..624c929d 100644 --- a/www/content/essays/codin-dirty.md +++ b/www/content/essays/codin-dirty.md @@ -254,7 +254,7 @@ Active Record provides a way for you to map ruby object to a database, it is wha And it does a great job of that, in my opinion: it makes the easy stuff easy, the medium stuff easy enough, and when push comes to shove you can kick out to raw SQL without much fuss. -(This is a great example of ["layering"](https://grugbrain.dev/#grug-on-apis) and API.) +(This is a great example of what I call ["layering"](https://grugbrain.dev/#grug-on-apis) an API.) But that's not all the Active Record objects are good at: they also provide excellent functionality for building HTML in the [view layer](https://guides.rubyonrails.org/action_view_overview.html) of Rails. They don't include *HTML specific* functionality, but they do offer functionality