Accepting the counter offer may not be a great strategy, but listening to it is. When changing jobs the last time, my old employer offered a salary bump to keep me. When I told this to my new employer, they immediately offered to match the salary. I ended up making more money than I would have otherwise.
HN user
omahlama
[ my public key: https://keybase.io/omahlama; my proof: https://keybase.io/omahlama/sigs/O8bmZnufz-ttSHdmT0DlLT5K82DWOmGX0DNh3k0BsQ8 ]
It's not really DOM manipulation that was avoided, it was the simpe rerender on every change model that was avoided (for good reason, before React it performed horribly for anything except trivial applications)
In my previous job at the Finnish software consulting company Futurice (http://futurice.com), there was a long discussion about this that ended with a volunteer-based publication of peoples salaries - around half of the 200 people opted in. The result was a bit anti-climatic: peoples wages were consistent and fair, no big drama.
After switching jobs to another software consulting company Reaktor (http://reaktor.com), I brought up this topic and the discussion was very similar. I decided to try a different route: I created a wiki-page called "Voluntary salary information" and added my name and salary to the top of the page. I then wrote a post to our discourse board explaining why I thought this was important. As of now there are 68 names on that list ( with only 1 obvious troll ) out of about 300 employees. Our head of HR replied to my discourse post with a detailed explanation of how peoples salaries are decided. Overall a great day for transparency.
That sort of thing happens all the time on stackoverflow, where most of the users aren't native English speakers. Go for it!
I don't want to give any information out before it's revealed to everyone, it wouldn't be fair. I'll just say that the response speed does matter, but at least in our beta tests the benefit of using one language over another was how productive the team was - so I would recommend choosing the language you're most comfortable with. Anyways, you can switch language at any point.
F# is very likely to be added (unless we run into some problems), thanks for your feedback :)
During the finals yes. The qualifying round is run with standardized virtual linux boxes, so all bots must have the same build and run scripts. With the amount of participants we're expecting, it wouldn't be possible to run the competitions manually.
I agree. The main point of this competition is fun - having beta tested the system I can promise that writing bots and watching them compete is a lot of fun. I hope your team can participate.
(Disclaimer: I'm not part of the organizing team, but I do work for Reaktor - so this is just my opinion, not an official position.) As I've understood, the same country requirement works just like in sports: you need to be a citizen of the country if you want to play in the national team.
I would suggest contacting the organizers about your situation.
It does work - I've seen it :) It does depend on a low ping between the bots and the server, but that is taken care of by the organizers.
Servers are available for testing during development, running the code on your own computer - the CI server is useful in that it verifies that your code compiles and runs on the linux machine used during the competition.