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 it back together. Write code every day and learn something new every day. The more you do this, the more you will learn and the better you will become.
- Backchannel, The Apple Watch project – “Gathering the best writing on Medium about the Apple Watch. Now we’re asking you to highlight and respond to these dispatches. Ultimately, we will cull the best passages to make the best Apple Watch review ever.”
- Trying to scratch a collective itch – A Personal Knowledgbase (Part 2)
- introducing Boomstat
- 365 Days of Pixel Art
- Rethink Digital Newspaper: The New York Times
“Under the hood, most critical software you use every day (like Mac OS X, or Facebook) contains a terrifying number of hacks and shortcuts that happen to barely fit together into a working whole. It would be like taking apart a brand-new 747 and discovering that the fuel line is held in place by a coat-hanger and the landing gear is attached with duct tape.”
— Ben Cherry
But by and large, people, I think, are still using the internet just as a utility.
That’s primarily one of the reasons why “how to” articles are still so popular. People go online when they need help with something. You need a fact, you look up the answer. You need to make something, you look up a recipe. You need to get somewhere, you look up directions. You need to buy something, you look up the product.