Curriculum Recap from Tonight

[Brendan Kemp]

Hi everybody!

I'll try to summarize everything we discussed tonight that is related to curriculum. Chime in if I forgot something.

We planned to really iron any final kinks in the installation instructions. This involves:

  * Writing a coherent set of instructions for OS X. We can cull this from the current wall of text, 

    writing further instructions as necessary for older versions.

  

  * Finalizing the shell instructions for Windows. We agreed to tell users to execute long-running processes like servers 

    in the Windows "cmd" shell. I will make the necessary edits, but everyone should check out the current version here: 

    http://www.railsbridgeboston.org/ruby_from_scratch/install/windows

  

  * Double checking the installation instructions for Linux. I installed an Ubuntu VM, ran through them, and made some minor edits. 

    I'd like a Linux expert to make sure I made the right choices.

  

  * Which brings up: the question of a one-line installation script. Should we use one in Linux, or OS X, for that matter?

    I currently agree with Andrew K's reasoning that the act of setting up the development environment manually—and the 

    concomitant comfort with your computer's inner workings—is one of the learning experiences that we 

    provide. Arguing for a script solution is the fact of time, specifically all the time we could spend teaching other

    important, under-represented topics like Git, or text editors. I think any script that we might select would have to 

    have make the correct configuration choices, in terms of correct use of super user permissions, correct installation path, 

    safe PATH modification, correct package manager usage, etc. Anyhow, we agreed that the question is on the table,

    and that we should discuss it further.

All of these steps require volunteers to run through an installation from scratch, to make sure the installation goes without a hitch.

If anybody wants to step up I'd be appreciative.

The Saturday day curriculum we agreed to keep substantially the same. 

  * We will keep the same example app, and build out further extra-credit around that, focusing on providing more content 

  for students who move quickly. There seemed to be agreement that certain topics could use

  extra credit sections, including Git and Ruby fundamentals.

  * We also agreed to structure the content so that the "answers" (i.e. the actual commands) can be hidden by default, and 

  revealed on click. This will allow advanced students to engage more with the material. I volunteer to make these changes.

TL;DR Here's what you can do! (Volunteer opportunities)

* Rewrite OS X directions; make sure they run smoothly on 10.6+

* Do a from-scratch installation using the instructions for Windows, Linux or OS X. Make sure you take note of any problem or ambiguity!

* Write an extra-credit section (ideas: Git, Ruby, …?)

* Write a Friday night breakout session

* Argue for or against one-line installation scripts.

* Write to tell everyone about the conversations I forgot from tonight.

- Brendan

[Daniel Choi]

That is a great summary Brendan.

On the point Michael Durrant made about wanting to cover TDD and other topics, it looks like RailsBridge SF is talking now designing "deep dive" follow-up workshops. Please join their mailing list if you want to engage!

This is the "deep dive workshops" thread:

https://groups.google.com/d/topic/railsbridge-workshops/D1V8rSAzvR8/discussion

Dan