wreq
If you're coming from Ruby, think HTTParty level of abstraction.
https://www.stackage.org/package/wreq
This is a great tutorial written by the creator. Definitely something to aspire to as a library author.
wreq
If you're coming from Ruby, think HTTParty level of abstraction.
https://www.stackage.org/package/wreq
This is a great tutorial written by the creator. Definitely something to aspire to as a library author.
I hereby claim:
To claim this, I am signing this object:
###The design of an interface should always speak the language of the consumer, ###for if not for the consumer, the interface serves no purpose.
I've been bitten by this on multiple projects now.
Take the following test setup for the class Accounts::Analytics::Account
module Accounts
module Analtyics
describe Account do
end
end
[Idempotence vs. Referential Transparency] (http://blog.tmorris.net/posts/idempotence-versus-referential-transparency/)
[Kingdom of Nouns] (http://steve-yegge.blogspot.com/2006/03/execution-in-kingdom-of-nouns.html)
[Destroy all ifs] (http://degoes.net/articles/destroy-all-ifs)