Can confirm, Claude Cowork is very cool, but if you actually use it for more than a few minutes it'll bring any Mac to its knees. Entire system becomes unresponsive eventually. https://github.com/a...
Can confirm, Claude Cowork is very cool, but if you actually use it for more than a few minutes it'll bring any Mac to its knees. Entire system becomes unresponsive eventually. https://github.com/anthropics/claude-code/issues/22543
Originally appeared on SINAPTIA.A few weeks ago, we ran into an interesting problem in one of our projects. We had a reports table with a reason column that used the classic Rails enum approach:
#...
Originally appeared on SINAPTIA.A few weeks ago, we ran into an interesting problem in one of our projects. We had a reports table with a reason column that used the classic Rails enum approach:
# db/migrate/XXXXXXXXXXXXXX_create_reports.rb
class CreateReports < ActiveRecord::Migration[7.1]
create_table :reports do |t|
t.string :title
t.integer :reason, default: 0, null: false
end
end
# app/models/report.rb
class Report < ApplicationRecord
enum :reason, {
spam: 0,
harassment: 1,
inappropriate_content: 2,
copyright: 3,
misinformation: 4
}, prefix: true
end
Everything worked fine until the client requested the ability to select multiple reasons for a report. A user could report…
Rails’ enum DSL is great for single values, but what about multiple? We compared 4 approaches across performance, extensibility, and maintainability to find the best fit. https://sinaptia.dev/post...
Rails’ enum DSL is great for single values, but what about multiple? We compared 4 approaches across performance, extensibility, and maintainability to find the best fit. https://sinaptia.dev/posts/storing-multi-valued-enum-fields-in-activerecord
