sak55 commented 9 years ago

24 -- One Helluva Ride

Rinse lather repeat.

Remember to link each of your PRs to your WIP Issue!

Requirements

[x] YAK (s)
[ ] WIP Issue: 24 -- Helluva Ride (s)
- [x] checklist of assignments and checkpoints
- [x] link to each PR you merge
[x] WIP Branch: (s)
- [x] work in: TIY-Assignments:feature/24--helluva-ride
- [x] deploy into: TIY-Assignments:gh-pages
[ ] WIP Files: (XL)
- [x] timeline/index.html (m)
- [ ] surf+paddle/index.html(m)
- [ ] katas/(L)
- [x] string-calculator.js
  - [x] "zero" through "ten"
  - [x] "ten" through "twenty"
  - [x] "twenty" through "thirty"
  - [x] "fifty" through "sixty"
  - [x] "ninety" through "one hundred"
  - [x] "one hundred" through "one hundred twenty"
- [x] check-writing.js
- [ ] roman-numerals.js
- [ ] euler-1.js -- formerly 3s+5s.js
- [ ] euler-2.js -- even Fibonacci
- [ ] euler-4.js -- largest palindrome
- [ ] euler-5.js -- smallest multiple
- [ ] apis/gymnastics.js (m)
- [x] Checkpoint: Got me some data...
- [ ] Checkpoint: Count it up right...
- [ ] Checkpoint: Filtering out just the PushEvent entries...
- [ ] Checkpoint: Now doing the complete opposite...
- [ ] Checkpoint: I have all the answers now!
- [ ] Mission Complete
- [ ] chessboard/ (L)
- [ ] index.html
- [ ] css/main.css
- [ ] js/main.js
- [ ] github/ (L)
- [ ] index.html
- [ ] css/main.css
- [ ] js/main.js

sak55 commented 9 years ago

Description

You've come a long way since that first week. Right now, you're dirty, tired, and worn-out, but just on the other side of this tunnel is Angular JS and full-blown application development. Hang tight.

Choose Your Own Assignment

There are a handful of assignments from the last few weeks that should stand out:

Redo all of these... or at least a reasonable replacement for each. String Calculator gotcha down? (It gets much more interesting after 20...) Swap it out for a different kata. Can't stand Surf & Paddle? The Iron Blog is essentially the same assignment, so do that one instead.

See Requirements for what to name them and where to put them, but make your own rules and checkpoints for each. Use whatever tools you think will help you... or challenge you. Pace yourself. Work with others. Review your notes. Look at your old code on Github, if it helps (probably won't, though). Write your own code.

Show me yo' moves!

Let's practice deploying to gh-pages as if it were the staging environment on a real project. As you complete each piece of the assignment, push your work to Github and push your branch to your gh-pages branch.

After you confirm your deployment, open a PR from your feature branch to your master branch and solicit feedback from your peers. Convert their feedback and any known issues you find into a checklist in the description of the PR. Add commits to the feature branch to check things off your list and get your 2x:+1:'s!

Once approved, merge that bad boy but keep the branch! Do some more work on the next piece, push to your feature branch, update your gh-pages branch, and open another PR to master for review.

Show me yo' moves!

To make it easier for your peers to find your work, include a file named index.md in your repository root. Initially, it should look like this:

---
---

### Projects

* [Current WIP](pub/index.html)

Note the two rows of three hyphens at the top of the file... They're important. When you push that file to gh-pages, Github will convert it to an index.html file automatically... as long as you have those hyphens. Use Markdown to link to each project as you complete it.

Coding Dojo Katas

Check Writing

/**
 * @param Number n representing a dollar value
 * @returns String of English words for `n`
 */
function toCheck(n){
} // END toCheck

assert.equal(toCheck(1.23), "one & 23/100s dollars");
assert.equal(toCheck(12.34), "twelve & 34/100s dollars");
assert.equal(toCheck(123.45), "one hundred twenty three & 34/100s dollars");
assert.equal(toCheck(1234.56), "one thousand two hundred thirty four & 56/100s dollars");
assert.equal(toCheck(12345.67), "twelve thousand three hundred forty five & 67/100s dollars");

/**
 * @param Number
 * @returns String an English number word
 */
function toEnglish(n){
} // END toEnglish

assert.equal(toEnglish(0), "zero");
assert.equal(toEnglish(1), "one");
assert.equal(toEnglish(2), "two");

Roman Numerals

/**
 * @param String numeral a Roman numeral
 * @return Number value of `numeral` in decimal
 */
function fromRoman(numeral){
} // END toNumber

/**
 * @param Number n greater than 0
 * @return String Roman numeral for `n`
 */
function toRoman(n){
} // END toRoman

assert.equal(fromRoman('I'), 1);
assert.equal(fromRoman('II'), 2);
assert.equal(fromRoman('III'), 3);
assert.equal(fromRoman('IV'), 4);
assert.equal(fromRoman('V'), 5);

assert.equal(toRoman(6), 'VI');
assert.equal(toRoman(7), 'VII');
assert.equal(toRoman(8), 'VIII');
assert.equal(toRoman(9), 'IX');
assert.equal(toRoman(10), 'X');

// Fill in the `undefined` values...
assert.equal(toRoman(20), undefined);
assert.equal(toRoman(30), undefined);
assert.equal(toRoman(40), undefined);
assert.equal(toRoman(50), undefined);
assert.equal(toRoman(100), undefined);
assert.equal(toRoman(200), undefined);
assert.equal(toRoman(400), undefined);
assert.equal(toRoman(500), undefined);
assert.equal(toRoman(600), undefined);
assert.equal(toRoman(900), undefined);

// Woah...
assert.equal(toRoman(1000), undefined);
assert.equal(toRoman(2000), undefined);
assert.equal(toRoman(4000), undefined);
assert.equal(toRoman(5000), undefined);
assert.equal(toRoman(6000), undefined);

// What comes next?
assert.equal(toRoman(9999), undefined);

You might need to learn something about Roman Numberals to finish this one.

sak55 commented 9 years ago

my PR

sak55 commented 9 years ago

my Timeline

sak55 commented 9 years ago

my String-Calculator

sak55 commented 9 years ago

my Check-Writing