songjiz

import { Controller } from "stimulus";
import { get } from "@rails/request.js";
import { PageSnapshot } from "@hotwired/turbo";

export default class extends Controller {
  static values = { hoverTime: Number };
  connect() {
    this.element.addEventListener("mouseover", this.prefetch.bind(this));
    this.element.addEventListener("touchstart", this.prefetch.bind(this));
  }

songjiz

import * as React from "react";
import { useMousePosition } from "~/hooks/useMousePosition";

/** Component to cover the area between the mouse cursor and the sub-menu, to allow moving cursor to lower parts of sub-menu without the sub-menu disappearing. */
export function MouseSafeArea(props: { parentRef: React.RefObject<HTMLDivElement> }) {
  const { x = 0, y = 0, height: h = 0, width: w = 0 } = props.parentRef.current?.getBoundingClientRect() || {};
  const [mouseX, mouseY] = useMousePosition();
  const positions = { x, y, h, w, mouseX, mouseY };
  return (
    <div

songjiz

import Foundation

enum Environment: String {
    case development, staging, production
}

extension Environment {
    static var current: Environment {
        if isAppStore {
            return .production

songjiz

# MODEL

class Case < ActiveRecord::Base
  include Eventable
  
  has_many :tasks

  concerning :Assignment do
    def assign_to(new_owner:, details:)
      transaction do

songjiz

class Notifier < ActionMailer::Base
  delivers_from '[email protected]'
  
  def welcome(user)
    @user = user # available to the view
    mail(:subject => 'Welcome!', :to => user.email_address)
    # auto renders both welcome.text.erb and welcome.html.erb
  end
  
  def goodbye(user)

songjiz

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.