"As a result, many young companies over focus their teams on their retention metrics, but do not spend enough time getting into intense depth on the actual user experience. This generally results in a frantic numbers chase that does not end in a great product."
Frictionless feedback essential to Consumerized Enterprize Apps…
At Google, “We don’t have a two year plan. We have a next week and a next quarter plan. Most of our successful products were built by small teams reacting quickly.” Indeed, awhile ago I asked Android head Andy Rubin what Android would look like in three years. He said there was no way to know;…
“The consumerization of IT renders the “enterprise-only” pivot null and void. In this new world, Google and Apple wage an ecosystem war: devices + apps + distribution. Add marketing, if you want, but Word Of Mouth is still more potent than ad dollars. Or merely reinforces it.”
Here’s what’s scary: You could easily fit all Facebook, Twitter, Groupon, Zynga, LinkedIn employees together into the 20,000 seats in Madison Square Garden. They just don’t employ a lot of people, relative to their valuations.
Ever wanted a blog that was made for coders? This one is built from the ground up with the needs of a modern programmer-who-happens-to-be-a-blogger-too in mind. Wheat is the new engine to howtonode.org released today.
If you’ve been itching to learn node, now is a great time. The API is stabilizing and now with a tool like wheat you can blog about your experiences.
If you don’t already have node.js, either compile by hand or use nvm (Node Version Manager)
> cd Code/howtonode.org
Starting wheat server using git repo at /Users/tim/Code/howtonode.org
node-router server instance at http://127.0.0.1:8080/
Articles are written in markdown so there is no messing with clunky WYSIWYG editors. Also as you can see from the tree, code samples are stored in their own files. This means you can use your favorite code editor to write up your code snippets, and you can test them for syntax errors or even check the output.
If the snippet is written in node.js, you can tell the engine to execute it and show the output inline in the article like in the What is this article. Here is some sample markdown:
This is an example of global scope:
This is an example of local scope:
Note that I was able to access `Person.name` and `Person.age` from
The * on the end means to execute the script. The hashtag means to show just that part of the file. This way you can explain a large file bit by bit, but keep it all in one functional place.
There is so much more the engine does, but this is just a sampling. There is live graphviz rendering, super scalable caching for production use on a bare git repo, RSS feed, etc…