Difference between revisions of "New Member Orientation"

From Earlham CS Department
Jump to navigation Jump to search
(Statement)
(Workspaces)
Line 13: Line 13:
  
 
=== Keys ===
 
=== Keys ===
* get a key request form from Bobbi.
+
* go [[http://form.jotform.us/form/41466536567161]]
 
* fill it out and include applicable locations
 
* fill it out and include applicable locations
** Dennis front entrance, ???
 
 
** Dennis back entrance, CAX
 
** Dennis back entrance, CAX
 
** Dennis roof, CAB 6
 
** Dennis roof, CAB 6
** 2nd floor lab, ???
+
** 2nd floor lab, CAA3
 
** Noyse basement, CAB 13
 
** Noyse basement, CAB 13
* get a signature from Charlie
+
* public Safety should email you when your keys are ready
* take form to security
 
  
 
== Projects==
 
== Projects==

Revision as of 13:42, 6 February 2015

I'm going to make no assumptions about you or your purpose for being here. Read what you need or want; you can always come back.

Overview

  • read the About Us page
  • there's generally a pool of projects available
  • you can pick what project you work on
  • we perform maintenance as well as implement new projects

Workspaces

  • Dennis roof
  • Noyes basement
  • Green Zone

Keys

  • go [[1]]
  • fill it out and include applicable locations
    • Dennis back entrance, CAX
    • Dennis roof, CAB 6
    • 2nd floor lab, CAA3
    • Noyse basement, CAB 13
  • public Safety should email you when your keys are ready

Projects

Check HIP for up-to-date project listings.

This is a list of present/past projects that we've worked on. It's intended to give you a taste of what we do.

  • solar array
  • wind generator
  • energy monitoring of buildings
    • normalization of resulting data
  • kiosks that display energy information
  • earthquake sensors
  • time server
  • construction cam

Communication

Group

  • we use a listserv, email hip@cs.earlham.edu to email everyone
  • generally it's good to notify the group about significant progress via email or in meetings
  • phone numbers / emails are useful to have
  • google services such as docs, spreadsheets, etc can be used for development
    • you need gmail accounts to utilize these services

Meetings

  • Friday in the Green Zone for lunch (12-1pm)
    • general discussion about current and future projects
    • bring-your-own-lunch style
  • Sunday on the roof (1-3pm)
    • working together in the same space

Documentation

Documentation is an important part of HIP because different people from different times will need to know about the work you did. It's more efficient to point them here than to explain something multiple times.

  • document projects
    • inline code documentation helps readability
    • wiki articles are fast and helpful
    • document changes to keep information relatively accurate
  • document your work, process, or experience
    • your experience is invaluable to someone who is in a similar situation

Wiki Basics

  • how to use
    • you need an account to be created by an admin; ask Charlie or Ivan
    • if a page doesn't exist, search for it and the wiki will let you create that page
    • make sure to click "Save Page" after you're finished editing
  • how to learn
  • how to style
    • having too many headers can be overkill
    • lists are the simplest way to organize content
    • trim things down