dr_rezzy

I think you guys are talking on different tracks here. jsprinkles brings up a genuine concern. However, he goes ahead and calls your skill unmatched in your domain and I respect that. Honestly, that was a bit of a shocker but I will accept this. Its one thing to be cagey with details and unscientific with your "forum" approach. But it bothers me that you go ahead and underestimate and even disrespect your audience. I can only come to the conclusion that you dont understand. Thats it, this is a very fitting response.

Why did mongodb drop 30 docs from its index? Did PG drop any? Does this not matter?

This is my biggest concern. This means that whenever you want to run a simple HTTP server, you need a signed certificate. Well, thats a huge hassle. So its likely shortcuts will be adopted to make HTTPS adoption more practical for everyday usage. This could lead to the weakening of the entire trust based certificate system due to the demand/pressure of scale. Ok, so now you strengthen the trust system and inadvertently untrust large parts of the unregulated internet. Great, you have just implemented tiered internet. Those who qualify for the trust based system get rewarded with access to HTTP(S) 2.0, those who do not are condemned to HTTP 1.X. Congrats guys, great foresight.

For spamming this is a gold mine.

Ditto, this site returns an error everytime I try and hit it.

Spot on. However, I cant think of a single achievement which was not created from unfiltered group brainstorming. Then again, I do things differently.

Its clear, closures actually solve the problem of random array access in high level languages. You are either after 1 value or all of them. These are 2 very easily optimized access patterns. Out of bounds array access isn't a constant threat.

Edit: I consider loop based programming my most essential coding pattern.

Honestly, these are quite possibly some of the most incoherent arguments I have ever seen:

"At least, I'm assuming that he's including these companies in his false-nostalgia..." - great assumption

"Where "major differences" would have been" - You seem to be reinforcing the authors point here.

"This has nothing to do with why Facebook didn't want to go public." - You totally missed the authors point here.

"He spends a couple of paragraphs decrying liquidity in markets, and then calls this a bad thing." -You might want to check the definition of decrying.

I like. Word splitting is very interesting. Today, 2012, I would be hard pressed to provide a reason to use this technique. Splitting an index is a classic complexity/resource trade off (your index has a very predictable compact footprint). Again, today, memory is cheap, wide, uniform, and predictable. Indexes are now cheap and highly specialized. Complexity can be reduced for simplicity. Index specialization now becomes natural. My point here is that this solves a class of very expensive searches with ease, leading wildcard searches et al. Also, couldnt really tell from your code (you may be doing this), but reverse your trigrams in your generated query. If ordered properly, your search will be a lot more efficient.

SPDY is here to increase efficiency between browser and server (this is sometimes called scaling). 'Dynamic network typologies' as presented is moving the network routing stack to a software CPU. Not sure I would bridge these two technologies together to solve my 'interesting worker topology patterns'. This is classic top down design.

Nothing. You are correct in missing an important part of this discussion.

or live in locations with better access to these resources

You arent seeing the bigger picture here. If you choose this level of efficiency, after getting dropped off at work, 'your car' will simply locate the next closest customer. If you want to spend the resources on your own private car or a more available one, more power to you.

I didnt really pay much attention to the points regarding commenting style because it seemed like the real point here was the direction java was going in the late 2000's (or more importantly the ideas being sold). In this context, this posting comes together as very insightful and actually resonates with a lot of truth.

I like the self awareness here but I kind of cringed at some of the points made by the author. LMAX is definitely a counter to the one size/approach/design/trend fits all thinking in software. I guess its true when they say execution is everything. In the end, a great example of a well executed innovative design.

So you are saying that adhering to memory bounds and limits (and possibly SLAs) should be ignored in favor of having your software crash because its easier? Sure, I can see it as a possible strategy in some cases. But to go ahead and cite this as a rule is kind of short sighted and a disservice to people who put thought into their memory allocation strategies.

Great write up. You really nail the essence of a true data driven approach (DDA) to solving problems. Simplification of the data world view can lead to great things. The key to your batch computation example is proper data modeling IMO. This leads to flexibility which is crucial for a design to be successful. I feel people will stumble with the content of this post because of the lack of proper understanding of DDA.

Zeke was my theory and algorithms prof in college. Kind of hard to wrap your head around these sort of problems.

That would only be a risk if we were talking about a typical high school multiple choice test. I would think that a cheater would be filtered out by this point in their career (this point being applying to a high tech company). However, collaborating on a solution is not necessarily a bad thing. I think the goal here is to find candidates which can deliver unique, valuable, and insightful problem solving skills. To go ahead and bottle that process up into a pre determined steps or a 1 hour drill doesnt serve your goals very well. Who knows, maybe these guys have a recipe which works for them. From my own experiences, I would disagree.

For me, this blog post represents a step backwards. They open up saying that the 1 hour interview provides absolutely no indication of how well a prospective candidate will perform. Hopefully most people will agree here. Then they go ahead and state that their staple interview will be an on the spot problem solving screening and then list the steps the expect the candidate to take in solving said problem. What does this say about their own problem solving skills? I will leave this upto the reader. Let me throw an alternative out. Why don't you give a prospective candidate a written test/problem and give them as much time as they want, using methods and environments they are comfortable with, and have them return to you a solution of their choosing. Wouldn't this best capture how a person breaks down a problem, solves it, and finally presents a solution? Leave the onsite to better understand someones personality, likableness, and workability. Maybe even ask them to walk you thru how they came up with the solution and how they worked the problem. The options here are plentiful.

I thought this was very well written and clear. These authors bring up a very valid point. Not really sure if the web can reinvent itself. Java applets and Flash both failed along the same lines. Maybe the web (and HTTP) is only good for relaying information and rich experiences will always be native. It doesn't have to be that way, it just is.

What century?

Is it me or is it a growing trend that 'academic' papers are omitting their publish date. Its frustrating to read a paper without this context.

This makes me really excited about the future of the 'desktop' ( => tablet). Microsoft has really nailed it in terms of user experience and performance. This is a good example of out innovating the competition and no other company is better suited to execute on this than Microsoft.

Right, the justification here is a bit blurry. The framework they present is pretty much J2EE redux. If you are going to take this angle, stick with Tomcat and its huge enterprise base. Unfortunately, this is far from reinventing Java for the web.

Lots of parallels here: http://www.weatherlabs.com/2011/08/device-detection.html

yup... Autonomy is a huge name in the enterprise biz. This blogger got it completely wrong when he said they are an SAP rival. Autonomy is Oracle's biggest threat now and will likely start making inroads on its biz.

Ive used idol very extensively for approx 5 years. Its like combining oracle db with google search and then adding language analytics. Basically its a very advanced db (these were the first guys to really get nosql into the enterprise). You dont query the db, you search it. Keyview is also a nice addition to the IDOL stack.