Notes on your Challenge Assignment

Thanks again for your time Keenan. I've included some specific notes within your code on ways that it can be improved. Some additional thoughts:

* Remember to ask questions when working on a project like this. Never assume intention if something is unclear or seemingly wrong. For example, in our wireframe, the remove button is larger than the follow up checkbox. Is that correct or is it a mistake? Which action is more important?
* Never assume anything is an edge case. That edge case might be important to a user.
* It's great to prototype new features and think about improving the UX, but they have to work. Most notably, the pagination. A very smart inclusion, but it doesn't update. If you remove all of the tweets on the screen, you're left with an empty page in your pagination.
* Look for places to add that last bit of polish to your UI. Two examples:
    - "Follow Up" breaks onto two lines
    - When you sort on the name column, the width of the column changes because the names are different widths.
* You mentioned that you had a version where the rows looks like our messages screen—we would love to have seen that.

TL;DR: Sweat the details.

If you're interested in learning a JavaScript framework, I suggest Backbone not only because it's what we use but because it will help you improve your JavaScript chops, as well. It's not as opinionated as Ember or Angular, so you'll learn a lot of good JavaScript practices, too. Try the Backbone Yeoman generator: https://github.com/yeoman/generator-backbone. (Bonus: You'll learn Grunt, too!)

You have a great future ahead of you. You really do get this stuff. I hope you'll stay in contact with Jim and keep us posted on your whereabouts. If you have any questions about this pull request or anything else you're working on and learning, don't hesitate to reach out to me directly. https://www.linkedin.com/in/arlodesign