Skip to content

Instantly share code, notes, and snippets.

federicofazzeri / .babelrc
Last active Jun 29, 2021
Node Express-based REST API (CRUD) using Firebase cloud Functions and FireStore cloud database + Babel config (The current Node version running in Cloud Functions is 6.10)
View .babelrc
"presets": [
["env", {
"targets": {
"node": "6.10"
patpohler / Big List of Real Estate
Last active Jul 27, 2021
Evolving list of Real Estate APIs by Category
View Big List of Real Estate

Big List of Real Estate APIs

Listings / Property Data

####Rets Rabbit

Rets Rabbit removes the nightmare of importing thousands of real estate listings and photos from RETS or ListHub and gives you an easy to use import and Web API server so you can focus on building your listing search powered website or app.

ryanb /
Created Nov 29, 2012
Points on how modules can make code difficult to read.

My issues with Modules

In researching topics for RailsCasts I often read code in Rails and other gems. This is a great exercise to do. Not only will you pick up some coding tips, but it can help you better understand what makes code readable.

A common practice to organize code in gems is to divide it into modules. When this is done extensively I find it becomes very difficult to read. Before I explain further, a quick detour on instance_eval.

You can find instance_eval used in many DSLs: from routes to state machines. Here's an example from Thinking Sphinx.

class Article < ActiveRecord::Base