asyncanup

Books on the bookshelf (top-right) are:

- daemons

- whoami

- traps

- curses

- pwd

- inbox

bags hanging underneath them:

- spawn

- nroff

- dates

- root

a log against the fireplace wall which says "login",

with potion-like bottles saying "uucp"

and the biggest bottle of potion is named "C" (of course),

while an old broken bottle lies on the ground called "B" (of course)

Symbols on the wizard's clothes are all unix symbols:

- $ (default PS1)

- * (glob)

- % (substring)

- > and < (pipe redirection)

Now to the bottom (right to left):

- A jar called "troff"

- A spool called "usr"

- Container called "awk"

- A jar of "oregano"

- Cursive writing on a parchment paper, "shell script"

- A small cup of "tar"

- Another bottle called "diff"

Update: Ah, you said excluding the words! I guess I was too excited to write down what I saw :P

Yes to case-by-case, and in this case, Hacker News being a somewhat representative demographic of the Tech sector, it is rather unfortunate that it lacks the noted diversity.

It's not ok to suggest that the Tech sector, being one of the most important industries for gaining financial independence and making an impact on the world, must remain the white male bastion that it is.

Couldn't agree more. But how will YouTube itself will be preserved beyond Google's economic interests?

I love the ES6 book, crisp and clear

The ui seems considered and polished, works good on mobile for me

this is so great. absolutely amazing advice

Thanks! Added some more context in a comment. Did you have any feedback for the slides and/or code?

Motivation for writing this tool will hopefully be made clear by the following abstract:

--------

Service discovery has been made too complex by combining it with orchestration. There are too many beasts-of-a-tool out there that do too much, and yet can't do versioned microservice deployments. This talk will walk you through 100 lines of Node.js code with no dependencies other than redis, and implement a discovery service with the following features:

1. Semantic versioning of services:

Services depend on specific versions of other services, so v1.2.3 & v1.3.0 can both be live, and you kill off old services that have no users.

2. Live health checks with inversion of responsibility:

Don't ping a service under high load with status & health checks, instead let it ping back when it can. If it can't ping back because it's near-capacity, then don't route any more traffic to it!

3. Mocking services during testing & development: Should not have to bring up the entire microservices stack to develop one of them.

4. Randomized scheduling: So you don't starve any one service, instead pick one at random from the ones available & healthy.

5. No highly-available service discovery service: Solving the chicken & egg requirement of a highly available service discovery service, in order to enable other highly available services. Only the service discovery database (redis) needs to be distributed.

A surprising number of tools out there simply fail to provide these set of features together, and yet pack in too many other things they want to do. This talk does the above in easy-to-understand 100 lines of Node.js code that you can use & modify with confidence!