One Paragraph of project description goes here
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
N+1 query problem
eager_load
wherepreload
| # Refactoring conditional logic using short-circut evaluation and ruby implicit return | |
| # before refactor | |
| def straight_flush?(array) | |
| if straight?(array) and flush?(array) | |
| return true | |
| else | |
| return false | |
| end | |
| end |
| // This code is to be used with https://turbo.hotwire.dev. By default Turbo keeps visited pages in its cache | |
| // so that when you visit one of those pages again, Turbo will fetch the copy from cache first and present that to the user, then | |
| // it will fetch the updated page from the server and replace the preview. This makes for a much more responsive navigation | |
| // between pages. We can improve this further with the code in this file. It enables automatic prefetching of a page when you | |
| // hover with the mouse on a link or touch it on a mobile device. There is a delay between the mouseover event and the click | |
| // event, so with this trick the page is already being fetched before the click happens, speeding up also the first | |
| // view of a page not yet in cache. When the page has been prefetched it is then added to Turbo's cache so it's available for | |
| // the next visit during the same session. Turbo's default behavior plus this trick make for much more responsive UIs (non SPA). | |
| # app/models/friendship.rb | |
| class Friendship < ApplicationRecord | |
| belongs_to :user | |
| belongs_to :friend, class_name: 'User' | |
| end |
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.
| #!/bin/bash | |
| # ๐ 2025 Shell Wrapped | |
| # A "Spotify Wrapped" style summary of your shell command usage | |
| # | |
| # Usage: curl -sL <gist-raw-url> | bash | |
| # or: chmod +x shell-wrapped-2025.sh && ./shell-wrapped-2025.sh | |
| # โ ๏ธ SAFETY: This script is 100% read-only. It only reads your shell | |
| # history file and prints statistics. No files are modified or deleted. | |
| # Feel free to audit the code below before running. |