Octobot - A Low-Latency, Highly Parallel Distributed Task Queue Worker

Re:Octobot - A Low-Latency, Highly Parallel Distributed Task... by Sukotto on Monday September 20, 2010 @02:03PM (#1709832)

This is a good case-study of what to do when building a home page for your project.

1) State what your project is about using language that a reasonably savvy (technology-wise) user can understand, even if unfamiliar with the problem domain. (this site would be better if they linked on "message queue" for those people that don't know what that is.)

2) Eye-catching call to action icons

3) Brief list of most important features

4) Brief high-level view

5) Brief low-level view

6) Some clean and minimalist stats on why you might want to use it

7) Easy to understand links to more info.

I don't know if I will ever need this product... but I'm bookmarking it anyway as an outstanding example of how to introduce people to it. (Except for the swear word. The word "Fucking" is really out of place)

Nice job guys.

[ Parent | on HN ]

Re:Octobot - A Low-Latency, Highly Parallel Distributed Task... by superjared on Monday September 20, 2010 @02:18PM (#1709907)

"Portland Fucking Oregon" is definitely a PDX thing. "We're too cool to not swear" or something. I dig it, but then I live here.

[ Parent | on HN ]

Re:Octobot - A Low-Latency, Highly Parallel Distributed Task... by JoachimSchipper on Tuesday September 21, 2010 @04:12AM (#1711876)

I thought their list of adjectives was too long; half of them boiled down to "performant", too, which is not too useful (of course you're trying to be performant; calling out throughput or latency specifically is useful because it helps people evaluate your work for their needs, but having both gives very little information...)

[ Parent | on HN ]