Daniel Vinciguerra dvinciguerra

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.

How this was created: Claude Code analyzed the entire codebase - routes, controllers, models, concerns, views, JavaScript, CSS, tests, and configuration. The goal was to extract not just what patterns are used, but why - inferring philosophy from implementation choices.

IRC Reference

Not intended as a guide for newbies, more like a "cheat sheet" for the somewhat experienced IRC user, especially one who wields some power over a channel.

The Basics

/join #channel
- Joins the specified channel.
/part #channel
Leaves the specified channel.

first=$1
second=$2

# Replace
find -name *.cpp -or -name *.h | xargs grep "$first" -l  | xargs perl -pi -e "s/$first/$second/g"

a=getDefaultIncludes; b=get_include_dirs_def; find -name "*.py" -or -name "SC*" | xargs grep "$a" -l  | xargs perl -pi -e "s/$a/$b/g"

a=abc; b=def; find -name "*.cpp" -or -name "*.h" | xargs grep "$a" -l | xargs perl -pi -e "s/$a/$b/g"

FWIW: I (@Rondy) am not the author of the content presented here, which is an outline from Edmond Lau's book. I've just copy-pasted it from somewhere and saved as a personal gist, before it got popular on newsnews.ycombinator.com. I don't remember where exactly the original source is from and neither could find the author's name, so I cannot give him/her the proper credits.

Effective Engineer - Notes

By Edmond Lau
Highly Recommended 👍
http://www.theeffectiveengineer.com/

Itamaeで擬似的にEnvironmentを設ける時の書き方

Itamae実行時にノードアトリビュートを与えて実行する(itamae -y node.yaml recipe.rb or itamae -j node.json recipe.rb)が、そのノードアトリビュート内部で擬似的にEnvironment変数を設定しておく。

# nodes/hogehoge-web-server.yaml
environment: development
cookbooks:
    - dnsmasq

MiniTest::Spec

use must for positive expectations and wont for negative expectations.

must_be | list.size.must_be :==, 0
must_be_close_to | subject.size.must_be_close_to 1,1
must_be_empty | list.must_be_empty
must_be_instance_of | list.must_be_instance_of Array
must_be_kind_of | list.must_be_kind_of Enumerable

	KEYMAPOPTS="us us"
	HOSTNAMEOPTS="-n alpine"
	INTERFACESOPTS="auto lo
	iface lo inet loopback

	auto eth0
	iface eth0 inet dhcp
	hostname alpine
	"
	TIMEZONEOPTS="-z UTC"

	{
	"workbench.startupEditor": "newUntitledFile",
	"editor.fontSize": 14,
	"editor.lineHeight": 1.8,
	"javascript.suggest.autoImports": true,
	"javascript.updateImportsOnFileMove.enabled": "always",
	"editor.rulers": [80, 120],
	"extensions.ignoreRecommendations": true,
	"typescript.tsserver.log": "off",
	"files.associations": {

	# This template is inspired on https://github.com/basecamp/audits1984/blob/master/.rubocop.yml
	#
	# 1 - Add dependencies to group :development, :test
	# gem "rubocop", "~> 1.26", require: false
	# gem "rubocop-performance", require: false
	# gem "rubocop-rails", require: false
	#
	# 2 - Create a file .rubocop.yml and add the lines below
	# inherit_from: https://gist.githubusercontent.com/lazaronixon/7815d84702f277ead5e89c9f2aa5581f/raw/rubocop.yml
	#

	# The following comments fill some of the gaps in Solargraph's understanding of
	# Rails apps. Since they're all in YARD, they get mapped in Solargraph but
	# ignored at runtime.
	#
	# You can put this file anywhere in the project, as long as it gets included in
	# the workspace maps. It's recommended that you keep it in a standalone file
	# instead of pasting it into an existing one.
	#
	# @!parse
	# class ActionController::Base