search

18F / 18f-scaffolding

A scaffold/generator to standardize 18F project setup
Other
26 stars 14 forks source link

Idea: alan facts #5

Open konklone opened 8 years ago

konklone commented 8 years ago 
18f alan

should provide a random Alan fact, ideally taken dynamically from the currently set Slackbot response (but manual sync might make it easier, to avoid Slack auth).

adelevie commented 8 years ago

agreed.

stvnrlly commented 8 years ago

Perhaps there should be an app serving Alan facts, which both Slack and this command could call?

vdavez commented 8 years ago

i was thinking about a repo with a yaml file.

adelevie commented 8 years ago

but will it scale?

vdavez commented 8 years ago

what, the yaml file? eventually we'll need to get the facts into a distributed db.

adelevie commented 8 years ago

let's start reading through all of these https://aphyr.com/tags/jepsen so that we can find a suitable database. if nothing out there is good enough, we might need to create alanDB.

konklone commented 8 years ago

I've been looking for an opportunity to give Manhattan a test run for the right problem. Let's get an Oort cloud going and we'll install Manhattan onto the underlying mainframe.

yozlet commented 8 years ago

As much as I hate to break up the new-toy party, I'm not seeing any product design to go with this implementation. Has anyone even done any user research yet? Paper prototypes? Hello?

Come on, people. I thought we were better than this.

adelevie commented 8 years ago

Prototype:

$ 18f alan
The 18f alan command is self-referential. See, https://github.com/18F/18f-cli/issues/5#issuecomment-226857115.
stvnrlly commented 8 years ago

I've added an initial alan command in https://github.com/18F/18f-cli/commit/d82d8395c3142cff51694abdf663652dcec77365. If we do create a source of alanfacts (perhaps a gist would do in lieu of a server?) I have an idea for incorporating it into the current script.