robmil's comments

The fine has both to be punitive and to serve as a deterrent to others — so to be punitive, it has to be relative to the income of the person/company being fined, and to be a deterrent it also needs to be severe. I don't see any reason it has to be similar to the direct cost of the damage caused.

In the UK, we call it "cut and shut": http://www.autotrader.co.uk/safety_and_security/cut_and_shut...

I'm not sure what this sub-Breivik material is doing on HN, but there we go.

SCSS actually makes this easier, given that you can have partials; it makes it easy to separate out layout and visual style and then combine them into a compressed stylesheet automatically.

It's happened quite a lot in the last few years, e.g. following the collapse of a black football player, Fabrice Muamba.[1]

You have to consider the different context at play here; the UK has never had a history of "fundamentalist" (for want of a better word) free speech like there is in the US. There are plenty of laws on the books, from sending malicious communications to inciting racial hatred, that prevent speech that would be entirely legal in the US.

I think that's something that's reflected (either a cause or an effect, I'm not sure which) in public opinion, too; there's certainly no widespread outcry here at these types of arrest. The only recent case I can think of where the ruling was against free speech and where public opinion was significantly against the ruling was the Robin Hood Airport tweet, where someone tweeted an obviously incredible threat to blow up an airport.[2]

[1]: http://www.guardian.co.uk/uk/2012/mar/27/student-jailed-fabr...

[2]: http://www.bbc.co.uk/news/uk-england-19009344

Also available is the brilliant underscore-cli[1], which brings the functional programming of _.js to the command line.

There's an examples page, if you're struggling to see how it might be useful[2], but I find myself using 'extract', 'find', and 'pluck' on a daily basis.

[1]: https://github.com/ddopson/underscore-cli

[2]: https://github.com/ddopson/underscore-cli/blob/master/Exampl...

Is there any way to get around the fact that adding a new machine involves adding N*2 remotes? (That is, one remote on each of the current machines to represent the new one; and then on the new machine, one remote for each existing machine). This seems like it would be the sticking point with Git annex.

I was hoping this was going to be something where the files themselves were distributed so that they didn't take up space on everyone's machines, a la MogileFS[1], but alas.

This is always a point of pain for us: in our studios we work from a central file server, so our shiny iMacs with their 1TB drives all have about 90% capacity on them — but we don't have any easy way to pool all that extra capacity and use it even as overflow for our central fileserver.

The search continues...

[1]: https://code.google.com/p/mogilefs/

For anyone who's after a book: I've found Dafydd Stuttard and Marcus Pinto's "The Web Application Hacker's Handbook" to be invaluable.

I've long since abandoned trying to do programming tests when interviewing coders. Instead, I work through a problem with them in a sort of socratic method; I play devil's advocate to them while they flesh out how they'd approach the problem.

It's far more illuminating, and a far better reflection of their worth as a candidate, than their ability to go off into a room somewhere and work through a problem alone. I'm much more interested in someone who thinks well than who codes well (since the latter can easily be trained).

We started off with our own toolkit for purging domains after deploys: https://github.com/robmiller/Varnish-Toolkit

But yeah, it just got a bit painful after a while.

We eventually abandoned Varnish because the purging was too far from our application logic. nginx serves static content just as fast as Varnish does, and so getting our application to write static HTML files that were redirected to via nginx was just as quick as Varnish but easier to purge when needed.

For a lot of sites, either using ESIs or including dynamic content via AJAX is a fairly simple solution that still leaves you with the benefits of caching.

I realise this is snark about the article going down, but it's actually a good point too. Not much point in optimising the client side if all your dynamic requests take a second for the server to process.

Oh, absolutely. Web workers are awesome and hopefully the future, but it seems a bit disingenuous not to mention the huge caveat that currently prevents their being adopted in a more widespread way.

Unfortunately they're not supported in IE9 or below, which this article oddly fails to mention. So a more accurate title might be "make your UI more responsive for ~60% of your users with HTML5 web workers".

For anyone looking to learn more about Chechnya regardless of whether it's linked to these attacks, I'd highly recommend Sebastian Smith's "Allah's Mountains: The Battle for Chechnya".

For wider reading on the region, I thoroughly enjoyed Oliver Bollough's "Let Our Fame Be Great: Journeys Among the Defiant People of the Caucasus", a nice blend of travelogue and history from the journalist who was Reuters' correspondent in the caucasus throughout the late 90s and early 2000s.

Not that I'd necessarily agree with it, but I think you're missing his overall point there: he's arguing that those things are time savers, but only for tasks within the domain they were designed to tackle, whereas macros allow more general and more automated solutions, saving time across all domains.

For those about to bemoan the breaking of things like Google Analytics: this patch only blocks third party cookies from domains that the user has never visited before. Since 99% of your visitors will have visited google.com, your Analytics should continue to function even after this update.

Some tips:

You can track and checkout a remote branch in just one command:

    git checkout -t origin/foo

If someone's working on a topic branch themselves, it might be better to rebase master rather than merging it:

    git checkout foo
    git rebase master