stuff that can be removed or generalized #272

Closed
cczona opened this Issue Aug 8, 2012 · 19 comments

4 participants

@cczona

I'm working on generalizing the curriculum for ongoing use. What are good candidates for removal?

  • refs to http://jumpstartlab.com/chat
  • refs to individual participants, such as "Steve will give lightening talk next week"
  • refs to milestone dates, such as "Homework for 2/10" or "March 12: Object design, source control, reading group"

Others...?

@steveklabnik

Awesome, thanks!

Outside of milestone dates, almost any date is probably going to be bad.

Those things are the only things I can think of that would need removed. Other things, which have tickets.

  • Continuing the JS* -> * name scheme change.
  • Removing any Ruby 1.8isms

Hmm. I'll post other things if I think of them.

@kytrinyx

@steveklabnik, @burtlo Should references to the chatroom be removed?

E.g.

CodeMash Rails tutorial

Are you prepared?

You need:

To join the chatroom at http://jumpstartlab.com/chat
Ruby 1.9.2 or greater
Rails 3.1.3 or greater
To open three terminal or command prompt windows and change into someplace you want to store your projects

@steveklabnik

I dont think so; we print this stuff out and it's useful then. @jcasimir ?

@jcasimir
Turing School of Software & Design member

In general I'm in favor of removing.

My vision for the "paths" (https://github.com/JumpstartLab/curriculum/tree/master/source/paths) is that those are the one-off note sheets for events like a CodeMash workshop. That's where specific dates, links, names belong. Then they should like off to the other resources (projects, topics, etc). Cool?

@steveklabnik

Seems fine. :)

@kytrinyx

To summarize: the source/academy directory is going to get a full overhaul, and the source/paths/ directory can contain specifics (dates, links, names).

The source/topics/ directory appear to be quite clear of dates and such.

To rephrase the current issue so that it is a bit more specific:

Clean up references to specific dates, days of the week, or instructors in the source/projects/ section.

In the order listed on the tutorials page, that means:

  • ruby_in_100_minutes.markdown
  • eventmanager.markdown
  • jstwitter.markdown or (if merged) microblogger.markdown
  • blogger.markdown
  • jsmerchant.textile or (if merged) merchant.textile
  • event_reporter.markdown
  • sales_engine.markdown
  • store_engine.markdown
  • son_of_store_engine.markdown
  • feed_engine.markdown

Also included in source/projects/, but not listed on the tutorials page:

  • encryptor.markdown
  • jscontact.textile
@kytrinyx

Ruby in 100 Minutes is clear.

@kytrinyx

EventManager is clear.

@kytrinyx

JSTwitter / MicroBlogger is clear.

@kytrinyx

Blogger is clear.

@kytrinyx

Merchant is clear.

@kytrinyx

EventReporter is clear.

@kytrinyx

In the SalesEngine the evaluation criteria, point (4) has the header "Live Hungry". What would be a more generic and appropriate name for this?

@kytrinyx

In the StoreEngine project there are demo users that seem tied to the specific HA version of this assignment. Does this have to do with the evaluation process and being able to test real emails?

Normal user with full name "Matt Yoho", email address "demoXX+matt@jumpstartlab.com", password of "hungry" and no display name
Normal user with full name "Jeff", email address "demoXX+jeff@jumpstartlab.com", password of "hungry" and display name "j3"
User with admin priviliges with full name "Chad Fowler", email address "demoXX+chad@jumpstartlab.com", password of "hungry", and display name "SaxPlayer"

@kytrinyx

Note: The "Live Hungry" evaluation criteria is also used in StoreEngine.

@kytrinyx

Ok, we're down to the two questions:

  • "Live Hungry" as a header for evaluation criteria, and
  • demo users in the StoreEngine project

Then this issue can be closed.

@steveklabnik

Yeah, "Live Hungry" seems too specific. I'd just change the passwords to 'password.'

@kytrinyx

I went with "Effort" instead of "Live Hungry".

@kytrinyx kytrinyx closed this Nov 30, 2012
@jcasimir
Turing School of Software & Design member
@mikesea mikesea pushed a commit to mikesea/curriculum that referenced this issue Mar 25, 2014
@kytrinyx kytrinyx Scrub HA-specific details from SalesEngine. See #272 94774f4
@mikesea mikesea pushed a commit to mikesea/curriculum that referenced this issue Mar 25, 2014
@kytrinyx kytrinyx Delete HA-specific details (StoreEngine). See #272. 184c151
@mikesea mikesea pushed a commit to mikesea/curriculum that referenced this issue Mar 25, 2014
@kytrinyx kytrinyx Remove HA-specific details (SonOfStoreEngine). See #272. 69043d6
@mikesea mikesea pushed a commit to mikesea/curriculum that referenced this issue Mar 25, 2014
@kytrinyx kytrinyx Delete HA-specific details (FeedEngine). See #272. 01f1871
@mikesea mikesea pushed a commit to mikesea/curriculum that referenced this issue Mar 25, 2014
@kytrinyx kytrinyx Remove HA-specific references. See #272. b87dcad
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment