MEDIUM-TERM QUESTIONS
- Define a high level mission statement
- what are we focusing on and what we do not plan on teaching?
- why we are not doing Rails, why you should go back to basics: blog post? disclaimer? (e.g. wordpress/tools/startup-type helpers vs learning how to program from the ground up)
- Coach inductions
- Explicit paths/tracks through our training content
- Development environment surgeries
- Define roles such as course coordinator/tutorial coordinator/tutorial owner
- Possibility of being evolving from student to coach
- Students working on their own projects: too vague? enforce what they are working on? separate areas?
- Discuss how to pair coaches and students
- Long term students: have buddies/pairs?
- Process for people to help out and volunteer, and be responsible for a thing
- Feedback for coaches
- Things better written out, figure out how people can help with copy, wording the mission
SHORT-TERM ACTIONS
Assigned
- Andrew: contact Sublime about free licences
- Despo: Flagging the fact that the end of HTTP track ends in “deploy your own”
- Camille: Create a discourse board
- Claudio: initial chats with new coaches
- Leo: draft a guide for standardised setup for students, Sublime, Atom (Railsbridge, think of Windows users)
- Despo: organise meeting on 12th July to discuss medium-term questions
- Matt, Camille: review funding proposal
Unassigned
- Flagging the fact that the end of HTTP track ends in “deploy your own”
- Ask LRUG for new laptops
- Sort out the CSS3 and HTML5 tutorials (lesson 5, title needs to change? tutorial needs to change? misguided to do it separately? why is this any different from the other APIs?)
COURSES
- Git and Github
- Reponsive design/grid
- Ops landscape, keywords and terminology
- HTTP fundamentals
- Advanced HTTP
- Terminal/Unix (Camille)
- TDD/mocks/stubs…
- Settings up a development environment
- UX
- Understanding hosting
- “Conceptual” sessions
- APIs
TUTORIALS
- CSS animations, transitions
- Fundamentals of programming, loops, satements, after HTML, learn what an algorithm is
- Databases: relational, nosq, sql basics, sqlite, creating and managing DBs
- SVG and canvas (d3.js)
- API/data formats: ajax, xml, json, rss, some examples that should already exists
- REST for beginners
OUT OF SCOPE BUT FUN
- Branding 101
- Arduinos
THINGS WE DON’T WANT TO TEACH
- wordpress
- debuggins
- algorithms
- open web apps
- ruby on rails
- payment systems
- deployment pipelines