|
|
@ -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 |
|
|
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 |
|
|
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 |
|
|
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`, `<any other technology here>`, |
|
|
|
|
|
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 |
|
|
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 |
|
|
something new every day. Learn part of a new language, a new framework, learn how to take something apart or put |
|
|
|
