748 karma · joined September 2, 2010
http://www.recawl.com - "A search engine for your web history"
http://www.webalertpro.com - "Competitive website content monitoring"
http://www.bookmarkerpro.com - "Search & monitor your bookmarks"
joel_at_halbert_dot_it
Who's your target market for this product? The styling on the homepage is pretty tech/minimal, but if you're going after the home user maybe something more light-hearted would be appropriate? I can see people using the videos to create custom Christmas or Birthday messages, but style-wise that market probably respond better to something more like: http://www.moonpig.com/uk/
Broad differences in storage models:
* Column Oriented Storage (e.g. HBase)
* Document Store (e.g. CouchDB, MongoDB)
* Key-Value (e.g. BerkeleyDB, TokyoCabinet, REDIS)
* Graph DB (Neo4J)
Furthermore each will have their own consistency, replication & availability models, as well as read/write optimisations.
Before choosing one you need to ensure it is adapted to your usage pattern. Here are some links that go into more detail:
A visual comparison, comparing trade-offs of each type of nosql db: http://blog.nahurst.com/visual-guide-to-nosql-systems
Article on appropriate use-cases for each type of nosql: http://blog.heroku.com/archives/2010/7/20/nosql/
NoSQL - the 'definitive guide' (apparently): http://nosql-berlinbuzzwords2010.heroku.com/#1
Further resources: http://nosql-database.org/
And here's a link on data from the top of HN today: http://www.junauza.com/2010/11/free-data-mining-software.htm...
Seems like a bit of a waste getting the HN community to review some colours and fonts though. If you told us a little more about the idea maybe we could give you feedback on that instead? I mean, the coming soon page is pretty insignificant with respects to the idea itself, no?
It's unlikely that anyone would use a developer that they didn't know personally, without a formal contract, for this type of work though.
On the other hand, if you're asking for a vanilla e-commerce site then it's less relevant, the code the developer uses may come from open source libraries, or it may be his that he his re-using, but it probably matters little to you as it's the content on the site not the code behind it that you really care about.
You will always own the copyright on the website, including the design artefacts, unless you are explicitly licensing them.
Ideally you would also somehow get the developer to verify that all the code they are using has a valid licence, as ultimately you're probably liable for infringement. Again, I guess this is trickier to do in a web based developer market, but probably not going to be an issue for a vanilla job like an e-commerce site or marketplace.
Sources:
UK Budget: http://www.guardian.co.uk/news/datablog/2010/may/17/uk-publi...
EU Contributions: http://news.bbc.co.uk/1/hi/8036096.stm
Afraid I don't have figures for US.
Yes, they are, but it's a political hot potato, arguably without mandate, and I doubt that it's on the scale of national regional development funds.
Don't get me wrong, I am pro Europe, but I think politicians have done an abysmal job of explaining the project to voters (esp in the UK).
True, but, there is a policial union of states in the US that doesn't exist in the EU. The EU is a monetary union without a political union, this means that it's politically unpalatable to explicitly redistribute tax money from the relatively rich to poor regions (Germany/France to Greece/Portugal) in the same way as Washington or London might to W.Virginia or Newcastle.
They are well attended, have guest speakers, and best of all - free beer ;-)
However, there are other reasons that deter people from launching start-ups in the UK, 1) it's expensive - London is very expensive, general living costs are higher than the US 2) The City is a disproportionately large draw for UK graduates, finance is a larger percent of the economy, compared to say the US.
* The need for speed, at every level of the architecture (network, tcp/ip, hardware, app)
* Reducing order (send/ack) round-trip times, this generally means putting your servers in a data cetre as close to the exchange as possible (co-located, if the exchange offers it). If your trading across multiple exchanges simultaneously it gets trickier.
* Sourcing market data - can you source direct from the exchange, rather than through a 3rd party like Reuters? Again, it comes down to how fast you can re-act to the market.
* Back-testing - you need historical data to test a model, then you need a way of testing the model - what are you going to test against? How are you going to simulate the exchange?
* Expense - it's expensive - market data, co-location etc etc all costs, as others suggested. HFT is generally short term positions, with some arbitrage strategies holding positions for less than a few milliseconds. A medium term (intra-day) type strategy requires less intensive (expensive) technology as your not trading to capture market prices that might only be extant for a few milliseconds.