From 8cd4ebb794857feb9bd77fae9c7062c3f494eb8c Mon Sep 17 00:00:00 2001
From: Northurland <40388212+Northurland@users.noreply.github.com>
Date: Fri, 26 Oct 2018 13:23:24 +0800
Subject: [PATCH] Update 20181014 How Lisp Became God-s Own Programming
 Language.md

---
 .../20181014 How Lisp Became God-s Own Programming Language.md  | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/sources/talk/20181014 How Lisp Became God-s Own Programming Language.md b/sources/talk/20181014 How Lisp Became God-s Own Programming Language.md
index c02447a637..a1dcf6c2eb 100644
--- a/sources/talk/20181014 How Lisp Became God-s Own Programming Language.md	
+++ b/sources/talk/20181014 How Lisp Became God-s Own Programming Language.md	
@@ -1,3 +1,5 @@
+Northurland Translating
+
 How Lisp Became God's Own Programming Language
 ======
 When programmers discuss the relative merits of different programming languages, they often talk about them in prosaic terms as if they were so many tools in a tool belt—one might be more appropriate for systems programming, another might be more appropriate for gluing together other programs to accomplish some ad hoc task. This is as it should be. Languages have different strengths and claiming that a language is better than other languages without reference to a specific use case only invites an unproductive and vitriolic debate.