I used this once as a subject for a retrospective. The team would play through the game together and make the guesses as to what would happen.
Afterwards we ended up playing against each other using some poker chips. It was a lot of fun and though it was clear that trust did not make you a winner, we might have ended up with a little more of it in the team afterwards.
It looks interesting but even after signing up I cannot find any documentation aside from the basic code snippets. An example of what I would like to know is: what if things go wrong, will there be retries?
If an error occurs on our end while processing it, we will keep retrying for a while. If an event fails to POST to your endpoint it'll have a failedAt time for when it failed. We are adding customizable retries soon, as well as docs and an SDK, thanks for your concern we know that's a big feature :)
Even if the wave isn't very tall, if it is fast-moving it can knock you off balance. Once you're down, wave doesn't have to be very tall to drown you. There's also the fact that rip currents are commonplace phenomena on beaches all over the world, so you combine that with a single unexpectedly fast wave and it's easy to believe a few people would die.
According to the "quick bulletin" on the bottom, this seems to be a downstream effect of a magnitude 6.9 earthquake that occurred. I suppose that will generally be the case for a tsunami, something usually drives it. In this case, it appears they're assigning 0 deaths (or stats) to the tsunami, but 2 deaths for the "total effects."
I've stayed (longer) because of the people more often then left because of them. It's likely also the type of company and the type of people attracted to them.
This is awesome!
Some feature requests:
it would be great though if you could have multiple sessions/tabs in stead of 1. Also a clear button would be nice.
When using it to make simple calculations while on a phone I think it would be easier than the long click select all delete combo, but perhaps this is not really the aim of the tool.
Don't wait it out. If you don't like your job, do something about it. Either change the work, or change jobs.
To change the work I suggest communicating with the people around you:
Talk to the previous developer, explain him/her what anti patterns are, why testing is important and perhaps venture into things like solid design or design patterns. Is he/she willing to listen/learn? Then he/she might also assist you in communication towards management. If not, then I personally wouldn't go to too much length to save his/her ass.
Communicate to management and talk their language as much as needed. Talk about what the cost of maintenance is and why finding bugs in production is so much more costly then while writing unit tests. Talk about the cost of change in this versus a well designed and tested system.
Then decide with management and hopefully the other dev what to do.
Afterwards we ended up playing against each other using some poker chips. It was a lot of fun and though it was clear that trust did not make you a winner, we might have ended up with a little more of it in the team afterwards.