Though a cool artifact, it seems like the essence of something like this comes from interaction with the others using the service.
There's a really interesting podcast segment[1] about the Preserving Digital Worlds[2] project which tries to answer some of the questions about how to best document / preserve something who's value comes from the experiences users share with each other
This is great. Outrage over government surveillance seems to be fading among the "mainstream", but this seems like just the thing that is accessible enough to get the general public on board.
What's the best way we can contribute if we can't be there in person for the rally?
"When I write a Cucumber feature, I have to write the Gherkin that describes the acceptance criteria, and the Ruby code that implements the step definitions."
As someone who recently started using cucumber, this was definitely a frustration at first. But after a couple weeks of writing step definitions, and focusing on making them reusable (using some of the tips here: http://coryschires.com/ten-tips-for-writing-better-cucumber-... ), I ended up with a pretty good bank of general steps that I could cobble together into new features without much modification. The result was something much more readable and reusable than if I wasn't using Gherkin on top of the step definitions.
Exec isn't the best designed website I've ever seen, but it's functional and presentable. There are plenty of startups / small companies that can't afford the money required for a senior level designer but would be happy to hire someone who could do even "design-school-freshman-quality stuff" for a reasonable price if it allowed them to present their idea / business in a way they couldn't on their own.
So if the measure of being a "professional designer" is someone who is paid to do design work, I think this is fine advice. A designer gets better with practice and real world work. This seems like a good starting point.
For anyone using PhantomJS I'd recommend checking out CasperJS (http://casperjs.org/) . It adds some nice features to PhantomJS and takes out a lot of the pain points
I'd give nzb.su a try. I started using them a few weeks ago as an auxiliary when I was having issues with nzbmatrix.
In my short few weeks of using it, the API seems better than nzbmatrix, but the community / comments on files is near nonexistent. If you're only looking for something to hook up to sickbeard / couchpotato though, it should do the job just fine.
There's a really interesting podcast segment[1] about the Preserving Digital Worlds[2] project which tries to answer some of the questions about how to best document / preserve something who's value comes from the experiences users share with each other
[1]https://soundcloud.com/roman-mars/99-invisible-13x-game-over [2]http://pvw.illinois.edu/pvw2/