http://www.archive.org/stream/lifeofsirernests00milluoft#pag...
1,906 karma · joined June 21, 2007
http://www.archive.org/stream/lifeofsirernests00milluoft#pag...
Also unless you like clicking through 11 screens, the "print" version is better: http://www.itworld.com/print/84390
http://news.ycombinator.com/item?id=654842
http://news.ycombinator.com/item?id=223972
http://apps.ycombinator.com/item?id=147614
http://news.ycombinator.com/item?id=107221
http://news.ycombinator.com/item?id=81707
Perhaps there's less need for it since a similar module (multiprocessing) is now part of the python standard library.
Make something people want. If you're young then you have plenty of time to succeed by doing something worthwhile instead of ultimately impoverishing everyone through trickery.
* MongoDB and Tokyo Tyrant are useful now. CouchDB has promise, but is too slow currently.
* Non-relational databases have shown their worth at larger sites when used cleverly.
* Non-relational databases will continue to improve performance, stability & features.
* Relational databases are still a great choice: fast, powerful and proven. With caching, denormalization, rework (e.g. Drizzle) & better replication, they will continue to be competitive.
Regarding bicycles for the visually impaired, I'd probably suggest a tandem model.
Does This Actually Work? · Not quite, at the moment. I mean, it works fine for the first 50 million lines or so of the big dataset’s quarter-billion, keeping my eight-core 32-thread SPARC T2000 maxed, and I mean smokin’, you can see the 50M blocks that Paralines is reading go by pop-pop-pop. But then it hits its heap limit and descends into garbage-collection hell and thrashes its way to a miserable single-threaded standstill.
I'm hoping he will eventually arrive at a clean solution that can handle the full 43GB or so of input.
1- http://www.tbray.org/ongoing/When/200x/2009/11/11/Clojure-Re...
Straightforward error correction techniques would help identify and compensate for minor errors and simple adding machine style recipt printers incorporating such logic could be made available within voting booths. Voters who want a recipt would just type the revealed code into the printer.
It could be particularly useful for celebrities, public figures, political protesters, parents, teenagers or anyone who might be otherwise embarrassed (or worse) should their email logs be revealed to an inappropriate social group or the general public.
My former company got along pretty well with our own mix of Trac/SVN for code and engineering issues, Request Tracker for trouble tickets, ScrumWorks for iteration management and MediaWiki for all other stuff.
This should be fixed.
While I agree with Mr. Dewalt's basic message, identifying integrity constraints as something a "lean startup" shouldn't worry about for a production application containing his customers data undermines his implicit claim of data management competency - experienced database developers know how to design and organize their schema so that details like dbms-specific foreign key implementation are trivial. When foreign keys cause you serious pain relative to your other data management problems it means you're doing something wrong.
What he didn't learn about his customers in the hour at most it should have taken him to get the keys right (thus helping ensure his customers data is not corrupted by application, framework or provider infrastructure bugs) pales in comparison to the lesson he will learn if their data is silently corrupted.
I would suggest looking at RT: Request Tracker. It has excellent support for creating and managing tickets with email.
1- http://en.wikipedia.org/wiki/Where_Mathematics_Comes_From
2- http://books.google.com/books?id=YXv6SEjTNKsC&pg=PA432...
I may be in the minority but I would have liked the opportunity to use the same filesystem on my OSX laptop that I do on my database server.
While in many cases it's trivial, I think it would also make sense for NoSQL's to add some kind of way to support common INSERT or COPY FROM .csv file commands. That would make it easy for organizations with existing SQL databases to see if a NoSQL could better solve some of their needs.
1- See http://databeta.wordpress.com/2009/05/14/bigdata-node-densit...