Andres Leon aleonjob

🆕 Update: See more extensive repo here: https://github.com/marckohlbrugge/unofficial-37signals-coding-style-guide

The Unofficial 37signals/DHH Rails Style Guide

About This Document

This style guide was generated by Claude Code through deep analysis of the Fizzy codebase - 37signals' open-source project management tool.

Why Fizzy matters: While 37signals has long advocated for "vanilla Rails" and opinionated software design, their production codebases (Basecamp, HEY, etc.) have historically been closed source. Fizzy changes that. For the first time, developers can study a real 37signals/DHH-style Rails application - not just blog posts and conference talks, but actual production code with all its patterns, trade-offs, and deliberate omissions.

Create new umbrella application

$ mix new chatter --umbrella
$ cd chatter

Create new Phoenix Project

$ cd apps

N+1 query problem

ORMs make it easy to a query per loop iteration, which we want to avoid

eager_load

single query (left outer join)
can reference the other table's columns in where

preload

a few queries (one per table)
typically faster

Common Options

-#, --progress-bar Make curl display a simple progress bar instead of the more informational standard meter.

-b, --cookie <name=data> Supply cookie with request. If no =, then specifies the cookie file to use (see -c).

-c, --cookie-jar <file name> File to save response cookies to.

	# FOR BUSY JOBS
	# take the process_id from the /busy page in sidekiq and kill the longest running one.
	workers = Sidekiq::Workers.new
	long_process_id = 'integration.3:4:71111aaa111' # Eg: 'integration.3:4:71d1d7f4ef5a'
	workers.each do \|process_id, thread_id, work\|
	process = Sidekiq::Process.new('identity' => process_id)
	process.stop! if process_id == long_process_id
	end

	# FOR SCHEDULED JOBS