Enough With the Service Objects Already
Enough With the Service Objects Already Skip to entry content Once upon a time I was writing a web app that needed to accept notifications of payments. Once it was notified of a payment (via a webhook) it needed to take certain actions to fulfill the purchase. An overweight controller Imagine that you’re working on this app. The payment notifications come in the form of PayPal-style IPN data. Here
Riffing on `interpose` implementations in Ruby - avdi.codes
Riffing on `interpose` implementations in Ruby Skip to entry content I very much enjoyed Brian Cobb’s step-by-step translation of the Clojure interpose function to Ruby. I too agree that interpose would be a handy method to have around. As a quick TL;DR: interpose is kind of like Array#join , except that it produces a sequence instead of a string. [1, 2].interpose(:sep).to_a # => [1, :sep, 2] Br
Zero to Smoke Test with Sinatra
The other day I put an app in production with (gasp) no automated tests. I’m careful to say no automated tests, because of course I had been testing it manually throughout the ~12 hours it took me to write the initial version of the app. In lieu of tests, I made sure to log copious amounts of information, which I then collected from my deployed app into Papertrail. For a single day’s work this was
Configuring database_cleaner with Rails, RSpec, Capybara, and Selenium - avdi.codes
Configuring database_cleaner with Rails, RSpec, Capybara, and Selenium Skip to entry content If you write Rails code, or any Ruby code that interacts with a database, and you also write automated tests, chances are you have heard of or used the database_cleaner gem. It’s a terrific gem that abstracts away the various ORM APIs for getting the DB into a “blank slate” state. Periodically I start a ne
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
What it’s like to come back to a Ruby project after 6 months - avdi.codes
