Skip to content

Instantly share code, notes, and snippets.

View bethsebian's full-sized avatar

Beth Sebian bethsebian

View GitHub Profile

Class 4: Project Kickoff

Class Overview

  • Introduction to Agile (10 min)
  • Project overview (10 min)
  • Sprint 1 (45 min)
  • Whiparound (5 min)
  • Break (5 min)
  • Sprint 2 (45 min)
  • Whiparound (5 min)

Class 3: Basic Algorithms (cont) and a Taste of APIs

Class Overview

  • Project Work Time and Check-Ins
  • Additional Concepts in Ruby
    • Defining and calling methods
    • Passing parameters
  • Introduction to APIs
  • API Work Time

Ruby and Basic Algorithms

Class Overview

  • Ruby fundamentals
    • Variables
    • Classes: strings and integers
    • User input
    • Flow control
    • Collections: Arrays and Hashes
  • Looping
@bethsebian
bethsebian / ATC_class_1_markdown_git.markdown
Created April 15, 2018 20:01
Advanced Teen Coding Class 1: Git and Markdown

Markdown and Git

Class Overview

  • Advanced Coding Series Principles
  • Introduction to Git
    • Why?
    • Setting up a workspace with Cloud9
    • Setting up a Github account
    • Git code-along
  • Introduction to Markdown

git add -p: goes chunk by chunk through code

"Police Data Tracker" is a website I built in mod 3 to aggregate and standardize police data from law enforcement agencies. My work in mod 3 was focused on developing a proof of concept, and for this reason I was not confronted with the entirety of the technical and strategic questions surrounding my work. Revisiting the project in mod 4, including defining and beginning to tackle my MVP, has proved much more difficult. Below, I outline the 3 most challenging issues I encountered and how I chose to resolve them.

###Defining data attributes for each data category
####Problem Disparities in each cities datasets complicate adding them to my database. Cities publish wildly different information. For example, consider the category of officer-involved shootings (OIS).

Los Angeles publishes 3 separate API endpoints to cover OIS: 1) data about the incident itself, 2) information about the officer(s) involved, and 3) information about the suspect(s) involved. This structure allows them to document incidents th

Setting Group Expectations

Group Member Names: Beth, Penny

1. When are group members available to work together? What hours can each group member work individually? Are there any personal time commitments that need to be discussed?
Schedule here: https://docs.google.com/spreadsheets/d/1QjxyP7p08GaC4Ncxw_rbkp8lwWO6ticnu_-L6dQEp90/edit#gid=0
Penney: Mornings are better Beth: Mornings are better, crash ~4.

2. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained?

Which of Sandi's rules do you feel like might be the hardest to follow—why? Rule 3, limit params passed to method to 4, including hashes, would be the most difficult. I agree it clutters code to call a method and pass it multiple params, but in the case of hashes, the benefit does not seem so clear.

My main question is how that affects creating objects from form data. We're accustomed to passing object params to a model, after verifying them with a private method that allows us to ensure we are only passing user-generated data we know is safe and useful. Haha...just answered my own question here: remembered that we don't actually pass the private object_params method params, that the private object_params method has access to those params and we don't need to pass them through.

I image there are still cases when passing a set of attributes along in a hash, between controller and model for example, would be handy.

What were we trying to accomplish?

  • Goals: take single-tenancy store to multi-tenancy store
  • Learning more important than extensions
  • Learning, familiarize ourselves with structure
  • Individual learning goals

Where did we hit (or miss) our objectives?

  • Lenny: felt like got 80% of exposure out of it
  • Justin: got base stuff done, didn’t get chance
  • Beth: refactoring, didn’t get a chance to work on permission service, implementing permission service early so everyone has a chance to touch it