From 87da43a4db9a84ae206c27248b11cf614214072d Mon Sep 17 00:00:00 2001 From: brettlangdon Date: Thu, 2 Jul 2015 19:41:37 -0400 Subject: [PATCH] nix the last sentence --- contents/writing/about/write-code-every-day/index.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/contents/writing/about/write-code-every-day/index.md b/contents/writing/about/write-code-every-day/index.md index 41e84af..50c6e51 100644 --- a/contents/writing/about/write-code-every-day/index.md +++ b/contents/writing/about/write-code-every-day/index.md @@ -46,9 +46,7 @@ Anywho, enough of me trying to self promote projects. The main point is that by already exists, without really trying to do anything new, I came up with an idea which spawned another project and for at least a week (and continuing now) gave me a reason to write code every day. Not only did I write something useful that I can now use in any future project of mine, I also learned something I did not know before. I learned -how to hand code a syntax parser in `go`. I like using this approach for learning new tools as well. Want to learn -`python`, `go`, `c`, `erlang`, `react`, `web components`, `angular`, `ember`, `express`, ``, -then write something you already know about first. +how to hand code a syntax parser in `go`. Ultimately, try to take "coding every day" not as a challenge to write something useful every day, but to learn something new every day. Learn part of a new language, a new framework, learn how to take something apart or put