#Spec thoughts
include 
- direction to simlar code -- syntax reference
- similar examples
- assign technical expert w big picture implementation strategies
^^ they find tutorials and examples
^^ even as simple as "I would use a flex box here"
- regular scheduling of work sessions in a project spec
^^ productive work sessions may include pair programming, code reviews, etc.
^^ simple code reviews may allow people to learn from each other efficiently
^^ better learning creates longer term retention and outcomes
^^ even regular github comments could help
- technical leadership does a little code for good infrastucture
^^ manager doesn't have to be technical leader would be more experienced member
^^ ideally training someone is rewarding and doesn't feel like ineffecient

- Emmassing specs might help with project example collection
^^ searchable and organized?
^^ tools we actually and regularly use and how their being used

Minimizing number of number of places people need to find things
Making sure link to spec is always present during project
- Where people are regularly, Slack?
Retrospective on specs to note what worked and what didn't

Viewing specs as training opportunity rather than administrative documentation

Also angela cmd + a !