After the first, comes the second day! #hackership

Tweet

Well, the second day was going to start pretty early and with a talk so I decided to get up early, and also I wanted to put into practice one of those best practices that we talked the first day, do exercise. So I got off the Ubahn a few stations earlier so that I would walk for a bit.
It has been a cold day but sunny, which for a change, so it really helped to wake up and get full of energy….will that help learning, who knows, but at least health will thank it 😀

The day started with a talk, given by Ellen on deliberate practice

Then a lighting talk followed 🙂 … keep you own journal of what your are doing, but if you automate something or you do it in the techie way you may find it more fun. So you can use
Jou*
gem install jou
jou -a "Add something to your journal"

Ok, the morning talks were over, time to get some coffee, to ask Ellen how to approach our own projects, getting ready for the day.

Some people have to set up their working environment, and in what I can help is setting it up in GNU/Linux, so let’s try!

First thing, you need to install rvm with ruby

curl -L https://get.rvm.io | bash -s stable --ruby
rvm install 1.9.3
rvm use 1.9.3
rvm rubygems latest

Now the latest version of ruby is 2.0 but since most of the documentation will be for 1.9, we’ve decided to also install ruby 1.9.3

Serendipity moment…because not everything is expected!! The redmen appeared…

what for?

 

Once its installed, let’s do the same with Rails, for that we follow Rails guides

In between pops up a jabber window, I can read the word hackathon and #hack4Good, a friend posts the following link
https://geekli.st/hackathon/52793a2660fb3f52d50001f8

yes, well a bit of procrastination…but not too much and for a good cause 😉

Ok, time to get into testing, unit test, integration test, test, test, test….

The good thing about the DIWO, among many others is that you exchange info, so I discovered https://learn.thoughtbot.com

Nice, so lets do some screen cast course on testing. Today Integration tests.
I’ve ended up finding out, that one of the things that I keep doing is miss spelling things, getting mess up with :, arrgggg, more annoying things, is not long since I’ve began using zsh as shell, but each time that I run my spec I get the followin error

zsh: correct 'rspec' to '.rspec' [nyae]? n

ufff … I’ll have to solve this.

More things that have come across while screencasting, that make me doubt in config/routes I can declare both
resource and resources … yes 1 ‘s’ difference … and what is the difference? no idea … question to ask.

While going though the tutorial I found out that I had install rails4 for my webcalendar app, but also for the tutorial I’m using rails4, though its done for rails 3, so I have to adapt certain things, as including strong parameter in the controller instead of attr_accesible in the model, so once updated it would look like


def create
@todo = Todo.new(todo_params)
@todo.save
redirect_to todos_path
end
private
def todo_params
params.require(:todo).permit(:description)
end
end


Going for a tea, eating some cookies to get a bit of energy(this time the redmen were not involved)…and in the meanwhile, doing some refactoring in the tests and finding out that things are deprecated but should be substituted by the same thing??

DEPRECATION: Rspec is deprecated. Use RSpec instead. Called from /todos/spec/support/sign_in_helpers.rb:13:in `<top (required)>'.

Tomorrow I’ll check that for the moment, I just take notes 😛