initialize: once, when the controller is first instantiatedconnect: anytime the controller is connected to the DOM
First, add pry-rails to your Gemfile:
https://github.com/rweng/pry-rails
gem 'pry-rails', group: :developmentThen you'll want to rebuild your Docker container to install the gems
⚡ See me talk about this at the London Node User Group ⚡
Found out today that while debugging a node application using console.log() in the terminal I can pass arguments that formats the styles in the console.
console.log('\x1b[31m', 'Hello, world', '\x1b[0m'); // red
| # A common concern,include into all doc modules | |
| # | |
| module BaseDoc | |
| include Apipie::DSL::Concern | |
| def namespace(namespace, options = {}) | |
| @namespace = namespace | |
| @namespace_name = options[:name] | |
| end | |
| attr_reader :namespace_name |
| # Compiled source # | |
| ################### | |
| *.com | |
| *.class | |
| *.dll | |
| *.exe | |
| *.o | |
| *.so | |
| # Packages # |
Originally published in June 2008
When hiring Ruby on Rails programmers, knowing the right questions to ask during an interview was a real challenge for me at first. In 30 minutes or less, it's difficult to get a solid read on a candidate's skill set without looking at code they've previously written. And in the corporate/enterprise world, I often don't have access to their previous work.
To ensure we hired competent ruby developers at my last job, I created a list of 15 ruby questions -- a ruby measuring stick if you will -- to select the cream of the crop that walked through our doors.
Candidates will typically give you a range of responses based on their experience and personality. So it's up to you to decide the correctness of their answer.
http://guides.rubyonrails.org/migrations.html
