From 22b30b4408bdd6e86c4a690f029f28024003db7a Mon Sep 17 00:00:00 2001 From: bryan Date: Wed, 18 Mar 2020 16:28:12 -0400 Subject: [PATCH] Grammar --- .../_posts/2020-03-18-insert-code-blocks-from-repository.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/blog.bryanroessler.com/_posts/2020-03-18-insert-code-blocks-from-repository.md b/blog.bryanroessler.com/_posts/2020-03-18-insert-code-blocks-from-repository.md index 3098c6c..90a728a 100644 --- a/blog.bryanroessler.com/_posts/2020-03-18-insert-code-blocks-from-repository.md +++ b/blog.bryanroessler.com/_posts/2020-03-18-insert-code-blocks-from-repository.md @@ -6,10 +6,9 @@ subtitle: Keep your tutorials in sync with upstream code tags: [jekyll, ruby, liquid, tags, git] --- - ### Overview -In addition to journaling, blogs are a great way to share code solutions with users searching for solutions to similar problems. However, most code is ever-evolving as any programmer will tell you, "code is only finished when it is abandoned." Writing static journal entries containing copy-and-pasted code blocks means that your blog's code blocks will eventually diverge from the most up-to-date commits in your version controlled repository as you continue to improve your software. +Blogs are a great way to share code with users searching for solutions to similar problems. However, most code is ever-evolving, and as any programmer will tell you, "code is only finished when it is abandoned." Writing static journal entries containing copy-and-pasted code blocks will lead to divergence from your code repositories as you continue to improve your software. **Wouldn't it be great if your blog's code blocks could dynamically track the code residing in your version control repository?**