Welcome prospective intern!
This is the intern version of https://github.com/hedgeyedev/Developer-Applicant-Exercise which is the 1st step of the intern interview process at Hedgeye. Th purposes for this exercise are twofold:
- Expose the prospective intern to some of the technologies (Ruby, Rails, Git)/process(Pull Requests) that will be used daily in the internship.
- A test of the interns ability to follow directions and execute. Often a resume and/or cover letter don't fairly represent what the intern is capable of, this exercises hopefully helps show what an intern can do.
- Fork this repository
- In the pick_me directly
- Add a file pick_me.txt which describes why we should choose you as an intern. It would be nice to stand out, but a fallback would be typical cover letter type verbiage. Include why you think our internship is interesting to you.
- (Optional) Anything else you want us to know, resume, portfolio, etc. is appropriate.
In the blog directory, create a simple Ruby on Rails scaffold based blog. you will have to do the following
- setup your computer for Ruby on Rails development. Rails Installer is a good start point for Windows and OSX, if you're running Linux, I imagine you know how to use your package manager to set it up. This setup for Ubuntu might be a good start point.
Create a rails project in the blog directory
$ rails new blog
Go into the blog directory and start
$ cd blog
Create a scaffold for your blog
$ rails generate scaffold Post title:string content:text $ rake db:migrate
Remove the index.html
$ rm public/index.html
Setup your routes to go to the blog index by changing config/routes.rb to
App::Application.routes.draw do resources :posts root :to => "posts#index" end
Run the server and when it's up check it out
$ rails s
Congratulations, you now have a functional but "butt ugly" (the technical term) blog, make it a little less ugly and clunky. Do what you can. Suggestions:
- Better (any) styling
- Change of labels
- Change of layout - have the index look more like a blog showing the whole blog article, or a larger portion with a "read the rest"
- Additional functionality, esp. that showing Ruby and/or other web development skills for extra credit
- Commit and Push your code to your fork
- 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.