off-topic 2018-05-02 | Slack Archive

qqq07:05:44

It should be added as a class to Baldur's Gate / Icewind dale, where instead of casting spells you just type exprs in the repl that modifies nearby objects.

danm10:05:53

@qqq Have you played else.heart.break()?

danm10:05:09

It's a game by a scandinavian team IIRC, where everything in the game is defined through a scripting language which you get a tool to access and modify. So the whole point is 'hacking' things like your bed to increase your rested to 100% in a minute instead of 8 hours, hacking doors so when you go through them you end up where you want to be on the other side of the map etc etc

steveh201813:05:56

Has anyone played around with ferret, a clojure-inspired project for the C++ embedded/ area? Very impressive to see one person make such independent progress.

tbaldridge13:05:25

I read a bunch of the source to get the gist of how it works, pretty cool for what it does.

dominicm19:05:35

Has anyone done cloud formation in continuous deployment before? How do rollbacks go in practice?

rymndhng04:05:12

do you mean continuous stack updates?

dominicm05:05:30

Yep

xtreak2906:05:08

We haven't used it in CD but we used terraform for initial server setup. We tried a remote store like S3 to store the state and then tried rolling back. I am not involved in the project so can't go on about how it worked. This link might help if you are using terraform : https://blog.gruntwork.io/how-to-manage-terraform-state-28f5697e68fa

dominicm06:05:11

We use terraform now. The lack of rollback during failure seems like it would be problematic for CD

rymndhng19:05:13

We have two types of stacks we deploy: 1. short-lived This is the stateless app stack. There's only an ASG and LC in here, we actually don't do stack updates here currently, we deploy a new short-lived stack and update the ELB to point at the ASG. You could do a stack update though! 2. long-lived The long-lived ones are applied via changesets through peer review to get the approval. These happen less frequently but it'd be possible to have CD create a changeset and await review. Databases, Queues, Topics, ELBs live here. --- We've found the tool iidy to be helpful it's a bit more user & scripting friendly out of the box (in terms of UI and also waiting for things to happen). https://github.com/unbounce/iidy

dominicm19:05:58

I'm going to look closely at this, this is really useful @U09U89Y6Q, thank you

rymndhng19:05:14

cheers 😁

dominicm08:05:32

@U09U89Y6Q when the changeset is deployed, is it deployed via automation?

rymndhng16:05:25

we don't -- it definitely could be though!

dpsutton20:05:43

just by the by, which would be faster? (vec coll) or (into [] vec)

dpsutton20:05:37

looks equivalent if (vec coll) is what happens with [coll]