| /* in ES6 you can use fat arrows to write anonymous functions */ | |
| const myFunction = () => { | |
| console.log('hello'); | |
| }; | |
| myFunction(); | |
| // hello | |
| /* but we can even simplify this further by removing the curly braces… */ |
| 1) justify-content: flex-end; | |
| 2) justify-content: center; | |
| 3) justify-content: space-around; | |
| 4) justify-content: space-between; | |
| 5) align-items: flex-end; | |
| 6) align-items: center; | |
| justify-content: center; | |
| 7) justify-content: space-around; | |
| 8) flex-direction: row-reverse; | |
| 9) flex-direction: column; |
Disclaimer: This piece is written anonymously. The names of a few particular companies are mentioned, but as common examples only.
This is a short write-up on things that I wish I'd known and considered before joining a private company (aka startup, aka unicorn in some cases). I'm not trying to make the case that you should never join a private company, but the power imbalance between founder and employee is extreme, and that potential candidates would
Collection of various design resources I use for projects and inspiration.
What this guide will cover: the code you will need in order to include Redis and Resque in your Rails app, and the process of creating a background job with Resque.
What this guide will not cover: installing Ruby, Rails, or Redis.
Note: As of this writing I am still using Ruby 1.9.3p374, Rails 3.2.13, Redis 2.6.11, and Resque 1.24.1. I use SQLite in development and Postgres in production.
Background jobs are frustrating if you've never dealt with them before. Over the past few weeks I've had to incorporate Redis and Resque into my projects in various ways and every bit of progress I made was very painful. There are many 'gotchas' when it comes to background workers, and documentation tends to be outdated or scattered at best.
Helper methods in rails are used only in views, not controllers. If you want to make a method available to multiple controllers, you can declare it in the ApplicationController, which is the base class for all your controllers. If you want the method to be visible to views, declare it as a helper_method.
It's important to note that running this reset will drop any existing data you have in the application
heroku restartheroku pg:reset DATABASE (no need to change the DATABASE)heroku run rake db:migrateheroku run rake db:seed (if you have seed)One liner
| require "open-uri" | |
| require "net/http" | |
| Error = Class.new(StandardError) | |
| DOWNLOAD_ERRORS = [ | |
| SocketError, | |
| OpenURI::HTTPError, | |
| RuntimeError, | |
| URI::InvalidURIError, |
Method lookup is a simple affair in most languages without multiple inheritance. You start from the receiver and move up the ancestors chain until you locate the method. Because Ruby allows you to mix in modules and extend singleton classes at runtime, this is an entirely different affair.
I will not build contrived code to exemplify the more complicated aspects of Ruby method lookup, as this will only serve to confuse the matter.
When you pass a message to an object, here is how Ruby finds what method to call:
I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!
\