virulent

Haha, except AWS doesn't lock your account randomly or stop droplets for benign abuse reports.

Also, OP required Redshift. DO does not offer that.

I have a similar feeling. I don't really like GOPATH, but I'm trying to come to terms with it.

Your Go "project" goes in $GOPATH/src, i.e. your git repo would be in $GOPATH/src/github.com/user/repo

If you have your main pkg in $REPO/service, then you can build like so: go build github.com/user/repo/service (this can be ran from anywhere as it uses $GOPATH)

If you need to add a dependency, use: go get github.com/.... and go get will add it to $GOPATH/src/ which you can then import.

not anymore :(

This is pretty nice. I was curious how the spread was like for multiple links: http://www.rndmlnk.com/counts/testredirect2

side note, it was fun to see what the max redirects is in Chrome with the redirect loop.

I agree that A is really simple. I was pretty surprised to see that as a problem.

Was that 3-4 mins from first starting to read it to finishing a solution? If so then great, but personally I would've taken 10-15 minutes because I'd be carefully reading it first and wondering why it sounds so simple.

Stanford's is pretty nice: http://stanford.edu/~liszt90/acm/ (notebook files). There's also one from a Korean university there.

Wow that's crazy, no doubt it must have been really demotivating.. I was in the Northeast NA regional and MIT (#11 in the frozen scoreboard) only solved 6/8 of the problems at regionals. Most of us only solved 1-3.

I participated in ACM-ICPC regionals back in November and it was a lot of fun. I definitely recommend it to anyone that has the chance to go to preliminaries next year.

The time limits are quite brutal for some of the problems @ finals, most of them I'd never have a proper optimal solution for.

Also, the fact that Peking understood and solved A in just 5 minutes is crazy. Sure, I could at least do A, but they practice enormously just for these.

> A crossing in central London had programmed intervals for red and green lights, for example. Pushing the button would only impact the length of these intervals between midnight and 7am.

This is the same where I live. The crossing buttons do nothing during the day (walk symbols still come on for the same length of time), but at night they need to be used. I don't push it during the day, but of course most people still do :-)

It seems to depend on reactivity[1], hence it doesn't block.

Here's an example: https://jsfiddle.net/k61y5sLo/2/

    Pre-callback
    Evaluating getCallbackText()
    Post-callback
    callbackTest => cb("Alice")
    Evaluating getCallbackText()
    callbackTest => cb("Bob")
    Evaluating getCallbackText()
    Callback returned: Alice Bob

https://github.com/aldonline/reactivity

I enjoyed the linked post[1] at the bottom more than the post itself.

    #define while(x) if(x)

Too bad April 1 is already gone, I'm kind of tempted to try and sneak that in.

[1] http://www.cs.earlham.edu/~skylar/humor/Unix/c.language.pran...

Maybe I use Word wrong, but I always hated how it was really easy to screw up formatting and spacing by accident. As well, changing some line spacing consistently across the document was a pain (e.g. list spacing).

With LaTeX I find I make a lot less accidental mistakes. If something goes wrong, I know exactly what caused it (just look at my changes!)

Ports inside a container aren't exposed publicly unless explicitly done.

Container linking lets containers connect to each other without exposing ports via docker.

The "linking" is exposed to the container via an /etc/hosts entry, so e.g. --link test-db:db adds "a.b.c.d db" to /etc/hosts which can be used by anything that needs it.

As mentioned by jon-wood, the simple linking approach only works with containers on the same machine unfortunately.

Why is this an article anyway? They use matching algorithms here in Canada for university co-op (intern) jobs as well. Lots of people don't get jobs, but that's no fault of the matching algorithm.