update heroku resources

mattmakai · mattmakai · commit 82c8ed4d8790 · 2021-09-21T06:39:30.000-04:00
diff --git a/content/pages/05-deployment/10-heroku.markdown b/content/pages/05-deployment/10-heroku.markdown
@@ -21,7 +21,14 @@ easily [deploy](/deployment.html) Python applications.
   [MySQL](/mysql.html) to [PostgreSQL](/postgresql.html) if necessary 
   as well as how to properly handle your settings files.
 
-* Heroku's 
+* [How to deploy Django project to Heroku using Docker](https://www.accordbox.com/blog/deploy-django-project-heroku-using-docker/)
+  explains that although [Buildpacks](https://devcenter.heroku.com/articles/buildpacks)
+  are the most common way to deploy to Heroku, packaing your app in a 
+  [Docker](/docker.html) container is also a viable approach. It walks through
+  the steps needed to deploy a [Django](/django.html) app in the remainder
+  of the article.
+
+* Heroku's
   [official Python documentation](https://devcenter.heroku.com/articles/getting-started-with-python) 
   is fantastic and walks through deploying WSGI applications in short order.
 
diff --git a/content/pages/10-working/18-developer-demos.md b/content/pages/10-working/18-developer-demos.md
@@ -9,18 +9,19 @@ meta: How to give technical demos to software developers.
 
 Creating and executing an appealing technical demo to an audience of software
 developers is a ton of work, but there is no better way to get people 
-legitimately interested in your product if you land a great demo. The 
-inherent difficulty involved in exceptional technical demos also creates
-a large moat that prevent others from easily copying the work you put into
-the demo.
+legitimately interested in your product if you land a great demo with
+an appropriate audience. The inherent difficulty involved in exceptional 
+technical demos also creates a large barrier that prevent others from simply 
+copying your work, which can happen with technical blog content.
 
-The most important parts to a standout technical demo are:
+To achieve a standout technical demo you must:
 
-1. show how to solve a difficult technical problem, as easily as possible
-1. take the audience on a story arc
-1. do it live (especially if you include code)
-1. rehearse constantly, both happy path and recovering from errors
+1. show how to easily solve a difficult technical problem
 1. speak plainly but accurately
+1. do it live, including writing code if required
+1. tell a story with a narrative arc
+1. rehearse constantly, both the happy path and recovering from errors
+
 
 Examples: 
 * [Twilio Phone Calls Demo at NY Tech Meetup (2010)](https://www.youtube.com/watch?v=-VuXIgp9S7o)
