Reverse cache like there’s no tomorrow. It’s 2010, and you’d expect people who still think Ruby can’t scale to be invested in that belief of theirs. I’d rather read about the One True tab spacing then yet-another-article-about-scalbility-myths. In spite of that, the second part of this article is excellent, and whipping out a minimal reverse caching proxy to yield 10x performance improvement is smart. And you don’t have to use Ruby:
The end result is a caching reverse proxy with very few tuning knobs, and behavior that’s not quite HTTP 1.1 correct, but that is very fast, stable, and hackable. It’s probably not actually as fast as it could be, since I piggy backed the implementation onto something that’s doing more than I really need, but it’s good enough
RESTfully yours. Part of adding geo-locations to Yaketee is finding a database of existing spots we can reuse. A database we can actually use – pro tip: read the terms of service fully before investing in anything. Ideally, a database we’ll enjoy and learning something from using. Enter the Gowalla API. Like everything else they do it’s smart, simple and meticulous. If you want to learn how to do a RESTful JSON interface right, do check it out.
Matter of perspective. It’s been too long to remember, but it feels right. Dustin Sallings (via Aristotle Pagaltzis):
git doesn’t have a high learning curve. svn has a high unlearning curve. observe the difference in those familiar with neither.
Be specific. Follow this good advice (<- walking the walk):
The one thing I’ve ever found truly important in issue trackers is that people who submit tickets start the names with verbs. I’m looking at your screenshots and seeing “better variable naming” and crying just a little bit inside .We’ve got a rule of thumb inside Stamen that issue names must read like imperatives: “improve variable names”, “delete blah functionality”, “fix broken jimmy-jammers”, etc. Nothing focuses the mind of the reporter like being asked to specify what exactly they’d like to see done, and it’s much easier for a developer to scan a list with actual tasks right in the sentence construction.
Salt your coffee. No, seriously (I have not yet tried it myself, just passing along):
The first thing that comes to mind is that salt reduces bitterness. And to be more precise it is the sodium ion (Na+) that interferes with the transduction mechanism of bitter tas