✨ Shiny future: Where we want to get to

The "shiny future" is here to tell you what we are trying to build over the next 2-3 years. That is, it presents our "best guess" as to what will look like a few years from now. When describing specific features, it also embeds links to design notes that describe the constraints and general plans around that feature.

Predicting the future is a tricky business! Many of the things described in the "shiny future" doc have a lot of uncertainty. We fully expect that the designs and narratives described in this document will change as we work towards realizing them. When there are areas of particular uncertainty, we use the Frequently Asked Questions and the design docs to call them out.

Help wanted. This is not a static document! There are lots of ways you can help to expand it! Take a look at the How to Vision Doc for more details.

Alan has a blast standing up a web server

CharacterStatus quoAssigned To
AlanAlan has trouble getting startedShane and estebank

Outline:

...

🤔 Frequently Asked Questions

* Write these

Grace deploys her service and is able to fix problems

CharacterStatus quoAssigned To
GraceGrace deploys her service and hits obstaclespnkfelix

Outline:

  • Grace launches service
  • Hits a stalled task, debugs the problem
  • Customers complain about poor performance, she tracks it down
🤔 Frequently Asked Questions

* Write these

Grace discovers the joy of generators

CharacterStatus quoAssigned To
GraceGrace tries to write a stream and pin breaks her mindVolunteer wanted

Outline:

  • Grace uses generators and the code writes itself. It's ALMOST TOO EASY.
🤔 Frequently Asked Questions

* Write these