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
Two screencasts, two ways to eradicate Ruby nil values – RubyTapas
Two screencasts, two ways to eradicate Ruby nil values nil values are the worst. They crop up where you didn’t expect them. Their presence forces you to litter your code with conditionals: checking, checking, and checking again if a variable contains nil . Today I’m making available a classic screencast from the RubyTapas archives. In it you’ll see a way to remove nils while dramatically simplifyi
How to make your Ruby code work on Windows PCs – RubyTapas
Windows users can feel like second-class-citizens in the Ruby world. Ruby gems and tools often don’t work quite right on Windows hosts. But we can fix this. Making your code Windows-compatible isn’t as difficult as you might think, and in the process you’ll learn to understand Ruby better! Welcome to the desert of the PC The vast majority of Ruby software is developed on UNIX-like machines. Go to
Things You Didn't Know About Exceptions
tries = 0 success = false while(!success && tries < 3) puts "Trying #{tries}..." return if success tries += 1 end puts "Giving up." Trying 0... Trying 1... Trying 2... Giving up.
Exceptional Ruby
By the end of this talk you should: Understand the mechanics of Ruby failure handling Be able to architect a robust failure handling strategy For apps or libraries. Be exceptionally bored This talk is about failure Exceptions are how we signal failures Failures are often caused by errors So what is a failure?
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
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
Exceptional Ruby
Emacs Chat with Avdi Grimm (Org-mode, Ruby, etc.) :: Sacha Chua
RubyTapas