johnm

'When Rinpoche told my wife that he was being billed as “the happiest man in the world,” he laughed as though that were the funniest joke he’d ever heard.'

Well, at least he gets it.

It's not that simplistic. It's important to go after a mix of companies (of different sizes, strength) so that you can set precedence, get quick settlements (i.e., funding to help playing chicken with the deep pockets), etc.

Um, er, the trolls go after the small fry, too.

Use versions like /v1/ .

If there's no version... * If there request is plain html then deliver a human readable documentation page (that still has hyperlinks for discoverability. * If the request is asking for whatever your application type is, redirect to the current stable version.

If there's an older version requested: * If it's no big whup, keep the old version usable. Sometimes I do this by just keeping the old version of the resource code around, sometimes by updating it to translate between the old version and the latest stable version. * If you want to kill an old version, think about what appropriate in terms of 300 Multiple Choices, 301 Moved Permanently, or 410 Gone relative to your users.

You end up with a "culture" whether or not you worry about it. Of course, what you end up with if you don't worry about it might not help you actually succeed.

Indeed. Most people use "complex" when they really mean "complicated".

What are the threat models that you care about (in some sort of rough rank order)?

So much good advice that's high-level so here's a real simple one...

Trim your nails.

Less than you want and more than you think.

markmail, krugle, imdb

Nuture nature.

This sounds perfect for a native XML "database". Check out e.g., MarkLogic Server. That's what we built http://markmail.org/ on top of.

Convenient how there's no memory architecture & bandwidth numbers. :-(

So much better than so much of the discussion around Tornado, that's for sure.

Definitely would like to see two more takes: * long-poll setup (lots of idle connections with sporadic bursty activity) * thundering herd (max sustainable active connections)

Yes, most of the full talks are being recorded and will be posted.

Yes, they've said that everything is an object. But, the whole question of interop with Java is still in flux.

One goal of the summit is for implementors (of languages and/or runtimes) to have a chance to talk through issues so it fits in with the conference just fine. The hype in the article is the problem.

Article fail. It's not "delivered" -- it's a language in the process of being designed.

Indeed. These types of interviews are much more about finding people who "think outside the box... just like me!" than about finding people who can do the job.

The MarkLogic server is a native XML database. It's designed and written from the ground up to do XML. That's why it's so much better/faster than the competition.

Storage-wise, it's often the case that the MLS DB for a project is actually the same size or smaller than the original data even after you add all of the indexes, etc.

Performance-wise, the MarkMail.org site is running a 4 node cluster. The cluster is totally managed by the ML server and is fully transactional across the cluster.

Feature-wise, the ML server provides all of the underlying goodies for doing not only the various text searches but also the slick faceted search.

Thanks for the support.

MarkMail is indeed built on top of the MarkLogic native XML database and it works very well.

If anyone is interested, I already wrote up a bunch of my reactions to the article (good and bad) in tweets.

The v1.4.x series is stable but little except bug fixes because work is nominally focused on...

The v1.5.x is more or less a rewrite that has languished for a couple of years with little progress.

Bigger facilities than that pretty junior college on the peninsula. :-)

Better to use e.g., vertical or left-justified labeling and use the in-field support to put in example values.

Wow! That's frightening.

Without that you'll never become great.

True Passionate Curiousity http://cobaltsaffron.com/newsletter/CobaltSaffron-01-us.pdf

Yeah, the aristocratic, "geek machismo" model of hiring conflates (weak) correlation with causation.

For me it's an anti-pattern that shows that such people lack a critical bit of intelligence and vision.

It's also a modern example of the Maginot Line fallacy.

Scala is to Java as C++ is to C.

SubEthaEdit

"Solve world hunger: Xerox donuts."