Lesson learned after trying functional programming (as a Ruby developer)
I’m a Ruby developer since early 2010 and big fan of Object Oriented Programming (OOP) always extending my knowledge around it. But as a part of OO growth it’s required to play around with new concepts and ideas and see where they take you. And that’s what I was doing past 2 years in free time with Elixir (a functional programming language). Recent years there is quite a rumble around functional p
PATCH vs PUT and the PATCH JSON syntax war
There are several articles/discussions on parallels of PUT vs PATCH and when to use one before other. Also the main struggle recent years seems to be how to translate the RFC proposal for PATCH JSON format. I’ve decided to spam the internet with one more opinionated article on this topic trying to explain everything one more time. First of all I’m a Ruby on Rails developer so I will reference some
RSpec be_within matcher
You can find entire code example in this gits RSpec has some really nifty built in matchers. In this article we will have a look at be_within matcher. The syntax is pretty simple value = 10.0001 expected_value = 10.0001 delta = 0.0001 expect(value).to be_within(delta).of(expected_value) The most common example where to use be_within is when comparing floating point values if their are in a range/d
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Ruby #call method
CSRF protection on single page app API
Policy Objects in Ruby on Rails
POST != Create and PUT != Update
Setup Ubuntu 16.04 for Ruby on Rails app (Cheatsheet)
