sjinta

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.

I think using "Monolith" for what they ended up with is badly chosen. Basically they just made a service less granular (or less micro, if you will).

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?

but it still ended up killing 2 people. I have a hard time imagining how that works.

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.

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.

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.

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.