Skip to content
Browse files

Merge pull request #3 from benjaminoakes/master

Simplify what we're looking for
  • Loading branch information...
2 parents bbbf6c3 + 918d488 commit e4e2339a4b7261a70455e04cdc45dd00b96f0a01 @fkchang fkchang committed Mar 15, 2012
Showing with 13 additions and 19 deletions.
  1. +13 −19 README.md
View
32 README.md
@@ -2,41 +2,35 @@
To be considered for a developer position at [Hedgeye](http://www2.hedgeye.com), you must successfully complete these steps [**](#footnote)
-**Please note:** your code will be tested on Ruby 1.9.2. If we need a browser to test, it will be the latest version of Chrome, Firefox, Internet Explorer, and/or Safari.
+**Please note:** your code will be tested on Ruby 1.9.2 and the latest version of Chrome.
1. Fork this repository
2. In the *why_hire_me* directory
* Add a file `cover_letter.txt` with cover letter type verbiage.
- * Add a file that describes one of your preferred development tools (editor, desktop app, etc.) and why you use it (max 3 paragraphs)
- * Fill out the questionnaire.txt and commit it
- * Anything else we should know
+ * Fill out the `questionnaire.txt` and commit it
+ * Anything else we should know. For example, one of your preferred development tools (editor, desktop app, etc.) and why you use it.
3. In the *simple_refactoring_exercise* directory you will find some Ruby code that needs to be refactored.
* An rspec spec is provided
- * Please [refactor](http://www.refactoring.com) the implementation. Clarity, and duplication a given, flawed implementation also likely
+ * Please [refactor](http://www.refactoring.com) the implementation. Clarity and duplication are a given, flawed implementation is also likely.
* Please note: feel free to change the specs, but they should all be passing when you turn in your code.
- * Leave a note what you refactored and why. Calling specific smells and specific refactorings recommended.
+ * Leave a note about what you refactored and why. Calling specific smells and specific refactorings is recommended.
4. In the *simple_public_timeline* directory, please create a simple web app (use the Ruby framework of your choice. Suggestion: Sinatra is good for a tiny app like this) that looks close to the middle column in logged out state of http://twitter.com/public_timeline
* A headline with "Recent Public Tweets"
* A smaller headline "What everyone on Twitter is talking about"
* Displays 20 entries from twitter's public timeline. Use the data/API of your choice
- * For each entry, show:
- * image profile on the left
- * a "stack" on the right including a link to the users profile, followed by the tweet text on the same line. Below that the relative time of the tweet (i.e. 1 minute ago) and source attribution (i.e. "via Twitter for Android")
- * Barebones style adequate. No need for nice css, text wrapping.
+ * For each entry, show the profile image, a link to the users profile, the tweet text, the time of the tweet, and source (i.e. "via Twitter for Android")
+ * Barebones style is adequate. No need for nice CSS or text wrapping.
* Provide the previously described view in 2 ways
- 1. have the route "/" retrieve the twitter data on the server side and then render
- 2. have the route "/via_js" retrieve the twitter data with Javascript and render it after the document loads
+ 1. Have the route `/` retrieve the Twitter data on the server side and then render
+ 2. Have the route `/via_js` retrieve the Twitter data with JavaScript and render it after the document loads
* Required
* `.rvmrc` and `Gemfile`
* at least 1 spec
- * Optional (Extra Credit)
- * Comprehensive specs
- * More/Nicer Styling
- * More things that look like the original
* Tips
- * Do use gems, and Javascript libraries.
- * If you are Ruby, Javascript and web development savvy, it shouldn't take you that long. A sample implementation, sans specs, is less than 100 lines of text total.
- * Optional stuff at the end. Don't get caught up on styling, that's what designers are for.
+ * Do use gems, and JavaScript libraries.
+ * If you are Ruby, JavaScript, and web development savvy, it shouldn't take you that long. A sample implementation, sans specs, is less than 100 lines of text total.
+ * Don't get caught up on styling, that's what designers are for.
+ * Be careful with Twitter's rate limiting while testing.
6. Commit and Push your code to your fork
7. Send a pull request, we will review your code and get back to you. If your GitHub profile does not include your name, please include your name in the pull request.

0 comments on commit e4e2339

Please sign in to comment.
Something went wrong with that request. Please try again.