| #!/usr/bin/env ruby | |
| # -*- coding: utf-8 -*- | |
| require "net/https" | |
| require "uri" | |
| require "json" | |
| require "time" | |
| KEENIO_PROJECT_ID = "XXXXXXXX" | |
| KEENIO_READ_KEY = "YYYYYYYY" |
The first thing that really surprised me today was the flexibility of Ruby's shovel operator, <<. A student in the class had tried the following:
a = [0]
a << aWhat do you think a is now? I was sure it would be [0, [0]]. But lo and behold, Ruby sparkles;
a = [0]
a << a
Day 1 of GA WDI program: we spent majority of the class in terminal(shell), getting comfortable with command line prompts. We also played with some Ruby in and Sublime Text. All in all, a good review of all the prep work on command line stuff. Ubuntu isn't as scary as when I first installed it yesterday.
tl;dr: Terminal Commands, Shebang #!/usr/bin/env ruby, chmod a+x demo.rb , Literals, cat, less.
file_name.md --> md stands for markdown file type
Ctrl + to zoom in (in apple: Cmd +)
The normal controller/view flow is to display a view template corresponding to the current controller action, but sometimes we want to change that. We use render in a controller when we want to respond within the current request, and redirect_to when we want to spawn a new request.
The render method is very overloaded in Rails. Most developers encounter it within the view template, using render :partial => 'form' or render @post.comments, but here we'll focus on usage within the controller.