1,701 karma · joined December 9, 2008
http://news.ycombinator.com/item?id=436390
I demand you recant, you evil genius, you. ;-)
The book should be read as follows (not listed in chapter order):
1) how to build a business that scales in output in a more than linear proportion to the time you put into it. [and how to avoid nonlucrative or time-intensive businesses].
2) suggestions of how to spend your time and money in a way that makes the most of both, in terms of quality [assumes you enjoy travel]
3) various useful companies and resources, some specific to US-based businesses that need to drop-ship physical goods
4) stupid chapter on how to skip out on work if you're an employee [with potentially useful tips on how NOT to do it]
5) various inspiration to get off your duff and do things (both in terms of starting your own business, and in traveling and doing things you've always wanted to).
The most useful pieces are (1) and (5), followed by (2) and (3) if they apply to you. (4) is the only part that I'd consider farcical, but the rest of the book was interesting enough that I don't sit around wishing for my $20 back.
There seems to be a decent contingent of people who hate the book, but I'm more interested in hearing from people who actually tried out the recommendations in the book and failed, especially if they're willing to go into the details of what went wrong.
2. Incorporate (probably as an LLC)
3. Sell copies of said app to people in exchange for money.
4. Relax more.
5. Exercise more.
6. Visit more places and people.
7. If steps 1-3 work, buy Wil Shipley a drink!
8. Spend next xmas in Munich.
(And if you've got a messed-up family situation, money can put some serious (geographical) distance between you. :)
It wasn't till I was ten or eleven that a friend announced to me that he had found a program on his computer that would allow us to make video games (qbasic).
I think the thing I missed out on most is having a few more years of wildly creative programming without being encumbered by any ideas about the right way to program.
Same to you, buddy!
Hell, they're even important for the aspiring web developer: being intimately aware of the flow of state will make any centralized, stateful bottlenecks in your application painfully obvious.
1) Rendering an undirected graph via graphviz's neato tool.
2) Rendering to svg, which might let graphviz not have to keep as much rendering information in memory at any one time.
3) Asking about it on the grapviz-interest mailing list. https://mailman.research.att.com/mailman/listinfo/graphviz-i...
Write a crawler that examines all local links, and builds a graph (it needn't be anything fancy; a collection of nodes and edges is enough, but you'll have to detect cycles when building the graph), and then print it out in graphviz .dot language.
Then you can feed it into neato [either through a command-line pipe, or construct one using Python's subprocess module], et voilà, instant pagemap! :)
You can also use some of the rendering modes and scrape position data for the rendered nodes, if you want to generate a clickable imagemap.
I will trademark all variants of "LOL", and collect every time he tries to...