INSERT GRAPHIC HERE (include hyperlink in image)
Subtitle or Short Description Goes Here
ideally one sentence >
| require 'yaml' | |
| Track = Struct.new :title, :duration | |
| # An Album represents an audio medium which has title, | |
| # interpret, a pause duration between tracks and a list | |
| # of individual tracks. | |
| class Album | |
| attr_reader :title, :interpret, :pause |
| threads=1 | |
| task-workers=0 | |
| out-of-order-eval=false | |
| max-prefetch=0 | |
| minibatch-size=1 | |
| nncache=0 | |
| smart-pruning-factor=0 |
| class AttachedValidator < ActiveModel::EachValidator | |
| # Active Storage validator to ensure that an attachment is attached. | |
| # | |
| # usage: | |
| # validates :upload, attached: true | |
| # | |
| def validate_each(record, attribute, _value) | |
| return if record.send(attribute).attached? | |
| errors_options = {} |
Exported on 6/12/2025 at 16:19:24 GMT+9 from Cursor (1.0.0)
User
Explain how KameSame does synonym detection when a user answers a question with a valid response but not the one we're looking for. can you please produce a report explaining this at a conceptual level and then back it up with progressively deeper technical dives?
I remember that while this is driven through the UI, it runs all the way down to the design of the database views, which i believe i even materialized for speed so that every night when the dictionaries are updated the synonym query is faster. i'll need you to check me on that stuff though b/c it's been 6+ years since i did this. provide receipts!
🆕 Update: See more extensive repo here: https://github.com/marckohlbrugge/unofficial-37signals-coding-style-guide
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.
| name | Logging Best Practices |
|---|---|
| description | Use before implementing logs in a medium to large scale production system. |
This skill is adpated from "Logging sucks. And here's how to make it better. by Boris Tane.
When helping with logging, observability, or debugging strategies, follow these principles: