- a reality show with gay men and one straight man.
- for april fool's day, HN karma arrows are inverted.
- frozen food with QR code of recipe (how long to microwave at what level), and microwaves that can read those and automatically cook.
- google gives you a badge for searching a term for the first time.
- social sharing aspect of cool searches you do. badges and levels.
- online search master consultancy that searches you stuff.
- Ask HN, Show HN, .. etc get different CSS color, font.
- news site where everything is paid. but you can earn their virtual currency by joining, visiting, watching ads... etc.
- mongodb-esque json crap db with joins and relationships and graph search.
- edge side include for json elements.
- can make a voice note on longitude and latitude so when others are around, they can hear the note.
- jot melody online or in a mobile app.
- jot lyrics.
- $1 online service where professional musicians or computers play your jotted melody (10 second max, probably with a good arrangement). melody rendering service.
- personal wayback machine. click a bookmarklet, the page is captured and saved for your personal index, search, retrieval. of course you can modify/annotate the retrieved page and possibly republish.
- http://www.json-generator.com/ but contents come from crawling actual web content (maybe from google).
- gravatar but using short video (gfycat, vine...).
- responsive book format (technical books with code listing actually render well on kindle..).
- responsive content web site. given where you are, when it is, who you are, what are capabilities of your device... etc provides you different contents. for example, at nights, gives you more adult pics. during work hours, gives you more work-related contents.
- dating web site where you publish dates afterwards, including location, time, budget.... tells you who gets the most expensive free meal. who spends the most money...
- search engine that only indexes disallowed resources.
- "RESTful" api with millions of verbs (not only GET, POST, ...). makes linguistic analysis of the verbs and the requested resources. does some magic.
- FedEx store right at security checkpoint. Toothpastes are returned to your home via trustworthy FedEx.
- mentorship service / travel mate site where you can find other mentors , entreprenuers to share ideas, pair coding brogrammers... etc on plane.
- submarine-spaceship that is actually a sumbarine and then it files all the way into the mars. a travel package that includes underwater, outer space,... etc.
- a web page that when requested by google bot, submits itself to google for crawl.
meh, types give you enough documentation. once you play around with examples on README, reading type annotations (that are actually written manually as a form of documentation) of functions in https://github.com/bitemyapp/bloodhound/blob/master/Database... make sense.
examples could be moved over into modules.. but I much much prefer to have examples in one place that could be read like a gentle introduction and walkthrough of the library. Said that, additional module and function documentation could be useful, too. But not at all if the library maintainer just fills stuff in to generate fat haddock. Again, type annotation says much.
And, you're welcome to contribute documentation to the library.
You must write tests first, but not the kind of tests TDD people advertise to write, such as unittest.
Instead, you should write short specifications on paper, whiteboard, or as code comments. You can even use automated proof system to verify what you're trying to implement is sane.
These specification-like tests will make you think upfront. They are not tided to any language/library/implementations. I find them much valuable than other automated tests TDD promotes.
I do think automated tests are valuable, too. It's awesome to have a program that can test your program and only your program by being tightly coupled with the program being tested. It runs your program in different ways using test doubles. Generates beautiful reports with coverage analysis. It's indispensable. But I don't think you must write them before you implement your program. And, you don't have to be driven by automated tests you wrote beforehand. If you must be driven by something, get driven by rich type system, automated proof assistants, whiteboards, discussions with coworkers.. etc.
mongodb is the best database in the whole wide world at the moment. I encourage everyone to jump in mongodb for agile web scale development with full big data capability.
