At Zalando we have an account per team, and have been releasing a bunch of tooling to help do this securely.[1] It's not completely easy (e.g., account creation at Amazon can not be automated), but the security aspects are really nice, and it lets us give teams more or less full access to just their account.
Zalando is hiring in Berlin, Dortmund, Erfurt, Mönchengladbach (Germany); Dublin (Ireland); and Helsinki (Finland).
Zalando has built an entire fashion ecommerce stack, and is now starting development work on a number of new tech initiatives around extending beyond being just an ecommerce website to being a platform for connecting people with fashion. There is a lot of high end engineering and product work, from programming warehouses to building Big Pipe to cutting edge data science to building entirely new customer facing products.
It's a great place to work and an incredible product vision.
Could each draw return a draw_hash, that is usable only once? Not only could you then have idempotent draws, you could easily embed it as hypermedia,a previous hash could be sent to a hand_history to return an array of point in time data
1. specify the api in json
2. apidoc generates really nice api documentation
3. apidoc generates a single-file client for the service (currently ruby or scala)
4. apidoc generates a routes file for play2
It's scala-biased at the moment because that's their tech stack, but in practice an api-first approach seems to lead to higher quality APIs compared to just hacking something together and annotating it to extract docs. Also having a really nice client without a complicated compile-time dependency graph (on the JVM) feels like a sweet spot.
I do not understand ... please, can you elaborate what is the connection between GEB (which I presume is 'Gödel, Escher, Bach') and for example the "Learn you a Haskell" book ? They are both good books, but I do not think that books about programming languages are suitable alternatives to GEB.
The xml stuff is more the exception than the rule. They've moved away from that approach. Whether to keep it at all has been discussed quite a bit. It would be more fair to look at the newer code in the collection framework to paint what is considered "best practice" by the creators of Scala.
[1] https://stups.io