The Perfect Margarita
This is my "go to" margarita because of the ease of preparation and the simplicity of ingredients.
1oz orange liqueur, 2oz tequila, 3oz limeade, 1/2 lime, shaken with ice.
What should we look for when doing code review? How should we receive code reviews from others?
thoughbot's Code Review guide is a great starting point. It articulates principles for the relational side of code review. This is especially relevant for us in a remote environment. How we give and receive feedback is as important as the feedback itself.
The following is a very incomplete list of questions to ask yourself during code review. The items here are meant to be starting points for a conversation with the code's author. Always assume the best intentions.
I highly suspect that the RSpec core team all use black backgrounds in their terminals because sometimes the colors aren’t so nice on my white terminal
I certainly use a black background. I'm not sure about the other RSpec core folks. Regardless, if there are some color changes we can make that would make output look good on a larger variety of backgrounds, we'll certainly consider that (do you have some suggested changes?). In the meantime, the colors are configurable, so you can change the colors to fit your preferences on your machine. First, create a file at
You'll need to reinstall
pow after updating the
POW_DOMAINS env var (see http://pow.cx/manual#section_3.1 for more details).
echo "export POW_DOMAINS=test,local" > ~/.powconfig curl get.pow.cx | sh
Now you should be able to access your local apps (that are being server by
pow) at the
See also: https://github.com/basecamp/pow/pull/547
defmodule HistogramCup do @moduledoc """ You are given an input list whose each element represents the height of a line towers. The width of every tower is 1. It starts raining. How much water is collected between the towers? Input: [1,5,3,7,2] , Output: 2 units Explanation: 2 units of water collected between towers of height 5 and 7
An excerpt from Programming Phoenix by Chris McCord, Bruce Tate, and José Valim
You won’t find a "PhoenixDelayedJob" or "ElixirResque", those complex packages that exist only to spin off reliable processes as a separate web task.
You don’t need one. Don’t get us wrong. In Ruby, those packages are well-conceived and a critical part of any well-crafted solution. In Elixir, those frameworks turn into primitives. The Elixir programming model makes reasoning about concurrent systems almost as easy as reasoning about single threaded ones. When you have two database fetches, you won’t have to artificially batch them together with a stored procedure or a complex query. You can just let them work at the same time, like this:
company_task = Task.async(fn -> find_company(cid) end)